| Previous | Next |
| EPT_S_INVALID_ENTRY | EPT_S_NOT_REGISTERED |
EPT_S_CANT_PERFORM_OP
The failure is inside endpoint-map management
EPT_S_CANT_PERFORM_OP is returned by endpoint-mapper operations when the mapper cannot carry out the requested database action. Endpoint registration, lookup, inquiry, and removal are management operations over mappings between RPC interfaces, object UUIDs, protocol sequences, and endpoints.
The status is intentionally broader than EPT_S_INVALID_ENTRY or EPT_S_NOT_REGISTERED. It says the requested mapper operation could not be completed, so the surrounding API and RPC extended error information are important.
What to capture
- Record whether the caller was registering, unregistering, resolving, or enumerating endpoint-map elements.
- Preserve the original RPC status and extended error chain; Microsoft documents dedicated detection points for endpoint registration and resolution failures.
- Use the local endpoint mapper for server registration as required by the RPC model; do not assume arbitrary remote mapper modification is supported.
- Compare registration and cleanup ordering when the error appears only during rapid service restart.
Port 135 reachability alone is not enough to diagnose this status. The mapper can be reachable yet unable to perform a specific database operation.
References
- Microsoft: Extended RPC error locations
- MS-RPCE dynamic endpoint registration
- The Open Group: endpoint map API
Looking for a different code? Search another status or error code.