| Previous | Next |
| RPC_NT_GROUP_MEMBER_NOT_FOUND | RPC_NT_INVALID_OBJECT |
EPT_NT_CANT_CREATE
Endpoint mapper could not create an entry
EPT_NT_CANT_CREATE belongs to endpoint registration rather than call execution. It indicates that the endpoint mapper could not add the requested database entry for a server interface, object, or binding set.
The useful evidence is the registration call and the binding vector that was being exported. A duplicate endpoint, malformed entry, unavailable endpoint mapper, unsupported name-service path, or local resource failure can all surface before any client call reaches the server manager routine.
What to check
- Log the server-side registration sequence: protocol sequence, endpoint creation, interface registration, then endpoint export.
- Look for duplicate static endpoints or repeated registration after service restart/recovery code.
- Check local RPC Endpoint Mapper events and service state before debugging client-side stubs.
References
- Microsoft Open Specifications: MS-RPCE glossary
- Microsoft RPC: RPC return values
- Microsoft RPC: types of binding handles
- Microsoft RPC: automatic binding handles
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.