Error on Print Job Event ID

[Tech Savvy]

Hi All,

Does anyone know what Windows Event View ID(s), if any, are fired when a Print Job fails to print?

I have a client that has LOB apps that auto print and once in a while it will fail. I'd like to start monitoring for a stuck job and create a script to fix it in my automated remediation with Syncro.

Not sure where to start except to look it up the next time they call, but if I can do this proactively that would be awesome!

 

[Mick]

372 rings a vague bell. In the Admin section, from memory.

 

[HCHTech]

Here is an article that seems on point. It looks like you need to enable the log & increase its default size, so you'll probably need powershell for that. @Mick is right about 372 being one kind of failure, but I'll bet there are others. I would definitely ask someone to call you when it happens next so you can investigate the specific error that is recorded when they have whatever problem they are having.

Also, you may find that your RMM limits you to which logs you can check - I had a similar task last year, looking for a way to check Hyper-V replication errors, and my RMM (Solarwinds) wouldn't let me check the log that contained the salient data. Fun times.

 

[alexsmith2709]

I dont know the event ID but this script is great if its a print spooler/print queue issue https://bradkovach.com/printflush/

 

[Tech Savvy]

I dont know the event ID but this script is great if its a print spooler/print queue issue https://bradkovach.com/printflush/

Thanks for the response, although I dont like this option... this script is a standard one.... stop the print spooler, clear existing jobs, restart the print spooler. However I definitely don't want to clear ALL the jobs. The print jobs coming in are online orders, if the job is dropped they have to find the order in one of three LOB apps and manually reprint it... not the best if you have a queue of 20 orders and ONE stuck print job wipes them all out.

In any sense, I can handle clearing/restarting the one print job, but the question I was really after in this post is how to automatically recognize that the issue has occurred so that it can be automatically remediated via the script.

Not flaming you for attempting to help, just clarifying for anyone else that is looking for something similar.

 

[HCHTech]

It sounds to me that by the time the job is stuck in the queue, unprintable for some reason, that it is too late to fix the problem on that one job. The only real option is to clear the queue. I think some effort needs to be made to identify what is going wrong during the creation of the print job to cause it to be unprintable.

 

[alexsmith2709]

Thanks for the response, although I dont like this option... this script is a standard one.... stop the print spooler, clear existing jobs, restart the print spooler. However I definitely don't want to clear ALL the jobs. The print jobs coming in are online orders, if the job is dropped they have to find the order in one of three LOB apps and manually reprint it... not the best if you have a queue of 20 orders and ONE stuck print job wipes them all out.

In any sense, I can handle clearing/restarting the one print job, but the question I was really after in this post is how to automatically recognize that the issue has occurred so that it can be automatically remediated via the script.

Not flaming you for attempting to help, just clarifying for anyone else that is looking for something similar.

If a job is really stuck, the only way to remove it is to stop the spooler delete the temp files and restart the spooler.
ID 6161 is also apparently a print spooler error. If you can find a consistent error in event ID from within event viewer you can attached an action and set that to run a program/script to run when the event is logged. Would this work?