| Previous | Next |
| RPC_S_UNSUPPORTED_TRANS_SYN | RPC_S_INVALID_TAG |
RPC_S_UNSUPPORTED_TYPE
Type UUIDs are part of manager selection
RPC_S_UNSUPPORTED_TYPE is tied to RPC object typing rather than C or MIDL scalar data types. In the RPC object model, a server may associate object UUIDs with type UUIDs and register manager entry-point vectors for those types. That lets the same interface dispatch different objects to different implementations.
The status indicates that the UUID type involved in the operation is not supported in that context. It should be distinguished from RPC_S_UNKNOWN_MGR_TYPE, where the requested manager type is simply not registered for an interface.
What to check
- Log the object UUID and type UUID passed to object-management APIs.
- Verify that application code did not confuse an interface UUID, object UUID, and type UUID; all are UUID values but have different roles.
- Keep the nil UUID semantics documented. A nil type resets an object to the default object/nil-type association in
RpcObjectSetType.
The safest fix is to trace UUID provenance through the object registry and interface-registration code rather than replacing UUIDs until the status disappears.
References
Looking for a different code? Search another status or error code.