I think I might have an explanation. I noticed from the log that job CRP550 entered the queue and did not finish.
I think that job might have caused the problem.

Its possible that this job threw a dialog box error and is waiting for a response.

Would this cause this problem?

Wed Dec 20, 2017 12:15 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6608

Quote:

Its possible that this job threw a dialog box error and is waiting for a response.

Would this cause this problem?

Yes, that certainly would. It would block the queue and eventually lead to "is near or at max-jobs capacity". Perhaps you can set timeout for the job in question, and let the scheduler to terminate it it and free the queue if the job gets stuck somehow.

Also, you can change that job properties, assign it to a separate queue, and make the scheduler not to queue new instances of the job if any are already running or queued. This way other jobs will not be impacted, they will run in a different queue, and for this one it would be easier to monitor and troubleshoot too.