| Previous | Next |
| RPC_S_COOKIE_AUTH_FAILED | RPC_S_SYSTEM_HANDLE_COUNT_EXCEEDED |
RPC_S_DO_NOT_DISTURB
The server deliberately refused dispatch while in a suspended state
RPC_S_DO_NOT_DISTURB is not a generic “server unavailable” condition. The RPC server exists but is suspended or quiescing, and the runtime could not resume it for the incoming request. The manager routine did not execute, so application-side partial work should not be inferred from this result.
Inspect service lifecycle, maintenance, shutdown, and listener-management code around the time of failure. Correlate calls that stop listening or suspend dispatch with the component expected to restart it. Client retries should use bounded backoff and should not hide a server that remains permanently quiesced because initialization or recovery failed.
What to inspect
- Log server listen/suspend/resume transitions with reasons and timestamps.
- Confirm the service is not stuck between stop and restart phases.
- Treat repeated results as server lifecycle failure, not network packet loss.
References
- Microsoft: RPC server dispatch architecture
- Microsoft: RPC failure handling
- Microsoft: RPC_S_DO_NOT_DISTURB definition
Looking for a different code? Search another status or error code.