RPC Program Fails When Server Run Down Occurs (149846)
The information in this article applies to:
This article was previously published under Q149846 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.
RESOLUTIONSTATUS
This problem no longer occurs in Windows 98. To resolve this problem, install the current version of Windows. For information about the current version of Windows, visit http://www.microsoft.com/windows.
Modification Type: | Minor | Last Reviewed: | 9/22/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbAPI kbnetwork kbProgramming kbRPC KB149846 |
---|
|