--------------------
From: "pedjasan" <
[email protected]>
Subject: add printer
Date: Fri, 30 Jan 2004 01:10:14 -0800
Newsgroups: microsoft.public.win2000.printing
When run add printer servicess Print spooler crash
(spoolsv.exe crash)
--
The most common causes of the Print Spooler service stopping are printer drivers and custom port monitors. If a new
printer or printer driver was added recently try removing it to see what happens. We can also check for a ustom port
monitor by looking at HKLM\System\CurrentControlSet\Control\Print\Monitors. If there is a custom port monitor we can
export a copy of that sub-key, as a backup, and then delete the sub-key to remove the custom port monitor. We would
then need to stop and restart the Print Spooler service for this change to take affect.
If this does not resolve the issue the Print Spooler service should add an entry to the Dr Watson log and generate a User
dump file, assuming Dr Watson is still the system's default debugger and it is setup to generate the User dump file, when it
stops. The log and the dump can be used to try and determine why the Print Spooler stopped.
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.
