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

DCOM error on server manager connecting to failover cluster

$
0
0

hi

we have 2 server 2012 r2 Hyper-V host servers one of them cannot connect to the cluster in server manager giving up the following errors.

DCOM was unable to communicate with the computer CherwellCluster using any of the configured protocols; requested by PID      918 (C:\Program Files\CA\arcserve Unified Data Protection\Engine\TOMCAT\bin\tomcat7.exe).

DCOM was unable to communicate with the computer CherwellCluster.cherwell.local using any of the configured protocols; requested by PID     2370 (C:\Windows\system32\ServerManager.exe).

I have checked the DCOM TCP/IP protocols on both Virtual Host servers and they match up ok.

a windows 10 remote server manager plus the 2nd Virtual Host can connect perfectly well. both of these can also get good reply from themselves, each other, the affected VH server and the cluster to the powershell command get-wmiobject mscluster_resourcegroup -computer cherwellcluster -namespace “ROOT\MSCluster“.

the affected server can do the same powershell command on the 2nd VH server and our 2012 r2 DCs but not the cherwellcluster

on the affected server the domain firewall is off, wmimgmt says repository is consistent, the entry for the cluster in server manager has been removed and re-added, the server has been rebooted a couple of times and has been brought up to date with windows updates.

whatever the underlying problem is it also affected the vEthernet NIC preventing it from seeing the domain suffix properly which i have fixed by adding it to the NICs Ipv4 DNS tab.

I've exhausted searching on the internet, any ideas?

thanks in advance

Giles.



Viewing all articles
Browse latest Browse all 5654

Trending Articles



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