Skip to main content
Question

Random Database Deployment error 24R2- IFS remote deployment


Forum|alt.badge.img+6
  • Sidekick (Partner)
  • 14 replies

We are encountering the following error in the 24r2 IFS deployments. In some environments and due to this the deployment process is getting stuck or hanging. In most cases, the deployment hangs indefinitely.

The error occurs during the deployment of IFS 24r2, and it appears inconsistently across various environments.

  • The background jobs are configured to 0.
  • We have attempted to resolve the issue by restarting the database, but the issue persists.
  • On some occasions, the error appears for different packages, not just one specific package, indicating that it may not be isolated to a particular module.

!!!PACKAGE GENERAL_SYS not created/replaced because it is locked by another process. You might need to redeploy it manually

2 replies

NickPorter
Superhero (Customer)
Forum|alt.badge.img+18
  • Superhero (Customer)
  • 324 replies
  • March 24, 2025

Something to consider might be whether a non-IFS process is getting in the way at the server level, such as antivirus or UAC, which is delaying the deployment and resulting in incomplete transactions that then result in locks.  Possibly either on the Apps Server or the DB side.

I used to get timeouts that manifested in strange ways when AV was running and scanning.  If it is something like this you should be able to turn it back on again as needed after deployment.


Forum|alt.badge.img+6
  • Sidekick (Employee)
  • 11 replies
  • March 24, 2025

Hi ​@NuwanK,

You can add the following to your list of troubleshooting steps

1. Make sure all scheduled tasks and background jobs are stopped before the delivery process.

Follow the below steps to turn off scheduled tasks:
-Go to 'System Parameters' > Filter for 'Scheduled tasks process startup' parameter > Set to 'OFF'

Disable ongoing DB processes:
-Go to 'Database Processes' window > Filter all jobs in 'Scheduled' state and use 'Break' command

2. Perform both database and middle tier restart

If the issue keeps happening, it is best to raise a Support case to investigate this in detail.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings