| Previous | Next |
| RPC_NT_NO_CALL_ACTIVE | RPC_NT_CALL_FAILED_DNE |
RPC_NT_CALL_FAILED
RPC_NT_CALL_FAILED is an NTSTATUS value used by the Windows RPC runtime. This status has an important execution semantic: the server was reachable at some point, and execution of the remote procedure may have started. A client therefore cannot safely assume that no side effect occurred merely because it received a failure.
It differs from RPC_NT_CALL_FAILED_DNE, which explicitly says that execution on the server did not start. This distinction matters for retry design, idempotency and reconciliation of operations that change remote state.
The call failed after the server may already have started the procedure
- Correlate client call IDs, server logs and application transaction identifiers to establish whether the procedure entered server code.
- Retry only if the operation is idempotent or the application has a durable way to detect and reconcile prior execution.
- Capture the transport and RPC extended-error details; the generic status does not identify the low-level cause.
References
- Microsoft: RPC return values
- Microsoft Open Specifications: MS-RPCE
- The Open Group: DCE 1.1 RPC specification
Looking for a different code? Search another status or error code.