| Previous | Next |
| RPC_S_ENTRY_ALREADY_EXISTS | RPC_S_NAME_SERVICE_UNAVAILABLE |
RPC_S_ENTRY_NOT_FOUND
The missing object is a namespace entry
RPC_S_ENTRY_NOT_FOUND means the RPC name-service layer could not locate the requested entry. The entry normally acts as a publication point from which clients import or look up binding handles compatible with an interface and optional object UUID.
This is not equivalent to RPC_S_NO_ENDPOINT_FOUND. A namespace lookup can fail before the client has a server binding or reaches a server endpoint mapper.
What to inspect
- Log the complete entry name after any namespace expansion and the selected name syntax.
- Verify that the server export path and client lookup path use the same service entry, including case and hierarchy rules of the active name service.
- Check deployment ordering: clients should not depend on an entry before the server has exported bindings.
- When an entry was intentionally removed, invalidate cached configuration that still references it.
Do not substitute the server's DNS name for an RPC namespace entry unless the application contract explicitly defines that mapping. Use the same naming model on export and lookup.
References
Looking for a different code? Search another status or error code.