| Previous | Next |
| EPT_S_CANT_PERFORM_OP | RPC_S_NOTHING_TO_EXPORT |
EPT_S_NOT_REGISTERED
Endpoint mapper enumeration has reached an empty result or the end of matching entries
EPT_S_NOT_REGISTERED is documented by Microsoft RPC as the condition where there are no more endpoints available from the endpoint-map database. It commonly appears in endpoint-map inquiry or lookup flows rather than as proof that the entire RPC subsystem is unavailable.
The endpoint mapper matches interface UUID, interface version rules, protocol sequence, and optionally object UUID information. A server can be running while no endpoint-map element matches the client's requested interface and binding context.
What to check
- Compare the queried interface UUID and version with what the server actually registered.
- Verify the protocol sequence; a TCP endpoint-map entry does not satisfy a named-pipe binding request.
- If an object UUID is present, check whether the server registered endpoint entries for that object or only for the nil object UUID.
- For enumeration code, treat the documented end-of-results condition correctly instead of retrying the same inquiry context forever.
Querying the mapper can distinguish a missing registration from a general network failure, but the filter fields must match the server's published endpoint data.
References
Looking for a different code? Search another status or error code.