RPC Named Pipe Server Program Encounters Invalid Handle Exceptions

ID: Q225094

The information in this article applies to:

SYMPTOMS

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.


CAUSE

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.


RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual fix. For information on obtaining the latest service pack, please go to:

For information on obtaining the individual fix, 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:
http://www.microsoft.com/support/supportnet/overview/overview.asp

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be 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.

Additional query words: 


Keywords          : kbbug4.00 kbfix4.00 nt4sp5fix 
Version           : winnt:4.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: July 2, 1999