Discussion Locked

W2K Server Printer subsystem unavailable

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After installing an updated Toshiba printer driver on a W2K Server we have lost all printers on the server and in Start / Settings / Printers we have only Add Printer. Any attempt to add a new printer results in messages about lack of resources andprinter subsystem being unavailable. Starting the printer subsystem does NOT help. Right mouse clicking in the Printers windows and selecting Server Properties also fails.

Any suggestions as to how we move forward, delete the printer driver please. We are currently unable to delete the printer driver as it is not there and cannot install a new driver either.

Any help gratefully received

Many thanks

Bryan

Any suggestions

5 replies

by timwalsh

The Printer Spooler service needs to be restarted.

Go to Start Menu | Programs | Administrative Tools | Services - search for Print Spooler. It should be set to start automatically. If the Status column says started, you need to right-click on the service name, and choose "Restart." If there is nothing in the Status column, right-click and choose "Start."

Hope this helps.

by bryan.scaife

This was the first thing I tried - the service appeared stopped and started successfully without resolving the issue (I also tried stopping/restarting)

by curlergirl

Further to Tim's answer - if the print spooler service is hung (i.e., it says it's started but you can't either stop or restart it), then you will probably have to reboot the server to get it restarted. Hope this helps!

by bryan.scaife

Tried this one as well with no success.
However from an earlier question in TechRepublic we investigated the Bitware problem, I navigated the directory and found a rather likeley Toshiba candidate in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Monitors
I had backup up the registry on the last site visit and decided to delete this key - instant success. The print subsystem worked and allowed the printers to be edited - I deleted the errant printers and I used the server properties tab to clean out all the contentious drivers ready for a clean install with approved drivers tommorrow
The article referred to that gave me this clue was:
http://support.microsoft.com/?kbid=257859

This discussion is closed to new replies.