Windows Cluster Service fails to start after ITCM Installation on Windows Server 2008 R2.


Article ID: 52373


Updated On:


CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER CA Server Automation CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager



If ITCM is installed on Windows Server 2008 R2 machine with the Failover Clustering feature installed, the Cluster Service may fail to start with the following errors in system event viewer.

  • Cluster resource 'Quorum' (resource type '', DLL 'clusres.dll') either crashed or deadlocked. The Resource Hosting Subsystem (RHS) process will now attempt to terminate, and the resource will be marked to run in a separate monitor.

  • The cluster resource host subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due to a problem in a resource DLL.


If you are using the Failover Clustering feature on Windows Server 2008 R2, you must apply the Microsoft hotfix KB978527.

The Microsoft hotfix KB978527 can be downloaded from the following location:

Note:- Please be aware that the ITCM Agent does not support failover between the cluster Nodes. The ITCM agent can be installed on all cluster Nodes and each cluster Node will be visible as a separate system on the Domain Manager.


Component: TNGAMO