Windows error 1706 (RPC_S_INVALID_ENDPOINT

Status / error code:		Category:

Constant name:
Source:	Operating System:
Description: The endpoint format is invalid.

Previous	Next
RPC_S_INVALID_STRING_UUID	RPC_S_INVALID_NET_ADDR

RPC_S_INVALID_ENDPOINT_FORMAT

RPC_S_INVALID_ENDPOINT_FORMAT means that the endpoint portion of an RPC binding is not valid for the selected protocol sequence. An endpoint is transport-specific: it might be a TCP port, a named-pipe endpoint, or another protocol-defined value.

Where it is usually introduced

The error often appears when a program combines an endpoint from one transport with another transport, treats an endpoint as a complete URL, or stores an endpoint in a configuration format that changes its delimiters.

What to check

Verify the protocol sequence first, then validate the endpoint using the rules for that transport.
Use RpcStringBindingCompose to create the final binding.
For dynamic endpoints, ask the endpoint mapper rather than hard-coding a value learned from one server instance.

Microsoft: String Binding · Finding Endpoints

Looking for a different code? Search another status or error code.