| Previous | Next |
| RPC_S_SERVER_UNAVAILABLE | RPC_S_INVALID_NETWORK_OPTIONS |
RPC_S_SERVER_TOO_BUSY
RPC_S_SERVER_TOO_BUSY means that the server could not accept or complete the RPC call because it was too busy. It is different from an unreachable server: the service was contacted but lacked capacity for this request at that time.
Safe recovery depends on the operation
A retry can be appropriate only when the application operation is idempotent or has an idempotency key. Retrying a state-changing request without that protection can create duplicate work if the server began processing before returning the status.
What to inspect
- Server CPU, thread pool, resource limits and request queues.
- Correlated service and RPC runtime events at the same timestamp.
- Client retry behavior, especially synchronized retries that can make overload worse.
Microsoft: RPC Return Values · RpcServerListen
Looking for a different code? Search another status or error code.