I think that WMI err means the primary’s cimv2 lost its rpc bind path to clussvc and u can bounce winmgmt + clussvc, it nudges a fresh rpc sess… if it still hangs, rebuilding the WMI repo usu clears the old rpc refs on that node.
WSFC 2025 MS SQL SVR 2022 Basic Availability Group(Bare metal)
Karin Loo
0
Reputation points
Dear Support,
Good morning, I encountered
"An attempt to connect to the cluster failed due to one or more nodes not responding to WMI calls. This is usually caused by a problem with the WMI infrastructure on the nodes"
from Primary Node of WSFC cluster Cluster_Primary.logSecondary showed Cluster healthy, operational DB AvailabilityGroup FailOver successful Secondary back to Primary but I cannot Connect the cluster from FailOver Cluster Manager for Primary.
Server = 192.84.27.151
DB AG EndPoint = 12.12.12.151
HeartBeat=10.10.10.151
Please assist. Thank you very much.