Printing issues over network

[Alencar Chaddad]

Hello everybody,
First, I apologize about my bad english... I'm trying!

I'll try to tell you about my structure. I have a server
with W2K Server SP4 and 12 printers. It's a DELL Computer
OPTPLEX GX270. Six HP Deskjet (5550C, 950C, 895C and
720C), 3 HP LaserJet 4000, 1 Lexmark Optra T610 and 2
Epson FX-2180. We have 3 Trellis print servers and 1 HP
JetDirect.
Our print queue crashes frequently, specially when we have
print jobs submitted by SAP 4.6C users.
So, I restart the Print Spooler and TCP/IP Print Server
(we have LPR ports configured) services and OK. Spoolsv
takes too many CPU usage too.
Please, somewhere had any problems with print jobs like
these?
Thanks!

 

[Bill Peele [MS]]

--------------------
From: "Alencar Chaddad" <[email protected]>
Subject: Printing issues over network
Date: Thu, 29 Jan 2004 08:43:13 -0800
Newsgroups: microsoft.public.win2000.printing

Hello everybody,
First, I apologize about my bad english... I'm trying!

I'll try to tell you about my structure. I have a server
with W2K Server SP4 and 12 printers. It's a DELL Computer
OPTPLEX GX270. Six HP Deskjet (5550C, 950C, 895C and
720C), 3 HP LaserJet 4000, 1 Lexmark Optra T610 and 2
Epson FX-2180. We have 3 Trellis print servers and 1 HP
JetDirect.
Our print queue crashes frequently, specially when we have
print jobs submitted by SAP 4.6C users.
So, I restart the Print Spooler and TCP/IP Print Server
(we have LPR ports configured) services and OK. Spoolsv
takes too many CPU usage too.
Please, somewhere had any problems with print jobs like
these?
Thanks!
--

Alencar,

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.