| Previous | Next |
| RPC_S_CANT_CREATE_ENDPOINT | RPC_S_SERVER_UNAVAILABLE |
RPC_S_OUT_OF_RESOURCES
The failure occurred inside RPC resource allocation
RPC_S_OUT_OF_RESOURCES means the RPC runtime or generated stub could not obtain memory, a call structure, a transport buffer, a thread-related object, or another internal resource needed to continue. It is more specific than a remote application returning its own capacity error: the request may not have reached the manager routine at all.
Correlate the status with process commit, handle count, thread count, active RPC calls, message size, and server concurrency limits. A single oversized conformant array can force substantial stub allocation even when ordinary process memory appears healthy. Persistent failures under low load point toward leaked bindings, contexts, async states, or server-side allocations rather than network reachability.
What to inspect
- Capture RPC extended error information before later calls overwrite it.
- Compare failing parameter sizes with generated IDL bounds and allocation limits.
- Track whether resource use returns to baseline after calls and contexts close.
References
- Microsoft: server stub allocation and NDR buffers
- Microsoft: RPC extended error detection locations
- Microsoft: RPC return values
Looking for a different code? Search another status or error code.