RPC Program Fails When Server Run Down Occurs

 Last reviewed: November 26, 1997
Article ID: Q149846
The information in this article applies to:
  • Microsoft Windows 95

SYMPTOMS

When you run a multithreaded program that uses the RPC (Remote Procedure Call) API, or multiple RPC programs concurrently, one of the following error messages may occur:

  • Invalid Handle
  • RPC Failure

When these error messages occur, the connection to the RPC server is lost.

CAUSE

These errors may occur when all the following conditions exist:

  • The RPC server is a DCE (Distributed Computing Environment) server running a non-Microsoft operating system such as OS/2 or UNIX.
  • There are multiple RPC sockets (threads) being opened, either by a multithreaded RPC client program, or by multiple RPC client programs.
  • At least one of the RPC threads has been idle long enough for the RPC server to time out and automatically terminate (run down) the thread.

Under these conditions, the Windows 95 RPC run-time libraries do not properly shut down the RPC connection when the server times out and calls its rundown procedures. Subsequent attempts to create a new RPC connection or access an existing connection fail, generating one of the error messages listed above.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows 95. An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.

Additional query words: 95
Keywords : win95 kbnetwork kbprg
Version : 95
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 26, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.