Local Print Spooler Service will Not Stay Running/localspl.dll Missing Details
Posted on 2011-09-10
1. I have a user in our office with a Dell Optiplex 980 running Windows 7 (32-bit) who suddenly lost connection to all her networked printers (HPs and Xerox).
2. When you go to Devices and Printers, none of the networked printers appear (she does not have any local printers) and click "Add Printer" an error message: "Windows can't open Add Printer. The local print spooler service is not running. Please restart the spooler or restart the machine."
3. I've restarted the spooler by using net start spooler and it is this service set to Automatic and to retry 2X if there is a failure.
4. Immediately upon clicking "Add Printer" the service drops and the error message already mentioned appears again.
The event viewer show error messages related to this: A) The print spooler failed to load a plug-in module localspl.dll error code 0xc1. This can occur because of system instability or a lack of system resources. B) The print spooler service terminated unexpectedly.
1) I've cleared out system32\spool\printers\*.*
2) I've compared the configuration of the print spooler of this computer with my own in the office (I have same model, operating system, etc) and they are identical (including HTTP and RPC dependencies.
3) The local company that supports our network has spent about an hour or two troubleshooting and have replaced the spoolsv.exe with a clean copy. This made no difference and they are stumped.
4) I attempted to add a printer through the Add Printer Wizard; same error message as if adding manually through Devices and Printers.
5) I've compared the versions of spoolsv.exe and localspl.dll on this computer with my own and I found that the spoolsv.exe files between the two machines match (same size, file version, etc.). However, when I compare the localspl.dll files, while the sizes are the same, the version on the affected machine is missing nearly all the details (Fileversion, Product Name, Product Version, FileName etc.) under Properties.
6) Does missing details on a DLL indicate corruption? Or is this normal? Could I copy the version from my computer and try it on the affected machine? (I would rename the one on the problem computer to LOCALSPL.OLD first).
7) Any thoughts on whether the problem is related to #6 above. The local company who supports our network has spent well over an hour on this problem and are stumped. They want to bring it into the office and do a repair Windows installation and tell us this will take 2-3 hours. I'd like to see if there is anything we can try first before we take this step and incur this cost and disruption while this machine is off site.