none
How do i determine which job, or what is causing the print server to stop spooler service

    Question

  • Hi guys

    Basically somebody is sending something to print which is killing the print server.

    We have like 729 printers.

    I don't know of any way of being able to map the printer to the job in c:\windows\system32\spool\printers as when it dies, I can't bring up the details of the print job due to the print spooler not running and constantly failing.

    Does anyone know of an easy way to do this.  I've also noticed that when connecting to the print server to connect to a new printer runs dog slow.

    Any ideas would be appreciated.

    Thanks

    Tuesday, May 1, 2018 11:55 AM

Answers

  • Hi,

    The best way to determine the cause of crash of Print Spooler is to catch a process dump of Print Spooler and using Windbg (Windows Debugger) to analyze.

    More info about gathering dump of faulting process can be found here :

    http://blogs.technet.com/b/askperf/archive/2009/04/13/prn-spooler-hang-crash.aspx

    http://blogs.technet.com/b/askperf/archive/2007/06/15/capturing-application-crash-dumps.aspx

    Start by updating the Printer driver to its latest version

    Best Regards,

    Frank



    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, May 2, 2018 8:45 AM
  • Hi,

    There is not an easy way to do this. 

    What version of Windows are you running?  There are ways to mitigate this.  With 729 printers you best be setting all the print drivers to shared driver isolation assuming 2008R2 or greater. That will push the failure to printisolationhost.exe rather than spoolsv.exe

    Have you reviewed the Windows Application logs for the failure already?  The faulting module is listed in about 50% of spooler crashes so you can track down the print driver and thus track to some printers.

    If you want to know the secret and have some time, we can discuss but be ready for some work and patience.

    If you have the process HDMP file from C:\ProgramData\Microsoft\Windows\WER\ReportQueue, copy it someplace and send the link.  I should be able to pull a driver dll in about 5 minutes.

    Thanks


    Alan Morris formerly with Windows Printing Team


    Tuesday, May 8, 2018 5:42 AM
    Answerer

All replies

  • Hi,

    The best way to determine the cause of crash of Print Spooler is to catch a process dump of Print Spooler and using Windbg (Windows Debugger) to analyze.

    More info about gathering dump of faulting process can be found here :

    http://blogs.technet.com/b/askperf/archive/2009/04/13/prn-spooler-hang-crash.aspx

    http://blogs.technet.com/b/askperf/archive/2007/06/15/capturing-application-crash-dumps.aspx

    Start by updating the Printer driver to its latest version

    Best Regards,

    Frank



    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, May 2, 2018 8:45 AM
  • Hi,
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Frank

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, May 3, 2018 9:38 AM
  • Hi,

    Was your issue resolved? 

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
    If no, please reply and tell us the current situation in order to provide further help.


    Best Regards,
    Frank

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, May 4, 2018 7:09 AM
  • Hi,

    There is not an easy way to do this. 

    What version of Windows are you running?  There are ways to mitigate this.  With 729 printers you best be setting all the print drivers to shared driver isolation assuming 2008R2 or greater. That will push the failure to printisolationhost.exe rather than spoolsv.exe

    Have you reviewed the Windows Application logs for the failure already?  The faulting module is listed in about 50% of spooler crashes so you can track down the print driver and thus track to some printers.

    If you want to know the secret and have some time, we can discuss but be ready for some work and patience.

    If you have the process HDMP file from C:\ProgramData\Microsoft\Windows\WER\ReportQueue, copy it someplace and send the link.  I should be able to pull a driver dll in about 5 minutes.

    Thanks


    Alan Morris formerly with Windows Printing Team


    Tuesday, May 8, 2018 5:42 AM
    Answerer