| Previous | Next |
| RPC_NT_ENUM_VALUE_OUT_OF_RANGE | RPC_NT_BAD_STUB_DATA |
RPC_NT_BYTE_COUNT_TOO_SMALL
RPC byte count is too small for marshaled data
RPC_NT_BYTE_COUNT_TOO_SMALL is produced by stub/NDR validation when a caller-provided size does not match the data that must be transmitted or decoded. It is common around conformant arrays, byte buffers, strings, and serialization buffers.
Do not diagnose this as a network short read until the IDL size attributes and actual buffer lengths have been checked. The stub may reject the arguments before any useful server-side operation happens.
What to check
- Verify IDL attributes such as
size_is,length_is, and buffer-count parameters against the actual allocation. - Check integer truncation when converting element counts to bytes.
- For serialization services, confirm that the supplied encode/decode buffer is large enough for the marshaled representation.
References
- Microsoft RPC: serialization services
- Microsoft RPC: using serialization services
- Microsoft RPC: RPC return values
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.