Print jobs processed by Print Spooler but nothing comes out at Physical Printer.
Print Cluster - Windows 2003. - three node cluster.
User sends print jobs from their desktop > It comes to Print Server (Windows 2003) > Spooler at Windows 2003 spools and job and send to printer but nothing comes out at Printer.
There is no error message nothing. An event is logged in Event viewer: Event ID 6161.
Description:
"The document \\document name owner by user name failed to print on printer printer_name. Data type: NT EMF 1.008. Size of the spool file in bytes: 192624. Number of bytes printed: 0. Total number of pages in the document: 3. Number of pages printed: 0. Client machine: \\ip_address. Win32 error code returned by the print processor: 0. The operation completed successfully."
"The document \\document name owner by user name failed to print on printer printer_name. Data type: NT EMF 1.008. Size of the spool file in bytes: 192624. Number of bytes printed: 0. Total number of pages in the document: 3. Number of pages printed: 0. Client machine: \\ip_address. Win32 error code returned by the print processor: 259. No more data is available.
Thanks
SP
User sends print jobs from their desktop > It comes to Print Server (Windows 2003) > Spooler at Windows 2003 spools and job and send to printer but nothing comes out at Printer.
There is no error message nothing. An event is logged in Event viewer: Event ID 6161.
Description:
"The document \\document name owner by user name failed to print on printer printer_name. Data type: NT EMF 1.008. Size of the spool file in bytes: 192624. Number of bytes printed: 0. Total number of pages in the document: 3. Number of pages printed: 0. Client machine: \\ip_address. Win32 error code returned by the print processor: 0. The operation completed successfully."
"The document \\document name owner by user name failed to print on printer printer_name. Data type: NT EMF 1.008. Size of the spool file in bytes: 192624. Number of bytes printed: 0. Total number of pages in the document: 3. Number of pages printed: 0. Client machine: \\ip_address. Win32 error code returned by the print processor: 259. No more data is available.
Thanks
SP
Anonymous (Last update 2/21/2007):
Check that the RAW or LPT port is opened between firewalls. The default port for RAW is 9100.
Eric Peeters (Last update 11/24/2006):
- Error code: 61 - The printer port was set up as a TCP/IP HP print server and the configuration utility used the printer's FQDN as address. Replacing the FQDN with the actual IP address of the printer resolved this problem.
Jonathan L. Raper (Last update 10/20/2006):
I had this exact same problem with a Xerox Phaser 8550DP. Sometimes, the job would print after trying to restart the print job, sometimes it would not. Then sometimes, after throwing this error, the job would print. After contacting Xerox tech support, I went into the properties of the printer, selected the "Ports" tab and clicked on "Configure Port". I changed the protocol from Raw to LPR and also set the queue name to auto (all lowercase). I did not change anything else. This appears to have fixed the problem.
Anonymous (Last update 9/2/2006):
We received this error when we were trying to print to a networked HP Photosmart 8400. Users were not able to print but the local admin printed without errors. After installing the printer driver on the server, the software detected the network printer and added a HP port. I changed the port to a standard tcp/ip port and users were then able to print.
Mihai Andrei (Last update 2/10/2006):
From a newsgroup post: "Please grant Full Control permissions to the C:\WINDOWS\System32\spool\
From a newsgroup post: "As article M208820 suggested, I turned off bidirectional printing for my networked HP printer, and the problem was solved".
Robert Dill (Last update 12/20/2005):
I fixed the problem with the Brother printer by installing the generic Brother PCL driver. After installing this as a new printer in the Add New Printer section, the old printer (which had 19 "deleting" documents stuck in it) was clear and now works great.
Ionut Marin (Last update 10/24/2005):
From a newsgroup post: "I encountered this problem on a Windows 2003 Server. In order to fix this problem I used the cleanspl.exe tool from the Windows 2003 resource tools and removed everything from the spooler except standard TCP/IP and USB. I then setup a test printer using a standard TCP/IP connection and printing started working again. I think that the problem was caused by one of our staff members, who had installed a non-compliant Windows 2003 driver".
From a newsgroup post: "I have performed a lot of research on printing issue after installing M896423. Many cases indicated that M896423 might cause some printers to stop working. There are two methods to resolve this issue (which have been confirmed to work on similar issues):
1. Follow the suggestions in M832219.
2. Install a new version printer driver.
The security update M896423 makes the printer spooler more secure. However, some old drivers cannot work with the updated spooler".
Woodrow Wayne Collins (Last update 6/24/2004):
This event might occur after installing the hotfix provided in article M824339.
Check that the RAW or LPT port is opened between firewalls. The default port for RAW is 9100.
Eric Peeters (Last update 11/24/2006):
- Error code: 61 - The printer port was set up as a TCP/IP HP print server and the configuration utility used the printer's FQDN as address. Replacing the FQDN with the actual IP address of the printer resolved this problem.
Jonathan L. Raper (Last update 10/20/2006):
I had this exact same problem with a Xerox Phaser 8550DP. Sometimes, the job would print after trying to restart the print job, sometimes it would not. Then sometimes, after throwing this error, the job would print. After contacting Xerox tech support, I went into the properties of the printer, selected the "Ports" tab and clicked on "Configure Port". I changed the protocol from Raw to LPR and also set the queue name to auto (all lowercase). I did not change anything else. This appears to have fixed the problem.
Anonymous (Last update 9/2/2006):
We received this error when we were trying to print to a networked HP Photosmart 8400. Users were not able to print but the local admin printed without errors. After installing the printer driver on the server, the software detected the network printer and added a HP port. I changed the port to a standard tcp/ip port and users were then able to print.
Mihai Andrei (Last update 2/10/2006):
From a newsgroup post: "Please grant Full Control permissions to the C:\WINDOWS\System32\spool\
From a newsgroup post: "As article M208820 suggested, I turned off bidirectional printing for my networked HP printer, and the problem was solved".
Robert Dill (Last update 12/20/2005):
I fixed the problem with the Brother printer by installing the generic Brother PCL driver. After installing this as a new printer in the Add New Printer section, the old printer (which had 19 "deleting" documents stuck in it) was clear and now works great.
Ionut Marin (Last update 10/24/2005):
From a newsgroup post: "I encountered this problem on a Windows 2003 Server. In order to fix this problem I used the cleanspl.exe tool from the Windows 2003 resource tools and removed everything from the spooler except standard TCP/IP and USB. I then setup a test printer using a standard TCP/IP connection and printing started working again. I think that the problem was caused by one of our staff members, who had installed a non-compliant Windows 2003 driver".
From a newsgroup post: "I have performed a lot of research on printing issue after installing M896423. Many cases indicated that M896423 might cause some printers to stop working. There are two methods to resolve this issue (which have been confirmed to work on similar issues):
1. Follow the suggestions in M832219.
2. Install a new version printer driver.
The security update M896423 makes the printer spooler more secure. However, some old drivers cannot work with the updated spooler".
Woodrow Wayne Collins (Last update 6/24/2004):
This event might occur after installing the hotfix provided in article M824339.
ASKER
I have already read above suggestions before posting the question. My problem had resolved after restarting Print Spooler service.
Can anyone please elaborate as to know what caused this?
Can anyone please elaborate as to know what caused this?
ASKER
As per investigation:
ERROR_NO_MORE_ITEMS (259)
This error code means that no more data is available. You may receive this error code if a program or a printer driver component sends an incomplete spool file to the print spooler on the print server. Therefore, the file does not print. Frequently, you can resolve this problem by installing the driver from the operating system CD.
ERROR_SUCCESS (0)
This error code means that the operation completed successfully. You may receive this error code if an underlying component such as GDI returns a failure but does not set the last error. This error is difficult to diagnose unless you reproduce the problem. Frequently, you can resolve this problem by installing the driver from the operating system CD.
Then why restarting Print Spooler service resolved the problem? Does Print Spooler service clears the memory and print drivers from memory after you restart the service?
I'm not sure about this one but need to find the root cause.
Thanks for your help.
ERROR_NO_MORE_ITEMS (259)
This error code means that no more data is available. You may receive this error code if a program or a printer driver component sends an incomplete spool file to the print spooler on the print server. Therefore, the file does not print. Frequently, you can resolve this problem by installing the driver from the operating system CD.
ERROR_SUCCESS (0)
This error code means that the operation completed successfully. You may receive this error code if an underlying component such as GDI returns a failure but does not set the last error. This error is difficult to diagnose unless you reproduce the problem. Frequently, you can resolve this problem by installing the driver from the operating system CD.
Then why restarting Print Spooler service resolved the problem? Does Print Spooler service clears the memory and print drivers from memory after you restart the service?
I'm not sure about this one but need to find the root cause.
Thanks for your help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://www.eventid.net/display.asp?eventid=6161&eventno=4177&source=Print&phase=1