--------------------
From: "Mike Trzinski" <
[email protected]>
Subject: spoolsv.exe will not stay up and running
Date: Thu, 11 Mar 2004 06:43:02 -0800
Newsgroups: microsoft.public.win2000.printing
The printer subsystem(spoolsv.exe) keeps going down with
no error to the event log. I am getting an access
violation error in the Dr. Watson log. All MS web site
says is to apply SP4, which I have done with no avail.
Anyone got an idea of why this keeps happening?
Thanks,
Mike
---
Mike,
The most common causes of the Print Spooler service stopping are printer drivers, third-party custom port monitors and
third-party print providers. If a new printer or printer driver was added recently try removing it to see what happens.
Check the following registry key for third-party monitors, removing any non-default monitors after exporting the key as a
backup:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors
The default port monitors are:
AppleTalk Printing Devices (When Services for Macintosh is installed)
BJ Language Monitor
Local Port
PJL Language Monitor
Standard TCP/IP Port
USB Monitor
Windows NT Fax Monitor
LPR Port
Check the following registry key for third-party print providers, removing any non-default print providers after exporting the
key as a backup:
KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers
The default print providers are:
Internet Print Provider
LanMan Print Services
We would then need to stop and restart the Print Spooler service for these changes to take affect.
If this does not resolve the issue, along with the Dr Watson log a User dump file should have been generated. The log and
the dump can be used to try and determine why the Print Spooler stopped but you may need to open a support incident to
have the dump analyzed.
Bill Peele
Microsoft Enterprise Support
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread
from which they originated.
