Printer servers are prone to an array of software problems, which can cause printer spooler not working error on Windows Server 2008 R2. Its first sign is an unexpected print downtime for the end users that rely on a specific printer server for network printing. In order to reboot the spooler through the server system, navigate to the list of processes below Administrative Tools on Windows Server 2008 R2. From the list, locate Print Spooler and choose Restart from the context menu.
Rebooting the printer spooler might help fix the error, but if the spooler crashes frequently on Windows Server 2008 (second release) you will need advanced troubleshoots. Some printer drivers may lead to memory corruption or can be incompatible with other devices in the network. If you feel printer driver is corrupt, follow the below steps to clear the spooler error.
Enable Printer Driver Isolation on Windows Server 2008 R2. This is highly recommended by tech professionals who are into network printer troubleshooting especially if spooler crashes on the server. Doing this will avoid the printer drivers from interfering with the printing process done through software.
Note that it can also be the print jobs in the print queue of the spooler that may cause it to crash on Server 2008 R2. In order to identify that, open the print queue and check for stuck printing tasks if any or ‘ghost’ print jobs and cancel them. If they do not exist on spooler software, keep an eye on the queue just as client computers print in order to know if faulty connections cause malformed print jobs. To resolve the connectivity problem, you may have to delete the printers from the server and then install them one by one.