The information in this article applies to:
SYMPTOMS
After a while, all Windows NT workstations are no longer able to submit
print jobs to a print server. You may receive the following error message:
A network trace of the traffic between a client and the print server shows that the server is returning STATUS_PIPE_NOT_AVAILABLE to the client whenever it tries to connect to the spoolss RPC server. File sharing and other remote administrative tasks against the server are not affected. Downlevel (non-RPC) clients can still print, and print jobs submitted from the server itself also print correctly. This tends to occur more frequently in the early evening as users are leaving work. CAUSE
Workstations are being powered off without being properly shut down.
Specifically, the problem arises if the workstation had one or more printer
property windows open. The server attempts to perform an RPC print
notification update to the client, but, because the client was turned off,
the underlying transport times out the connection request. During this
period, the RPC run time is unable to create any named pipe instances for
new incoming print requests.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the
Microsoft Knowledge Base: Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack STATUSMicrosoft has confirmed this to be a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4. Additional query words:
Keywords : NT4SP4Fix kbbug4.00 kbfix4.00.sp4 |
Last Reviewed: January 20, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |