NTSTATUS 0xC002004D (RPC_NT_INVALID_OBJECT): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The RPC object UUID supplied with the binding or call was the nil UUID where a real object was required.

Previous	Next
EPT_NT_CANT_CREATE	RPC_NT_NO_INTERFACES

RPC_NT_INVALID_OBJECT

Invalid or nil RPC object UUID

RPC_NT_INVALID_OBJECT belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_INVALID_OBJECT, mS-RPCE extends the DCE/RPC model: generated stubs marshal parameters, the runtime binds to an endpoint and protocol sequence, and security or transport failures can be returned as RPC facility status values.

RPC bindings can carry an object UUID that selects a particular server object behind an interface. This status indicates that the object UUID is invalid in this context, specifically the nil UUID where the operation requires a concrete object.

Do not confuse the object UUID with the interface UUID. The interface identifies the contract; the object UUID can route the call to a particular object instance, manager type, or registration.

What to check for RPC_NT_INVALID_OBJECT

Dump the binding string and object UUID before the call is made.
Check whether the server registered object UUIDs or only an interface endpoint.
If the client constructs bindings manually, verify that UUID parsing did not silently replace an invalid value with nil.

References for RPC_NT_INVALID_OBJECT

Looking for a different code? Search another status or error code.