| Previous | Next |
| RPC_NT_INVALID_TIMEOUT | RPC_NT_ALREADY_REGISTERED |
RPC_NT_OBJECT_NOT_FOUND
RPC_NT_OBJECT_NOT_FOUND is an NTSTATUS value used by the Windows RPC runtime. This status means that an object UUID was usable as an identifier but no corresponding RPC object registration was found. Object UUIDs can influence manager selection independently of the interface UUID that identifies the remote procedure contract.
It differs from RPC_NT_INVALID_STRING_UUID, where the UUID text cannot be parsed at all, and from RPC_NT_UNKNOWN_IF, where the server does not recognize the requested RPC interface. The three failures occur at different lookup layers.
A valid object UUID could not be matched to an RPC object registration
- Record the object UUID separately from the interface UUID and verify that the client is sending the intended object identity.
- Inspect object registration and unregistration order on the server, especially for dynamically created objects.
- Do not replace the object UUID with a nil UUID unless the interface contract explicitly supports object-independent dispatch.
References
Looking for a different code? Search another status or error code.