| Previous | Next |
| EPT_S_CANT_CREATE | ERROR_INVALID_TIME |
RPC_S_INVALID_OBJECT
Object-based dispatch received an empty object identity
RPC_S_INVALID_OBJECT identifies the nil UUID in an RPC object context. Object UUIDs can help a server select a manager implementation or resource behind an interface. A nil UUID means no specific object; an API that requires an actual object identity rejects it rather than treating it as an arbitrary default.
Log the UUID before it is attached to the binding and distinguish an all-zero value from parsing failure or an unknown nonzero object. Check initialization order and whether a structure was zeroed after UUID assignment. If object-based dispatch is optional, omit the object UUID deliberately; if required, allocate and persist the correct identity.
What to inspect
- Print the complete UUID and test explicitly for nil before the call.
- Trace where RpcBindingSetObject or equivalent binding construction occurs.
- Do not substitute the interface UUID for an application object UUID.
References
- Microsoft: setting an object UUID on a binding
- MS-RPCE: object UUID meaning
- Microsoft: invalid RPC object status
Looking for a different code? Search another status or error code.