Print Spooler Stopping automatically

[Fran Rhomberg]

Hi,
I have 4 Windows 2000 Advanced Servers Running in
Terminal Server Application mode. The Print Spool
Service continually stops throughout the day. No viruses
are detectd on these servers. Any suggestions? Thanks.
- FR

 

[Debbie Welsh]

Fran:

I'm having the exact same problem. Spooler stops almost
every day in the morning around 6:30am. Can't figure out
why. We have about 20 printers we are supporting, most
HP. If you figure anything out let me know and I'll do
the same.

Debbie
(e-mail address removed)

 

[joseph nader]

I had similar problems , my servers were stopping once a day , not as often
as yours , I can not remember exactly what was the cause, but I had many
citrix client printing continously.
This is a temporary solution if you like until I remember what was the cause
:

I create a little batch job to check the spooler every 5 min and if down it
started again and send me a message Here is the script

@echo off

REM last edited by JN - july 2003
REM a weekly script will set the blat server to the mail server
REM this script checks the spooler every five min and attempt to start it
REM note that it is better to wait 10 sec or so after a spooler is down
REM and than start it again The sleep command is borrowed from cygwin

net start | find "Print Spooler"
if %errorlevel%==0 goto end
sleep 10
net start "Print Spooler"
if %errorlevel%==0 goto end
blat file1 -t (e-mail address removed) -noh2

:end

 

[Kyle]

Our print spooler is stopping as well, about mid-
afternoon every day.

EventID 2510 occurs at roughly the time the spooler stops.

Event Type: Error
Event Source: Server
Event Category: None
Event ID: 2510
Date: 12/14/2000
Time: 2:06:11 PM
User: N/A
Computer: Computer_Name
Description: The server service was unable to map error
code 1722.

This is what EventID.net says as a possible problem:

1722 = "The RPC server is unavailable." - This problem
is caused by the JetAdmin port monitor being corrupted or
outdated. See Q199915 and Q158751.

Damned if I can update the JetADmin port monitor though!

Any thoughts?
Kyle
(e-mail address removed)

 

[Fran Rhomberg]

I have a possible resolution. This situation finally
generated an Event Viewer occurance:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 1/22/2004
Time: 10:01:19 AM
User: N/A
Computer: XXXXXX
Description:
The Print Spooler service terminated unexpectedly. It
has done this 5 time(s). The following corrective action
will be taken in 0 milliseconds: No action.
After performing a search, I found the following
KBArticle:

http://support.microsoft.com/default.aspx?scid=kb;en-
us;820550

You have to contact Microsoft to obtain this hotfix. I
installed this around 11:00AM this morning and the print
spooler hasn't crashed yet. Prior to this patch, it was
crashing every 20 minutes. I still think it needs more
time to declare it a solid fix, but I am optimistic.
Hope this helps anyone else that is experiencing the same
problem.
- FR

 

[Fran Rhomberg]

Debbie,
I posted a possible resolution (see the response to my
original post). This may or may not help you. You
indicated that the spooler crashes for you once per day.
Mine was happening every 20 ot 30 minutes, on multiple
terminal servers. Check your event viewer to see if you
can obtain an EventID for your spooler crash. Hope this
helps.
- FR

 

[Fran Rhomberg]

Joseph,
Nice batch file. Thanks. I'm trying to make this work,
so I don't have to babysit my servers until I find the
solid fix. I may have the fix, provide from Microsoft -
I'm testing it right now. Regarding your batch file, how
do you make it check the spooler every 5 minutes? I
setup the batch file to run in the scheduler, however it
is not launching the sleeper. I downloaded the sleeper
application and placed it in the recommended folder, but
it doesn't seem to re-check after the first check.
- FR

 

[Vanessa]

Hello,

I've been having the same problem as a number of people
with the Print Spooler stopping periodically throughout
the day. I'm new to the server world and frantically
trying to fix the problem. As for the Event Id... the
error that was generated in my Event Viewer had an Id
number of 54.. will this hotfix work for me? Any
suggestions or help would be greatly appreciated.

Thanks,
Vanessa