If you are experiencing issues with a Server 2008 R2 Print Server, and the print spooler service is continually going offline and stopping for unknown reasons, then follow this post to troubleshoot and resolve.

Note: Mileage may vary depending on your environment.

In our case, the print spooler is running into Event ID 337:

&nbsp;

<a href="http://egroup.jasonmangone.com/wp-content/uploads/2011/10/printspool1.jpg"><img class="alignleft size-full wp-image-5408" src="http://egroup.jasonmangone.com/wp-content/uploads/2011/10/printspool1.jpg" alt="" width="444" height="360" /></a>

 The issue is pointing to Active Directory and a further investigation of the following event log points us to our ultimate destination.

 <a href="http://egroup.jasonmangone.com/wp-content/uploads/2011/10/printspool2.jpg"><img class="alignleft size-full wp-image-5395" src="http://egroup.jasonmangone.com/wp-content/uploads/2011/10/printspool2.jpg" alt="" width="444" height="360" /></a>

&nbsp;

&nbsp;

With this information in hand, we know that we are specifically dealing with a WSD issue on the Print Server itself.

Log into the Print Server and review the properties of the Print Server. Be on the lookout specifically for "WSD" under the Ports tab.<a href="http://egroup.jasonmangone.com/wp-content/uploads/2011/10/printspooler31.jpg"><img class="alignleft size-full wp-image-5399" src="http://egroup.jasonmangone.com/wp-content/uploads/2011/10/printspooler31.jpg" alt="" width="444" height="360" /></a>

&nbsp;

In this case we have one. This is the culprit. If you scan through your printers, you should find a printer that is not configured via an IP address like the others. He’ll be configured to use this port:

&nbsp;

<a href="http://egroup.jasonmangone.com/wp-content/uploads/2011/10/printspooler4.jpg"><img class="alignleft size-full wp-image-5403" src="http://egroup.jasonmangone.com/wp-content/uploads/2011/10/printspooler4.jpg" alt="" width="444" height="360" /></a>

Reconfigure the currently configured “WSD Printer” as an IP based Printer. Then circle back and delete the WSD port, and remove the WSD port from the Print Server Properties.

&nbsp;

You should now see your PrintSpooler service run just fine.