RPC Named Pipe Server Program Encounters Invalid Handle Exceptions

This article was previously published under Q225094
This article has been archived. It is offered "as is" and will no longer be updated.
A program using the remote procedure call (RPC) named pipe server transport encounters an excessive amount of invalid handle exceptions when attempting to close a remote connection. The RPC program does not stop responding (hang) because of the structured exception handling surrounding the RPC call, but may affect performance and the logic of the server program.
This problem occurs because the Windows NT RPC Named Pipe Server transport is inadvertently receiving an RPC fault over the network. This fault is reported as an invalid handle because of a problem with identifying the client session.
To 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:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
Microsoft has confirmed that this is a problem in Windows NT 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.
More information
This problem may cause the Spooler service (Spoolss.exe) to encounter excessive invalid handle exceptions, which can be observed by running the process under a debugger. The exceptions negatively affect the service.

Article ID: 225094 - Last Review: 11/02/2013 23:37:00 - Revision: 3.0

  • Microsoft Windows NT Server 4.0 Standard Edition
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB225094