Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Jobs Not Printed When Print Server Is Busy
Article ID: 232230 - View products that this article applies to.
This article was previously published under Q232230
Print jobs may intermittently not be printed when a print server is busy. When this occurs, event ID 10 is recorded in the event log with a message stating "0 bytes, 0 pages printed." Event ID 13 indicates that the print job has been deleted.
There is a problem with the local procedure call (LPC) code that can cause messages to be lost when the client and the server are the same process ID (PID) under certain circumstances.
Windows NT Server or Workstation 4.0To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
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 Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.
Article ID: 232230 - Last Review: June 6, 2012 - Revision: 4.0