| Previous | Next |
| RPC_S_UUID_NO_ADDRESS | RPC_S_UNKNOWN_AUTHN_TYPE |
RPC_S_DUPLICATE_ENDPOINT
An endpoint is transport-specific server address information
RPC_S_DUPLICATE_ENDPOINT indicates an endpoint collision. For RPC over TCP an endpoint can be a TCP port; for RPC over named pipes it can be a pipe name. A server that chooses a well-known endpoint must ensure that its endpoint and protocol-sequence combination does not conflict with another active server instance.
Dynamic endpoint registration and explicit endpoint selection are different designs. The endpoint mapper can publish dynamically created endpoints, while a fixed endpoint is intentionally selected by the application.
What to check
- Log the protocol sequence and endpoint passed to
RpcServerUseProtseqEp*. - Check for a second service instance, stale supervisor process, or another interface using the same explicit endpoint.
- If multiple server instances may expose the same interface/object combination, review the no-replace endpoint registration semantics rather than overwriting map entries.
- Do not confuse this with
RPC_S_ALREADY_REGISTERED, which is about an object UUID/type mapping.
Choosing a dynamic endpoint is often appropriate when a fixed transport endpoint is not part of the external protocol contract.
References
Looking for a different code? Search another status or error code.