Monday, July 15, 2019

Server spooler crash troubleshooting

Google: determine|identify|troubleshoot|pinpoint printer|driver|what cause server spooler crash|stop

Print Spooler Issue on Server 2012 R2 Dec 14, 2016
[Monitor C:\Windows\System32\spool\PRINTERS for orphaned print jobs and] When this happens look in the listed printers on the print server to see if it is any one particular printer that is offline with hung up print jobs. It may well just be a particular printer with a corrupt driver.
...
[From Print Management,] set [suspected] drivers to Isolated mode (Right click --> Set Driver Isolation --> Isolated

Spooler Crashing in Windows 2016
You'll first want to check the print queue and see if there are "stuck" or "ghost" jobs and purge them. Then use the spooler restart steps above.
a good area to check for spooler crashes may be watching how many active printer sessions your print environment is establishing with that server. Too many simultaneous sessions will flood the print queue and cause the print spooler to crash.

Note to self:
Crashed printer spooler can be found on Windows SYSTEM Logs with event ID 7031 dan 7034

Tool(s) related to redirected printer :
How to use this tool to delete a redirected printer :

No comments:

Post a Comment