I’ve been seeing a series of print jobs getting stuck in the active status, when I dig through the server logs, I don’t see the related tasks, numbers, it’s as if the task agent is not processing the request.
Stuggling to find the root cause of this problem,.
What I know: Two situations it is happening for, an automated print being generated by a function using a Baq report, and an auto print fired by a data directive SOAck report) Testing printers installed on the app servers logged in as the app pool user work. We have three task agents on different servers.
I had enabled logging for sysatak and reports in the app server confiig file.
The big issue is it seems to be random and no really repeatable fashion. The Active tasks have a schedule and task of 0.
Any thoughts as to how I can better find the root cause. I know I can enable verbose logging on the task agent logs themselves rather than the server log. I am also aware of Applicatipn insights and Serillogs, but have not delved that deeply into that area yet.
I would be interested if someone could explain the chronological steps the task status takes as it proceeds through the process from being submitted, going active, complete and the error status, and any other status I missed (is it pending??)., and of course when the Task Agent actually get picks up the taak. This thread.might be a good explainer.
I would also be interested if anyone haa come across this issue in their own environment before and how they solved it.
Thanks