Unable to run job due to "failed to acquire semaphore lock or maximum job count reached" when 0 instances running (11 replies)
Closed due to inactivity.
Closed due to inactivity.
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
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.