Win32 error code

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi! Problem: Printing to an Intermec Printer fails. Error code:
- Event ID 61:
The document <filepath> owned by <username> failed to print. Win32 erro code
returned by the print processor: 5 (0x5).
After this error in the systemlog the spoller sends a printfile with the
size of 0 kb.

Printing to the printer has worked, but stoped working. We use the Generic
Text build in driver in Windows 2000. The print dissapear from the print que,
but since the file is 0 kb there is not much coming out of the printer.
I have check user rights on the filepath in the error message, and it looks
ok. We have about 10 InterMec printers and all generate the same error.
 
Hi! Thanks for your reply. I have read on the net that this message 5(5x0) is
access denied. The problem is that the error comes and goes. First we had it
once a week for two-three hours. Then last week printing was down three days,
now it works again. Could it be access denied when it comes and goes like
this?

Could it be related to nework problems? Or spooler?

Regards from Tore

Alan Morris(MSFT) said:
error 5 is access denied.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

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

Tore said:
Hi! Problem: Printing to an Intermec Printer fails. Error code:
- Event ID 61:
The document <filepath> owned by <username> failed to print. Win32 erro code
returned by the print processor: 5 (0x5).
After this error in the systemlog the spoller sends a printfile with the
size of 0 kb.

Printing to the printer has worked, but stoped working. We use the Generic
Text build in driver in Windows 2000. The print dissapear from the print que,
but since the file is 0 kb there is not much coming out of the printer.
I have check user rights on the filepath in the error message, and it looks
ok. We have about 10 InterMec printers and all generate the same error.
Click to expand...
Click to expand...
 
Back
Top