Return
-
Title
The RPC server is unavailable -
Description
Summary :Farm/Server Monitoring > This article provides information on how to troubleshoot an RPC error when attempting to add a farm using a clustered SQL server in Diagnostic Manager.,Symptom
The following message is encountered when attempting to add a farm using a clustered SQL server:
SharePoint Topology Access - Server Performance Credentials (FAILED) Error: WMI connection to the node of the SQL Server clustered instance failed. Error: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA). Double check that WMI is configured on the node and Collection Service service account has permission to access the node using WMI.
-
Cause
SharePoint Diagnostic Manager has successfully connected to the cluster server registry via WMI to get the names of nodes and is subsequently having issues attempting to connect to said node via WMI. The "The RPC Server Is Unavailable" message usually indicates that the RPC traffic is not getting to the remote server, or there is no RPC listener on the remote server. -
Resolution
Perform the steps below to troubleshoot the RPC error:- Ensure the Remote Procedure Call (RPC) service is running on the remote server.
- Verify that there is a TCP listener on the remote server by running the netstat -nao command and verifying that the TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1304 entry exists.
- In the Tools sub-directory, run rpcping /s SERVERNAME /t ncacn_tp_tcp. This command verifies that RPC can communicate with the remote server. The output should be similar to Completed 1 calls in 15 ms 66 T/S or 15.000 ms/T.
- Ensure that the traffic is not being blocked by local or internal network firewalls. Either disable the firewall or configure the Windows firewall to allow incoming RPC traffic.
- Use the remote server IP address instead of the server name. If the IP address works, there may be a DNS issue.
- If the remote server resides on a different domain, the two domains may not trust each other, or the user account being used does not have administrator permissions on the remote server/domain.
- If both computers are in the same domain and the user account has administrator permissions, try rejoining both computers to the domain.