| Previous | Next |
| RPC_S_CANNOT_SUPPORT | RPC_S_INTERNAL_ERROR |
RPC_S_NO_CONTEXT_AVAILABLE
RPC impersonation requires an active call and a suitable security context
RPC_S_NO_CONTEXT_AVAILABLE is returned when the server cannot obtain a security context that allows it to impersonate the RPC client. Microsoft documents this status for RpcImpersonateClient when the server does not have permission to impersonate the client.
This is different from RPC_S_NO_CALL_ACTIVE, where no client call is active on the server thread, and from an unknown authentication service. Authentication may have occurred, yet the resulting context may not grant the impersonation capability requested by server code.
What to inspect
- Confirm impersonation is attempted while processing the intended RPC call or with the correct client binding handle.
- Inspect the binding security quality-of-service and impersonation level negotiated for the call.
- Do not assume packet privacy or successful authentication automatically permits delegation or impersonation at every level.
- Always pair successful
RpcImpersonateClientwithRpcRevertToSelfon the correct execution path.
Use RPC extended error information and security-context diagnostics to distinguish insufficient impersonation capability from credential-validation failures.
References
- Microsoft: RpcImpersonateClient
- Microsoft: RpcBindingSetAuthInfoEx
- Microsoft: Extended RPC error locations
Looking for a different code? Search another status or error code.