It seems like every night we have a SQL job scheduled the Epicor Task Agent gets hosed up and stops working.
I’ve had to disable the job since I get a call every night about the task agent not spitting out the reports.
We print out a BAQ report around 100-200 times an hour and so when the task agent starts running into problems, we lose out on a chunk of time where the report isn’t being ran / printed.
The issue is that the report goes into either the Scheduled Tasks as an “Immediate run request” or it goes into the Active Tasks as “PENDING” and just stays there… When I remote in and go to fix the issue I usually have to clear out all these pending tasks and the immediate run request tasks and then either restart the Task Agent service itself - or just the Production Environment task agent.
Has anyone else had issues like this before? I’m not sure why SQL jobs would cause issues with the Task Agent at all, but even now that the jobs are disabled the tasks still get hung up at least twice a week. Any ideas?
During a time that production isn’t running I bet we could manually get the issue to occur just by running the SQL job and trying to run the same amount of BAQ reports that is usually ran…
Here’s the job information:
It’s part of the Daily Maintenance plan
It’s just puzzling that the task agent runs into issues whenever SQL starts running something…
aidacra
(Nathan your friendly neighborhood Support Engineer)
5
The SQL job is blocking a SQL object that the task agent processing needs. Don’t use the built-in SQL Wizard options for index/stats maintenance as it is overkill. I’d recommend implementing the Ola Hallengren index maintenance script as it only maintains those indexes/stats when it is needed based on the thresholds you set.
A Reorganization is online and non-blocking and it’s most likely the Update Stats Fullscan, that being said definitely use a script to intelligently only reorganize the indexes that need it.
Just a side note. You should not need to delete out the jobs stuck in immediate run or pending. When you restart the Task Agent it should kick them off and start to print out.
