| Previous | Next |
| RPC_NT_NO_PRINC_NAME | RPC_NT_SEC_PKG_ERROR |
RPC_NT_NOT_RPC_ERROR
Non-RPC status passed through an RPC error path
RPC_NT_NOT_RPC_ERROR belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_NOT_RPC_ERROR, 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 usually appears in error translation code. Something attempted to interpret or convert a value as a Windows RPC error, but the value is not in the RPC runtime error space.
The diagnostic target is the boundary where application, Win32, NTSTATUS, HRESULT, or RPC_STATUS values are mixed. A real transport or authentication failure may have been overwritten by incorrect status conversion.
What to check for RPC_NT_NOT_RPC_ERROR
- Trace the original error value before any mapping to RPC_STATUS or HRESULT.
- Check wrappers that collapse several error spaces into one return type.
- Do not assume the RPC runtime generated the original failure; this status may be a secondary translation failure.
References for RPC_NT_NOT_RPC_ERROR
- Microsoft Open Specifications: MS-RPCE overview
- The Open Group: DCE 1.1 RPC introduction
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.