RPC Server Unavailable Error was Thrown by the RPC Runtime
Topic Last Modified: 2010-08-20
The Microsoft Remote Connectivity Analyzer issues an RPCPing to several Exchange Server endpoints to simulate the connections that are made when a Microsoft Outlook client connects to Microsoft Exchange Server 2007 Outlook Anywhere or to Microsoft Exchange Server 2003 RPC over HTTP. To connect, the client must be able to successfully connect to the HTTP endpoints of the Microsoft Exchange Information Store, the referral service of DSProxy within the Exchange System Attendant service, and to the DSProxy service within the Exchange System Attendant service over ports 6001, 6002, and 6004, respectively. If the test fails, the Microsoft Remote Connectivity Analyzer generates the following error:
"RPC Server Unavailable error (1722) was thrown by the RPC Runtime"
This issue can be caused by any of the following conditions:
Failures in DNS name resolution
Missing or invalid ValidPorts key in the registry of the Internet-facing Exchange 2007 Client Access server or of the Exchange 2003 server
Exchange services not listening on the required endpoints
Firewalls blocking the required ports
For More Information
To resolve this issue, do the following:
Troubleshoot name resolution, and verify that the server acting as the RPC proxy can correctly resolve the internal fully-qualified domain name (FQDN) of the mailbox server or of Exchange 2003.
Open Registry Editor on the Client Access server or on the front-end server, and verify that the ValidPorts registry value exists under HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Rpcproxy. Also confirm that the key includes the NetBIOS and FQDN for all mailbox servers and for each required port (that is, for ports 6001, 6002, and 6004).
To test endpoint connectivity, open a Telnet session on the Client Access server or on the front-end server, and then Telnet to each port on the mailbox servers (that is, on ports 6001, 6002, and 6004). Successful Telnet connection result would be indicated by the presence of the "ncacn_http/1.0" banner when connection is established. Testing a Telnet connection to both NetBios name and FQDN is recommended. If you cannot successfully Telnet to any of the ports, and if there is a firewall between the servers, check your firewall configuration.
If you are receiving this error on port 6004, and if you are using Exchange 2007 on Windows Server 2008, make sure that you have Exchange 2007 SP1 RU4 or later installed. This is because a problem that affects IPv6 can cause DSProxy requests to fail and generate this error. For more information about this specific issue, see the Exchange Team blog post, "How does Outlook Anywhere work (and not work)?".
Modification of the ValidPorts does not apply to Microsoft Exchange Server 2010. In Exchange 2010, the registry value is ValidPorts_Exchange. You do not have to manually modify this value. This value is created by automatic configuration in Client Access Server settings.
For information about how to troubleshoot DNS, see Troubleshooting DNS.
To learn more about Exchange 2007 Outlook Anywhere and the ValidPorts key, see How does Outlook Anywhere work (and not work)?
To learn more about Exchange 2003 RPC over HTTP and the ValidPorts key, see RPC over HTTP Interactions on the RPC Proxy Server.
To review another option to solve the Outlook Anywhere connectivity issue with Exchange 2007 SP1 on Windows Server 2008, see How does Outlook Anywhere work (and not work)?.
Microsoft Remote Connectivity Analyzer has limited documentation at this time. In an effort to improve the documentation for each of the errors that you might receive, we would like to solicit additional information from the community. Please use the Community Content section below to post additional information about why you failed at this point. If you require technical assistance, create a post in the appropriate Exchange TechNet forum or contact support.