| Previous | Next |
| RPC_NT_CANNOT_SUPPORT | RPC_NT_INTERNAL_ERROR |
RPC_NT_NO_CONTEXT_AVAILABLE
No RPC security context for impersonation
RPC_NT_NO_CONTEXT_AVAILABLE belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_NO_CONTEXT_AVAILABLE, mS-RPCE extends the DCE/RPC model: generated stubs marshal parameters, the runtime binds to an endpoint and protocol sequence, and security or transport failures can be returned as RPC facility status values.
This status is about RPC security, not about application context handles. It normally appears when server code tries to impersonate the active caller but the call does not carry a usable security context.
Check how the client binding was authenticated, which authentication level was negotiated, and whether the server is trying to impersonate outside the lifetime of the active RPC call. A server cannot recover this by checking file permissions; it must have an authenticated RPC call context.
What to check for RPC_NT_NO_CONTEXT_AVAILABLE
- Verify that the client called the endpoint with authentication enabled, not anonymous or unauthenticated binding.
- Correlate with the server path that calls RpcImpersonateClient or equivalent impersonation logic.
- For callbacks or queued work, confirm that impersonation is not attempted after the original RPC call context has ended.
References for RPC_NT_NO_CONTEXT_AVAILABLE
- Microsoft RPC: client impersonation
- Microsoft RPC: authentication-level constants
- MS-RPCE: security context handle
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.