| Previous | Next |
| RPC_NT_NO_INTERFACES | RPC_NT_BINDING_INCOMPLETE |
RPC_NT_CALL_CANCELLED
RPC call cancellation reached the runtime
RPC_NT_CALL_CANCELLED belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_CALL_CANCELLED, 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 means cancellation was observed by the RPC runtime. It may be explicit client cancellation, timeout-driven cancellation, thread termination, or cleanup after a higher layer abandoned the operation.
The main question is who cancelled the call and whether the server also observed cancellation. For long-running calls, cancellation can race with completion, so correlate client logs, server logs, and transport closure.
What to check for RPC_NT_CALL_CANCELLED
- Check for explicit RpcCancelThread, async cancellation, request timeout, or application shutdown around the failure time.
- Determine whether the server continued processing after the client side cancelled.
- For idempotent operations, decide whether retry is safe; cancellation does not prove the server made no changes.
References for RPC_NT_CALL_CANCELLED
- Microsoft RPC: asynchronous RPC
- Microsoft RPC: making the asynchronous call
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.