Unable to run job due to "failed to acquire semaphore lock or maximum job count reached" when 0 instances running (11 replies)
Wow...
I changed the "Maximum Concurrent Instances" value to 206, and it's STILL NOT RUNNING.
It appears that the only way to run a job now is to set "Maximum Concurrent Instances" to 0 in order to get it to run.
This is not acceptable, as this job should only run 1 instance at a time.
Randy, we're aware of the issue.
The only way to resolve this at present is to either change the maximum instances to 0, or restart the server to clear the semaphore.
I am going to open a support ticket, as we need some collateral from you, so we can identify the cause.
Thanks
Thanks for this response.
Is it possible to have a different error message for each case? The present one "failed to acquire semaphore lock or maximum job count reached" doesn't really tell you if it's an issue with a semaphore lock, or the maximum concurrent instances job count being reached. It makes it hard for the user to discern what is actually happen if you have 2 error messages rolled into one.
Also, since setting "Maximum Concurrent Instances" to 0 isn't really in option in all cases, can you provide information on how to clear the semaphore?
The only present fix is to restart the server.
The server was restarted last night, and on the first run the job ran into the same issue.
Is there a planned fix for this? We cannot run the job without setting "Maximum Concurrent Instances" to 0 which is not acceptable as the job is quite resource intensive.
Any update on this?
Hello?
We attempted the fix sent over, and it failed and after reverting IMan is broken and cannot run any jobs.
The error in IMan (after installing patch) was: "Method not found: 'System.String Realisable.Utils.Security.SecurityIdentity.GetLocalisedNameFromWellKnownSid(Realisable.Utils.Security.WELL_KNOWN_SID_TYPE)'."
After reverting to the original version of Realisable.Utils.Concurrency.dll, we are now getting errors of "Automation Error"
I will send Errors.txt along in an email, but I will include the screenshots of IMan.
Also, when we ran the .cmd file, we noticed an error, I will include that screenshot as well.
I have a job which is set to run every 15 minutes... but it hasn't run in 3 days due to a "failed to acquire semaphore lock or maximum concurrent job count reached" error even thought that job has a "Maximum Concurrent Instances" value of 1. I changed this value to 0 to test the job, and it ran. I then changed it back to 1, and now I"m getting that error again.
The job is currently not running, but for some reason IMan thinks that the job is running so it will not run again with "Maximum Concurrent Instances" set to 1.
I have restarted all of the IMan services, but it STILL thinks there is a job running...
Is there a way to clear IMan so that it no longer incorrectly thinks that the job is running, because it obviously isn't running.