| Previous | Next |
| RPC_NT_UNKNOWN_AUTHZ_SERVICE | EPT_NT_CANT_PERFORM_OP |
EPT_NT_INVALID_ENTRY
Invalid RPC endpoint-map entry
EPT_NT_INVALID_ENTRY comes from the endpoint-mapper side of the Windows RPC facility. The endpoint mapper maintains dynamic endpoint records that let a client resolve an interface and object UUID to the concrete local endpoint used by a server process.
This status is more specific than a missing server. It says the endpoint-map record supplied to an endpoint operation is not structurally acceptable for that operation: for example, the interface, object UUID, protocol sequence, annotation, or endpoint data does not form a valid entry.
What to check
- Check the interface UUID, version, object UUID list, protocol sequence, endpoint string, and annotation used when registering or querying the endpoint map.
- Compare the failing entry with the actual binding vector returned by the server before registration.
- Do not treat this as a firewall problem until the endpoint mapper request itself has been decoded and shown to be well formed.
References
- Microsoft Open Specifications: MS-RPCE glossary
- Microsoft RPC: RPC return values
- Microsoft RPC: types of binding handles
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.