G
Guest
I have been struggling with the following printing problem for a few weeks
and I have not been able to get it resolved. The problem is occuring on a
Windows 2000 Terminal server with SP4 installed.
Begining about a month ago, I began getting complaints from users that their
printers would suddenly disappear when the had an RDP connection to the
server. I investigated the problem and discovered that the Print Spooler
service had failed and remained stopped. I then restarted the Print Spooler
service and printing was restored.
When investigating the occurs I have noticed the following Events occur in
the System Event log (in order):
1. EVENT ID 7031 (1 instance)
"The Print Spooler service terminated unexpectedly. It has done this 1
time(s). The following corrective action will be taken in 0 milliseconds:
Run the configured recovery program. "
2. EVENT ID 2510 (1 instance)
"The server service was unable to map error code 1727."
NOTE: 'net helpmsg 1727' returns 'The Remote Procedure Call failed and did
not execute'
3. EVENT ID 2510 (Multiple repeating instances until print spooler is
restarted)
"The server service was unable to map error code 1722. "
NOTE: 'net helpmsg 1722' returns 'RPC server is unavailable'
Whenever this problem occurs, there is an entry written to the Dr. Watson
log that indicates that the spoolsv.exe had crashed. The last event list
above will repeat multiple times until the print spooler has been restarted.
I have researched the following events, but did not find anything that
matches my envioroment. For example, many people suggest that it is a
problem with HP JetAdmin software, but this server does not run any JetAdmin
software.
In addition to the Print Spooler dying, clients have a very difficult time
installing printers. From Windows XP clients, I will browse to the server
and double click on a printer in hopes of getting the printer installed. It
will then take a very long time (at least 7 minutes) to install the printer
on the local PC. Then with the printer finally installed, if you try to view
the properties of the printer it will also take an extremely long time to
open. I initially thought that this could be a DNS issue, but I have
verified that the client PCs are using the correct DNS server. In addition,
clients can browse files and other network computers without this extreme
delay.
Most of the printers in the network are HP (6 out of 7 I believe). I have
downloaded and installed the latest drivers for all printers. Since
completing this, the Print Spooler service continues to die. I have also
tried moving the Print Spooler directory to another partition on the server,
still no luck.
Finally, I have tried to configure the Print Spooler service to run a batch
file to restart itself after it fails. This does not even "correct" the
issue. A user has to go to the server and manually click the batch file that
stops the Spooler service and starts it again.
I am running out of ideas. My next step is to remove all the printers and
add them in again. But before I do that I was wondering if anyone had any
suggestions that might help with my problem. The server is in a busy
production enviroment and this could cause quite an interuption while I do
this.
Also, if I do need to remove all the printers and uninstall them, is there
some kind of tool available that I can run to completely remove all printers
and their associated printer drivers from the system. I want to make sure I
completely clean everything related to printers off so I only have to do this
once. I had heard that there is a support tool for Windows 2003 Server that
can do this, but I am not aware of anything for Windows 2000.
I appreciate any help and suggestions that you can offer. I have tried to
be as detailed as possible, but if you need some additional information
please let me know.
Jason
and I have not been able to get it resolved. The problem is occuring on a
Windows 2000 Terminal server with SP4 installed.
Begining about a month ago, I began getting complaints from users that their
printers would suddenly disappear when the had an RDP connection to the
server. I investigated the problem and discovered that the Print Spooler
service had failed and remained stopped. I then restarted the Print Spooler
service and printing was restored.
When investigating the occurs I have noticed the following Events occur in
the System Event log (in order):
1. EVENT ID 7031 (1 instance)
"The Print Spooler service terminated unexpectedly. It has done this 1
time(s). The following corrective action will be taken in 0 milliseconds:
Run the configured recovery program. "
2. EVENT ID 2510 (1 instance)
"The server service was unable to map error code 1727."
NOTE: 'net helpmsg 1727' returns 'The Remote Procedure Call failed and did
not execute'
3. EVENT ID 2510 (Multiple repeating instances until print spooler is
restarted)
"The server service was unable to map error code 1722. "
NOTE: 'net helpmsg 1722' returns 'RPC server is unavailable'
Whenever this problem occurs, there is an entry written to the Dr. Watson
log that indicates that the spoolsv.exe had crashed. The last event list
above will repeat multiple times until the print spooler has been restarted.
I have researched the following events, but did not find anything that
matches my envioroment. For example, many people suggest that it is a
problem with HP JetAdmin software, but this server does not run any JetAdmin
software.
In addition to the Print Spooler dying, clients have a very difficult time
installing printers. From Windows XP clients, I will browse to the server
and double click on a printer in hopes of getting the printer installed. It
will then take a very long time (at least 7 minutes) to install the printer
on the local PC. Then with the printer finally installed, if you try to view
the properties of the printer it will also take an extremely long time to
open. I initially thought that this could be a DNS issue, but I have
verified that the client PCs are using the correct DNS server. In addition,
clients can browse files and other network computers without this extreme
delay.
Most of the printers in the network are HP (6 out of 7 I believe). I have
downloaded and installed the latest drivers for all printers. Since
completing this, the Print Spooler service continues to die. I have also
tried moving the Print Spooler directory to another partition on the server,
still no luck.
Finally, I have tried to configure the Print Spooler service to run a batch
file to restart itself after it fails. This does not even "correct" the
issue. A user has to go to the server and manually click the batch file that
stops the Spooler service and starts it again.
I am running out of ideas. My next step is to remove all the printers and
add them in again. But before I do that I was wondering if anyone had any
suggestions that might help with my problem. The server is in a busy
production enviroment and this could cause quite an interuption while I do
this.
Also, if I do need to remove all the printers and uninstall them, is there
some kind of tool available that I can run to completely remove all printers
and their associated printer drivers from the system. I want to make sure I
completely clean everything related to printers off so I only have to do this
once. I had heard that there is a support tool for Windows 2003 Server that
can do this, but I am not aware of anything for Windows 2000.
I appreciate any help and suggestions that you can offer. I have tried to
be as detailed as possible, but if you need some additional information
please let me know.
Jason