| Previous | Next |
| RPC_S_UNKNOWN_AUTHZ_SERVICE | EPT_S_CANT_PERFORM_OP |
EPT_S_INVALID_ENTRY
The endpoint map stores interface-to-address information
EPT_S_INVALID_ENTRY belongs to the endpoint mapper, whose database maps RPC interface and object information to transport-specific server endpoints. A registration can combine an interface specification, a vector of server bindings, and object UUIDs to create endpoint-map elements.
An invalid entry is therefore an endpoint-map data problem, not a generic malformed application record. The relevant fields are the interface identifier and version, object UUID, protocol sequence, endpoint, and associated tower/address representation used by DCE/RPC.
What to inspect
- Check which endpoint-management or inquiry API returned the status and capture the interface UUID/version and object UUID filter.
- For registrations, build the binding vector from
RpcServerInqBindingsrather than synthesizing server bindings by hand. - Ensure registration and unregistration use matching interface, binding-vector, and object-UUID inputs.
- When interoperating with a non-Windows DCE/RPC implementation, inspect the actual endpoint-map element or protocol tower representation.
Changing the application procedure or credentials does not repair malformed endpoint-map data. Focus on registration and mapper state.
References
Looking for a different code? Search another status or error code.