Tuesday, November 26, 2013

Print Server feeling melancholy?

I had a client contact me the other day with a print server that was feeling a little melancholy.  They said the server rebooted and then the printers were no longer listed.  All clients showed the printers were offline.  I did no find any good documents on the interwebz that helped so I thought it would be a good idea to post how we finally cheered the server up.

Error that showed when the server boots:
"Spooler SubSystem App has encountered a problem and needs to close"

Problem:
The print spooler service would start then immediately shutdown.

Step 1:  Check to see if there are any hung print jobs

  • Go to c:\%windir%\system32\spool\printers
  • Delete any files in that folder
  • If you want to do this from a CLI
    • NET STOP SPOOLER
    • DEL %SYSTEMROOT%\SYSTEM32\SPOOL\PRINTERS\*.* 
    • NET START SPOOLER
Step 2:  Backup then remove printers in the registry to find the culprit.
  • Win+R to bring up the run window
  • type regedit and press enter
  • go to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3
  • Right Click on said key and click export.  This will create a backup of this information that can be restored with a simple double-click so be sure to safe this in a safe place.
  • Now you can delete the subkey that you believe could be the culprit.  To test go to services and start the print spooler service.  If it shuts back down you can assume it was not the bad driver.  So back to the registry to delete another driver.
  • Once we've found the problem driver we can try to download an updated driver from the vendors website.
This should cheer that server right up.

.Net said .No so this says .Youbetterorelsebuddy

 I was having trouble with .net framework install on new computers.  I'm not sure why it didn't work repeatedly, but found that if y...