| Previous | Next |
| RPC_NT_SERVER_UNAVAILABLE | RPC_NT_INVALID_NETWORK_OPTIONS |
RPC_NT_SERVER_TOO_BUSY
RPC_NT_SERVER_TOO_BUSY is an NTSTATUS value used by the Windows RPC runtime. This status distinguishes capacity from absence: the server is available, but it is too busy to complete the operation. Queue depth, listener backlog, worker availability and request cost can all affect this state, depending on the transport and server configuration.
It is not equivalent to RPC_NT_SERVER_UNAVAILABLE. Nor does it prove that the target procedure executed. Treat it as a load and admission-control signal, then inspect the server-side listener and request execution path.
The server was reachable but could not accept or complete the call under current load
- Measure concurrent calls, RPC listener backlog, process resources and latency distribution around the failure window.
- For TCP-based RPC listeners, review the configured maximum-calls hint together with actual system and socket-provider limits.
- Use bounded retry/backoff only where the RPC operation is safe to repeat and application semantics permit it.
References
Looking for a different code? Search another status or error code.