| Previous | Next |
| RPC_NT_INVALID_OBJECT | RPC_NT_CALL_CANCELLED |
RPC_NT_NO_INTERFACES
No RPC interfaces registered
RPC_NT_NO_INTERFACES belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_NO_INTERFACES, 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 the runtime could not find registered RPC interfaces in the context being queried. It is stronger than a single unknown opnum; the interface registration set itself is empty or not visible to the caller.
On a server, check whether RpcServerRegisterIf or equivalent registration succeeded before listening. On a client lookup path, check filters and endpoint mapper visibility.
What to check for RPC_NT_NO_INTERFACES
- Confirm server startup order: protocol sequence registration, interface registration, endpoint registration, then listen.
- Check whether the server exited or restarted between endpoint discovery and the call.
- Verify that firewall or service isolation has not made endpoint mapper results stale.
References for RPC_NT_NO_INTERFACES
- 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.