I have recently installed SCVMM 2012 SP1 and am in the midst of verifying the agents and refreshing my VM Hosts. The SCVMM upgrade was done by migrating uninstaling SCVMM from my original 2008 R2 server, building a 2012 VM, and installing SCVMM 2012 SP1 to the new 2012 VM.

I've reassociated the hosts with the new SCVMM installation, and every VM host seems to be working well after the agent has been upgraded except for one Windows Server 2008 R2 Core cluster Host in a two-node cluster. In the cluster one of the nodes in the cluster has no problems, but the other node continually says that the Cluster Service is Stopped when the service is not in fact stopped at all.

Troubleshooting steps:

1. I've removed the agent from the cluster hosts by removing the Cluster from SCVMM
2. Restarted the Cluster host
3. Re-installed the VMM agents via the SCVMM console.
   

I can manage the cluster via the Fail-Over Cluster Manager and migrate machines to the node in question without issue. SCVMM also sees all of the virtual machines running on the node as well.

Any suggestions?

were you ever able to resolve this?  I have this same exact issue except with a SCVMM 2008 R2 instance.  5 node 2008 R2 cluster and just one of the nodes keeps giving me grief about the cluster service being stopped but I'm able to manage it via Failover cluster Manager without a hitch.

Hi,

I was confronted to the same problem this week, and we found a solution with Microsoft support.

It seems that the WMI namespace of the failover cluster feature is corrupted.

The solution we found was to empty the node, to evict it from the cluster, uninstall the SCVMM agent (remove from SCVMM), uninstall the failover cluster feature, reboot, install the failover cluster feature, install the agent (add host to SCVMM), and finally reconnect the node in the cluster.

It worked for me, I hope it will work for others.

• Edited by nlecert 19 hours 21 minutes ago
• Proposed as answer by nlecert 19 hours 21 minutes ago

Hi,

I was confronted to the same problem this week, and we found a solution with Microsoft support.

It seems that the WMI namespace of the failover cluster feature is corrupted.

The solution we found was to empty the node, to evict it from the cluster, uninstall the SCVMM agent (remove from SCVMM), uninstall the failover cluster feature, reboot, install the failover cluster feature, install the agent (add host to SCVMM), and finally reconnect the node in the cluster.

It worked for me, I hope it will work for others.

• Proposed as answer by nlecert 19 hours 20 minutes ago

Hi,

I was confronted to the same problem this week, and we found a solution with Microsoft support.

It seems that the WMI namespace of the failover cluster feature is corrupted.

The solution we found was to empty the node, to evict it from the cluster, uninstall the SCVMM agent (remove from SCVMM), uninstall the failover cluster feature, reboot, install the failover cluster feature, install the agent (add host to SCVMM), and finally reconnect the node in the cluster.

It worked for me, I hope it will work for others.

• Edited by nlecert Wednesday, May 20, 2015 11:53 AM
• Proposed as answer by nlecert Wednesday, May 20, 2015 11:53 AM

Hi,

I was confronted to the same problem this week, and we found a solution with Microsoft support.

It seems that the WMI namespace of the failover cluster feature is corrupted.

The solution we found was to empty the node, to evict it from the cluster, uninstall the SCVMM agent (remove from SCVMM), uninstall the failover cluster feature, reboot, install the failover cluster feature, install the agent (add host to SCVMM), and finally reconnect the node in the cluster.

It worked for me, I hope it will work for others.

• Edited by nlecert Wednesday, May 20, 2015 11:53 AM
• Proposed as answer by nlecert Wednesday, May 20, 2015 11:53 AM

Hi,

I was confronted to the same problem this week, and we found a solution with Microsoft support.

It seems that the WMI namespace of the failover cluster feature is corrupted.

The solution we found was to empty the node, to evict it from the cluster, uninstall the SCVMM agent (remove from SCVMM), uninstall the failover cluster feature, reboot, install the failover cluster feature, install the agent (add host to SCVMM), and finally reconnect the node in the cluster.

It worked for me, I hope it will work for others.

• Proposed as answer by nlecert Wednesday, May 20, 2015 11:53 AM

Hi,

I was confronted to the same problem this week, and we found a solution with Microsoft support.

It seems that the WMI namespace of the failover cluster feature is corrupted.

The solution we found was to empty the node, to evict it from the cluster, uninstall the SCVMM agent (remove from SCVMM), uninstall the failover cluster feature, reboot, install the failover cluster feature, install the agent (add host to SCVMM), and finally reconnect the node in the cluster.

It worked for me, I hope it will work for others.

• Proposed as answer by nlecert Wednesday, May 20, 2015 11:53 AM