| Previous | Next |
| RPC_NT_INVALID_TAG | RPC_NT_NO_ENTRY_NAME |
RPC_NT_INVALID_BOUND
The NDR array bounds do not match the IDL contract
RPC stubs marshal variable arrays and conformant data with bounds. This status means the received or supplied bound cannot be accepted for the declared IDL type, for example because it exceeds the allowed range or contradicts another size field.
The failing value is usually in the stub data, not in the endpoint mapper. Check the generated MIDL contract, maximum counts, actual buffer length, and any caller-provided length fields.
What to inspect
- Log the transmitted max count, offset and actual count for variable arrays.
- Validate caller length fields before entering the RPC call.
- Check for client/server stub version mismatch.
References
- Microsoft Open Specifications: MS-RPCE
- Microsoft: Remote Procedure Call (RPC)
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.