Network Shared Printing Error Event ID 61



I had a fully functional printer share operational and running until recently.

After removing and reinstalling device drivers, ports and checking
securities, I cannot get this printer to cooperate. Nothing is being sent to
the printer. Not even test prints. Rebooted the server, restarted print
services, checked to ensure the virus scanner was not scanning the spooler
directories. What else?

The only user capable of successfully printing a test page is the
administrator. Sometimes a user can print a test page but this is only true
at the first attempt. Any further attempts to print a test result in the same
errors as described below.

The event info:

Event Type: Error
Event Source: Print
Event Category: None
Event ID: 61
Date: 11/23/2004
Time: 4:53:37 PM
User: Domina\rbauer
Computer: STKN001
The document Test Page owned by rbauer failed to print. Win32 error code
returned by the print processor: 29 (0x1d).

Which is followed by:

Event Type: Information
Event Source: Print
Event Category: None
Event ID: 10
Date: 11/23/2004
Time: 4:53:37 PM
User: Domain\rbauer
Computer: STKN001
Document 11, Test Page owned by rbauer was printed on HP2230 via port
HP2230_P1. Size in bytes: 24; pages printed: 1

And finally:

Event Type: Information
Event Source: Print
Event Category: None
Event ID: 13
Date: 11/23/2004
Time: 4:53:37 PM
Document 11, Test Page owned by rbauer was deleted on HP2230.

This is truely an unsatisfatory condition that is causing a great deal of
The server is a fresh build of W2K Server and running SP4

Shilpa Sinha [MSFT]


Maybe this will help.

If I have misunderstood your concern please let me know.

This issue is addressed in the Knowledge Base article 810647. A supported
fix is available for this issue. The hot fix has been packaged and placed
on an HTTP site for you to download.

Reference Link

After you install Windows 2000 Service Pack 3 (SP3) , you may see many
error event 61 entries in the System event log:

Event ID: 61
Event Type: Error
Event Source: Print
Description: The document document_name owned by username failed to print.
Win32 error code returned by the print processor: 63(0x3f)

Starting with SP3, every status other than 0 that is returned by the print
processor is logged as error event 61. However, some status codes are not
really errors. You must also evaluate the Win32 error code. For example,
for status code 63 (0x3f), type the following line at a command prompt:
net helpmsg 63
This returns a "Your file waiting to be printed was deleted" message. This
means that the user canceled the print job intentionally. This is already
logged as informational event 13.

After you install the hotfix that is described in this article, event 61 is
not logged for Win32 status 63 (0x3f).

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft
Windows 2000. For additional information, click the following article
number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported fix is now available from Microsoft, but it is only intended to
correct the problem that is described in this article. Apply it only to
computers that are experiencing this specific problem. This fix may receive
additional testing. Therefore, if you are not severely affected by this
problem, Microsoft recommends that you wait for the next Windows 2000
service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the fix. For a complete list of Microsoft Product
Support Services phone numbers and information about support costs, visit
the following Microsoft Web site:;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support
calls may be canceled if a Microsoft Support Professional determines that a
specific update will resolve your problem. The typical support costs will
apply to additional support questions and issues that do not qualify for
the specific update in question.

The English version of this fix has the file attributes (or later) that are
listed in the following table. The dates and times for these files are
listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference between
UTC and local time, use the Time Zone tab in the Date and Time tool in
Control Panel.

Date Time Version Size File name
04-Dec-2002 16:54 5.0.2195.6154 250,640 Localspl.dll
04-Dec-2002 16:54 5.0.2195.6047 79,632 Spoolss.dll
04-Dec-2002 16:54 5.0.2195.6044 84,752 Win32spl.dll

Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article. This problem was first
corrected in Microsoft Windows 2000 Service Pack 4.

For additional information about how to obtain a hotfix for Windows 2000
Datacenter Server, click the article number below to view the article in
the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product

Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.


Thanks for getting back to me. I'm not sure if this hotfix applies since SP4
has been installed.


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

Printing Error in Event Log 1
print spooler and server service problems 4
Remote printing? 2
Delayed Write of Data : Event ID:50 0
the Event Viewer error 1
MATS error 3
Suddenly unable to network 5
Event ID: 11 1