| Previous | Next |
| RPC_NT_BYTE_COUNT_TOO_SMALL | RPC_NT_INVALID_ES_ACTION |
RPC_NT_BAD_STUB_DATA
Bad marshaled data received by an RPC stub
RPC_NT_BAD_STUB_DATA is a strong hint that the failure is at the NDR/stub boundary. The received data does not match the structure, lengths, discriminants, conformance information, or transfer syntax expected by the generated stub.
The endpoint may be reachable and authentication may already be complete. Focus on IDL compatibility, stub version, transfer syntax, data corruption, and whether a client is sending data produced by a different interface definition.
What to check
- Confirm that client and server were generated from the same IDL or from explicitly compatible IDL versions.
- Check union discriminants, array bounds, string terminators, and variable-size structures.
- Use an RPC-aware trace or debugger at the stub boundary; ordinary socket logs will not explain NDR validation failures.
References
- Microsoft Open Specifications: MS-RPCE overview
- The Open Group: DCE 1.1 RPC protocol definitions
- Microsoft Open Specifications: NTSTATUS values
- Microsoft RPC: serialization services
Looking for a different code? Search another status or error code.