W2003 print problem

P

Peter Lawton

We've got a W2003 print server printing to a lot of different networked
printers including HP deskjets.

Sometimes when a user or an administrator tries to print the print job
appears briefly then disappears without printing.

There's an error in the event log:-

Source: Print
Event ID: 61
Description:
The document Test Page owned by username failed to print on printer
printername. Win32 error code returned by the print processor: 5. Access is
denied.

This problem only seems to happen to the networked Deskjets (1100 and 5850)
and only happens occasionally, most of the time they work OK, the only way
to use the printer again is to re-start the print spooler on the print
server, which we can only do out of hours.

There's plenty of free memory and disc space on the server

Thanks
 
S

Shilpa Sinha [MSFT]

Hi

Maybe this will help

When you print to a file in Windows Server 2003, you receive Event ID 61

SUMMARY
========
This article discusses Event ID 61. This event appears in the system event
log when you are experiencing printing problems. This event may appear if
you print to a file, and you do not specify the file's full path. The event
may also appear because of a problem with a driver or with a port monitor.

SYMPTOMS
=========
When you print multiple jobs at the same time to a specific file name, and
you do not specify the full path of the .prn file, the .prn file will be
created in the %Systemroot%\System32 folder. You may receive an
"ACCESS_DENIED" error message, your computer may stop responding, and
printing may stop. The system event log may have one or more instances of
the following event log message:

Event Type: Error
Event Source: Print
Event Category: None
Event ID: 61
Description: The document document name owned by username failed to print
on printer printer name. Win32 error code returned by the print processor:
3003. A StartDocPrinter call was not issued.

You may also notice that use of paged-pool memory is high.

CAUSE
=====
This problem occurs when you do not specify the full path of the file you
are printing to. If a file is specified as filename.prn, the file will be
created in the %Systemroot%\System32 folder. Various users will have
different rights to this folder. If you print to a file that is located in
this folder, you may receive an "ACCESS_DENIED" error message. In this
case, if you continue to write jobs to this same file, the spooler
continues to try to print the job. This scenario can exhaust page-pooled
memory and cause your computer to stop responding.

RESOLUTION
========
To resolve this problem, provide a specific destination when you create a
local file as the destination of a local port print job. Do not use the
system folders.

MORE INFORMATION
==============
Third-party print drivers and third-party port monitors may cause the
majority of Event ID 61 error messages.

For additional information about Event ID 61 log entries, click the
following article number to view the article in the Microsoft Knowledge
Base:

810647 - The system event log contains many Event 61 entries
http://support.microsoft.com/default.aspx?kbid=810647


For information about how to contact your vendor, click the appropriate
article number in the following list to view the article in the Microsoft
Knowledge Base:

65416 - Hardware and Software Third-Party Vendor Contact List, A-K
http://support.microsoft.com/default.aspx?kbid=65416

60781 - Hardware and Software Third-Party Vendor Contact List, L-P
http://support.microsoft.com/default.aspx?kbid=60781

60782 - Hardware and Software Third-Party Vendor Contact List, Q-Z
http://support.microsoft.com/default.aspx?kbid=60782

You may also receive the following Event ID 61 log entries when you print:

Event Source: Print
Event ID: 61
Description: The document DocumentName owned by UserName failed to print.
Win32 error code returned by the print processor: 63 (0x3f). Error code 63
- job in the queue was deleted.

Event Source: Print
Event ID: 61
Description: The document DocumentName owned by UserName failed to print on
printer 3003 (0xbbb). Win32 error code returned by the print processor: %5
Error code 3003 - A StartDocPrinter call was not issued.

Event Source: Print
Event ID: 61
Description: The document ApplicationName - DocumentName owned by UserName
failed to print. Win32 error code returned by the print processor: 1392
(0x570).

Event Source: Print
Event ID: 61
Description: The document ApplicationName - DocumentName owned by UserName
failed to print. Win32 error code returned by the print processor: 259
(0x103).

Event Source: Print
Event ID: 61
Description: The document ApplicationName - DocumentName Print Job owned by
UserName failed to print. Win32 error code returned by the print processor:
259.

Event Source: Print
Event ID: 61
Description: The document ApplicationName - DocumentName Print Job owned by
UserName failed to print. Win32 error code returned by the print processor:
29.

Event Source: Print
Event ID: 61
Description: The document ApplicationName - DocumentName Print Job owned by
UserName failed to print. Win32 error code returned by the print processor:
119 (0x77).

Error code 119 appears if the printer is offline.

Event Source: Print
Event ID: 61
Description: The document ApplicationName - DocumentName owned by UserName
failed to print. Win32 error code returned by the print processor: 998
(0x3e6).

Check the client computer print driver. If the driver is a third-party
print driver, try the corresponding Microsoft print driver.

Event Source: Print
Event ID: 61
Description: The document ApplicationName - DocumentName owned by UserName
failed to print. Win32 error code returned by the print processor: 1813
(0x715).

Event Source: Print
Event ID: 61
Description: The document ApplicationName - DocumentName owned by UserName
failed to print on printer 122 (0x7a).
Win32 error code returned by the print processor: 1392 (0x570).
Win32 error code returned by the print processor: 259 (0x103).
Win32 error code returned by the print processor: 63 (0x3f).
Win32 error code returned by the print processor: 3003 (0xbbb).

The information in this article applies to:

o Microsoft Windows Server 2003, Standard Edition
o Microsoft Windows Server 2003, Enterprise Edition

Reference Link:
=============
http://support.microsoft.com/default.aspx?scid=kb;en-us;838172&Product=winsv
r2003

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

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

Top