Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

Windows 2012 R2 Failover cluster RPC server Unavailable Exception from HRESULT: 0x800706BA

$
0
0

Today I was asked to change the IP address of a Windows 2012 r2 Failover cluster that is for a SQL 2014 AG. When I connected to one of the nodes in the cluster I opened failover cluster MMC and to my surprise there was nothing showing. I immediately went to the other node and tried and found that nothing was showing on the 2nd node either. When I try Connect to Cluster from either node I get " An error occurred trying to display cluster information. The RPC server is unavailable.(Exception from HRESULT:0x800706BA)".

I next tried to ping each node by name from the other and I was able to get a reply. When I ping the Cluster name, from the node in our remote datacenter The name resolves to one of the IP's assigned to the cluster name but the request times out. When I ping from the node in our local datacenter, I get destination host unreachable and it has the local nodes IP. 

Next I opened Powershell and ran Get-ClusterResource


From this it appears that the first Cluster IP address is missing (and offline). This may mean that the remote data center node is active. But I would think I still need to have the first Cluster IP Address showing an actual IP. How do I add that back and bring that node online as the primary from Powershell?

Seeing this prompted me to look at another WSFC that we have. When I connected to a node from a different WSFC, I found the exact same issue! I am not sure why the MMC does not show the failover cluster configuration and when I try to connect I get the same error as on the first 2 nodes of the other cluster. 

I have checked to make sure that the failover cluster service and the RPC service are running on all members of both clusters. I also restarted both members of the first cluster. I am not sure how to proceed at this point. I would like to fix this if possible and find the root cause. If need be I can delete the Windows cluster and rebuild it but I want to save that as a last resort so that I don't have rebuild the SQL availability groups.

Any help would be greatly appreciated.

Thanks,

TD

 

Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>