Hi Experts,
I have three nodes with SAN Yesterday i reboot one server HP-SRV3 due to Windows Update requirement and Antivirus update requirement. The rebooted server was UP and running but on other servers HP-SRV1 and HP-SRV2 i am unable to connect with cluster although they were not rebooted.
Getting this error on
connect to cluster
and
validate configuration
cluster access is denied. (exception from hresult: 0x80070005 (e_accessdenied))
I have checked the following.
Cluster services is running on three server
I am able to ping HP-SRV2 and HP-SR1 from HP-SRV3 and vise versa.
I am domain admin also add my account on cluster computer object in AD
From HP-SRV3 cluster is showing that other nodes HP-SRV1 and HP-SRV2 are UP and but on HP-SRV1 and HP-SRV failover cluster manager i am unable to connect Failover Cluster Manager.
Kindly help how can i resolve and troubleshoot.
Note : All relevant screen-shots and failover cluster manage validation report attached
257459-report.pdf
Windows Server:
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
Clustering:
The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
Probably a bit to late, I had the same issue and it turned out to be a DCOM error that appeared in the eventlogs, fixed it doing the workarround I found:
https://support.microsoft.com/en-us/topic/kb5004442-manage-changes-for-windows-dcom-server-security-feature-bypass-cve-2021-26414-f1400b52-c141-43d2-941e-37ed901c769c
Will do some further research if there is anything I can do except disable the hardening but working for now
Registry setting to enable or disable the hardening changes
During the timeline phases in which you can enable or disable the hardening changes for CVE-2021-26414, you can use the following registry key:
Path : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\AppCompat
Value Name: "RequireIntegrityActivationAuthenticationLevel"
Type: dword
Value Data: default = 0x00000000 means disabled. 0x00000001 means enabled. If this value is not defined, it will default to enabled.
Do you have latest windows update installed on all nodes.
I was facing similar issue. Applying windows latest update on the nodes fixed the issue for me.
I hope the above information can help you.
If the ANSWER is helpful, please click "Accept Answer" and upvote it. Thanks
Thank you for posting the question to the Q&A forum.
From the screenshots, it seems that something is related to the network on the server. I would recommend to check this article :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/b1be178e-ae61-4a80-b880-b84b251a2d98/cant-connect-to-cluster-in-failover-cluster-manager?forum=winserverClustering
I also check this article official from MS but is not a case in this situation :
https://learn.microsoft.com/en-us/troubleshoot/windows-server/high-availability/cluster-validation-failure-error-80070005
btw: Why you don't do the update from the Cluster Aware updating?
I hope the above information can help you.
If the ANSWER is helpful, please click "Accept Answer" and upvote it. Thanks
