| Previous | Next |
| RPC_S_SYSTEM_HANDLE_COUNT_EXCEEDED | RPC_S_GROUP_MEMBER_NOT_FOUND |
RPC_S_SYSTEM_HANDLE_TYPE_MISMATCH
The runtime received the wrong kind of operating-system handle
RPC_S_SYSTEM_HANDLE_TYPE_MISMATCH is type validation for a MIDL system_handle parameter. A numeric handle value was valid enough to inspect, but the underlying kernel object was not the declared type—for example, a file handle supplied where an event, token, section, or process handle is required.
Log both the IDL-declared sh_* type and the code path that created the handle. Avoid untyped wrappers that combine unrelated HANDLE values, and validate array element provenance before the call. Duplicating the same wrong handle or requesting broader access cannot change its object type.
What to inspect
- Trace each handle to the API that created or opened it.
- Keep typed RAII wrappers separate for different kernel object classes.
- Check array indexing and structure packing before blaming handle creation.
References
- Microsoft: supported system_handle object types
- Microsoft: RPC handle format concepts
- Microsoft: system-handle type mismatch status
Looking for a different code? Search another status or error code.