'[380] Unable to start JobManager thread for job' appears in SQLAgent log.

The above message appears in the SQLAgent log. The job(s) in question don't run, it can affect all or only some of the jobs under that agent. Only solution is a restart of the SQLAgent. Can find no mention of JobManager in the online books
Anyone else experienced this?| The above message appears in the SQLAgent log. The job(s) in question
don't run,
| it can affect all or only some of the jobs under that agent. Only
solution is a restart of the
| SQLAgent. Can find no mention of JobManager in the online books.
|
| Anyone else experienced this?
--
This error indicates that you are unable to allocate more threads for
SQLAgent jobs. How many jobs are concurrently running when you hit this
error? You may need to reduce this amount.
Hope this helps,
--
Eric Cárdenas
SQL Server support|||The instance of SQL has approximately 40 jobs configured. Only 3 or 4 are active at one time. The rest are adhoc or run infrequently.||||
| The instance of SQL has approximately 40 jobs configured. Only
| 3 or 4 are active at one time. The rest are adhoc or run infrequently.
--
To confirm or dismiss that this error is a thread issue, setup performance
monitor logs on threads for SQL agent and see if you have an escalation of
threads.
If all else fails, I recommend raising a case with Microsoft product
support to assist you.
Hope this helps,
--
Eric Cárdenas
SQL Server support