Event 7031 and event 61 on windows 2000 print server: what to do?

P

Pierre

Hi out there,

our windows 2000 print server has really been acting up
recently. It was deployed around the holidays with
service pack 3. I use standard TCP/IP ports to reach the
printers and most of the drivers are PCL 6 with a couple
of postscript exceptions. I originally settled on PCL
because of many issues using postscript on the older
print server. We've been getting this message
intermittently:

The document Microsoft Word - filename.doc owned by
username failed to print. Win32 error code returned by
the print processor: 122 (0x7a).

now this seems to compound into the following message:

The Print Spooler service terminated unexpectedly. It
has done this 1 time(s). The following corrective action
will be taken in 60000 milliseconds: Restart the service.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

The only info I've found is on the latter. It suggests
finding updated versions of the localsp.dll, spoolss.dll
and win32spl.dll files but even after upgrading to
Service Pack 4, these files are still too old.

any suggestions you can provide would be helpful.
 
M

moray

I have the same problem, and have found kb article 820550
which addresses this exact issue. I'm trying to find the
hotfix in question to test.

hope this helps
Moray
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Print Spooler Event ID 7031 6
Print spooler terminated event ID 7031 1
Print spooler crash on 2003 Server SP2 8
Print Spooler Terminating. Event ID 7031 2
Event ID 61 - Print jobs stuck on 'spooling' 0
Print Spooler terminate with Event ID 7031 0
Print Spooler Stopped 3
The Print Spooler service terminated unexpectedly. 7031 2

Top