| Previous | Next |
| RPC_S_INVALID_TIMEOUT | RPC_S_ALREADY_REGISTERED |
RPC_S_OBJECT_NOT_FOUND
Object UUID dispatch is separate from interface dispatch
RPC_S_OBJECT_NOT_FOUND belongs to the RPC object model. A binding may carry an object UUID in addition to an interface UUID. On the server, object UUIDs can be associated with type UUIDs so the runtime selects the correct manager entry-point vector for an interface implementation.
The status therefore does not mean that the remote host or endpoint is missing. It means the requested object UUID could not be resolved in the object/type mapping used by the RPC runtime or application-supplied inquiry function.
What to inspect
- Read the object UUID from the client binding and compare it with the UUIDs registered through
RpcObjectSetType. - If the application installed an
RPC_OBJECT_INQ_FN, verify that the callback can still resolve the object and returns the expected type UUID. - Check object lifetime: removing the mapping while clients retain bindings can turn previously valid calls into object lookup failures.
Do not fix this by changing endpoint mapper or firewall settings. Endpoint discovery may already have succeeded; the failure is in object-specific server dispatch.
References
Looking for a different code? Search another status or error code.