| Previous | Next |
| RPC_S_INVALID_NET_ADDR | RPC_S_INVALID_TIMEOUT |
RPC_S_NO_ENDPOINT_FOUND
RPC_S_NO_ENDPOINT_FOUND means that RPC could not find an endpoint for the requested interface and binding information. This is often an endpoint-discovery failure, not a general proof that the machine is unreachable.
How endpoint discovery works
RPC servers may use dynamically assigned endpoints. The client then needs an endpoint mapper or another discovery mechanism to obtain the endpoint that matches the interface UUID, protocol sequence and server.
What to check
- Confirm that the target server has registered the required RPC interface and is running the component that exposes it.
- Verify that endpoint mapper access is not blocked by network policy or a firewall.
- Check that client and server use the same interface UUID, transport and architecture of the deployment.
Microsoft: Finding Endpoints · RPC Return Values
Looking for a different code? Search another status or error code.