PRB: "RPC_S_SERVER_TOO_BUSY" When Binding to Server on ncacn_np

ID: Q176734

The information in this article applies to:

• Microsoft Win32 Software Development Kit (SDK)

SYMPTOMS

If more than one client connects to an RPC server using the ncacn_np protseq at nearly the same time, the call may fail with error code 1723:

   RPC_S_SERVER_TOO_BUSY

CAUSE

This is due to the way the named pipe transport works. The server side creates an instance of the pipe for use by clients. The first client to attempt a connection is associated with that instance. To allow another client to connect, the server must create another instance of the named pipe. If another client attempts to connect before the new instance is created, the server appears (to the second client) not to be accepting connections.

RESOLUTION

RPC clients should be written to handle a situation where the server is too busy to accept a connection because it is highly likely that there might be too many clients attempting to establish a connection at a given time. Options for handling this situation include automatically retrying, prompting the user for a course of action, or failing.

STATUS

This behavior is by design.

Additional query words:

Keywords          : kbnetwork kbAPI kbRPC kbSDKPlatform kbGrpNet 
Issue type        : kbprb

Last Reviewed: July 31, 1998