We keep getting this error for a job that normally runs for 5-10 minutes, but has been ittermittently running with no scheduler id as an error, or we have to kill it after 5-10 minutes when it doesn't get a scheduler id. We suspect it's the thread pools but not sure if that's the reason consistently. Please advise.
------------------------------
Scheduling Consultant
South Jersey Industries
GA
------------------------------