RPC_S_SERVER_TOO_BUSY on first connection.

[ed.gar]

Hi,

I have an RPC application, the server and client. The application works fine
on WinXP, 7 and Vista, but one of our customers reports that client app
fails to connect due to error 1723 - RPC_S_SERVER_TOO_BUSY. This is the
first connection from client app to server app. There are no other
connections.

The server app defines max calls as RPC_C_LISTEN_MAX_CALLS_DEFAULT:

status = RpcServerRegisterIfEx(
Remote_v1_0_s_ifspec, // Interface to register.
NULL, // Use the MIDL generated
entry-point vector.
NULL, // Use the MIDL generated
entry-point vector.
RPC_IF_ALLOW_CALLBACKS_WITH_NO_AUTH, // - security
RPC_C_LISTEN_MAX_CALLS_DEFAULT, // - max calls auto-listen
SecurityCallbackAuth); // - function pointer


The client app calls RpcBindingSetAuthInfo:


SCHANNEL_CRED_VERSION m_sc;

...

status = RpcBindingSetAuthInfo (m_remoteBinding, //
Binding
(RPC_CSTR) m_prnName, //
ServerPrincName
RPC_C_AUTHN_LEVEL_PKT_PRIVACY, //
AuthnLevel
RPC_C_AUTHN_GSS_SCHANNEL, //
AuthnSvc
&m_sc, //
AuthIdentity
RPC_C_AUTHZ_NAME //
AuthzService
);


The status is RPC_S_SERVER_TOO_BUSY.

Is there any common reason for RPC_S_SERVER_TOO_BUSY? I can't replicate this
issue. Do you have any hint? I don't have direct nor remote access to the
box causing problems.

Thanks,
Ed.

[Stefan Kuhr]

Hi Ed,

Never had that. Is this the result of the RpcBindingSetAuthInfo?

Does it go away if you implement a loop that retries after modest sleeps
inbetween retries?

--
S

[ed.gar]

> Never had that. Is this the result of the RpcBindingSetAuthInfo?
>
> Does it go away if you implement a loop that retries after modest sleeps
> inbetween retries?

Hi,

I still didn't get feedback from person who reported this issue, it might
have been an issue with network or corrupted system - I don't know. Besides,
only one person out of few hundred reported such a problem. I've tested my
software on XP, Vista an Win7 - no issues.

My guess is that it happened in RpcBindingSetAuthInfo. The connection is
initiated by clicking the "Connect" button in GUI, I do not try to
reconnect in case of error. User might try to connect few times, but it
can't drain system resources.

Thanks,
Ed.