cluster service has determined that this node does not have the latest copy of cluster configuration data

Microsoft.Windows.2008.Cluster.Management.Monitoring.cluster.service.has.determined.that.this.node.does.not.have.the.latest.copy.of.cluster.configuration.data (Rule)

Knowledge Base article:

One of the nodes does not contain the latest copy of the cluster configuration, which means the Cluster service will not start on that node. Try starting the Cluster service on all other nodes in the cluster. If the Cluster service can be started on a node with the latest copy of the cluster configuration data, then the node that previously could not be started will probably be able to obtain the latest copy and then join the cluster successfully.

If there are no nodes available with the latest copy of the cluster configuration, use the Force Cluster Start command. This action should be considered a last resort, because some cluster configuration changes could be lost.

To perform the following procedure, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

To force the cluster to start:

  1. On a node that contains a copy of the cluster configuration that you want to use, open the Failover Cluster Management snap-in.

    To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

  2. In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
  3. Click the cluster, and then under Actions (on the right), click Force Cluster Start. (Under most circumstances, that is, when no error has been triggered by the existence of older copies of the cluster configuration, this command is not available in the Windows interface.)

    Note   When you use this command on a given node, the copy of the cluster configuration that is on that node will be treated as the authoritative copy of the configuration and will be replicated to all other nodes.

Element properties:

TargetMicrosoft.Windows.2008.Cluster.Monitoring.Service
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
cluster service has determined that this node does not have the latest copy of cluster configuration data
{0}

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.2008.Cluster.EventProvider Default
WA WriteAction Microsoft.Windows.Cluster.GenerateAlertAction.SuppressedByDescription Default

Source Code:

<Rule ID="Microsoft.Windows.2008.Cluster.Management.Monitoring.cluster.service.has.determined.that.this.node.does.not.have.the.latest.copy.of.cluster.configuration.data" Enabled="onEssentialMonitoring" Target="Clus2008Library!Microsoft.Windows.2008.Cluster.Monitoring.Service" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.Windows.2008.Cluster.EventProvider">
<Criteria>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>1561</Value>
</ValueExpression>
</SimpleExpression>
</Criteria>
<LogName>System</LogName>
<PublisherName>Microsoft-Windows-FailoverClustering</PublisherName>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WA" TypeID="ClusLibrary!Microsoft.Windows.Cluster.GenerateAlertAction.SuppressedByDescription">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.2008.Cluster.Management.Monitoring.cluster.service.has.determined.that.this.node.does.not.have.the.latest.copy.of.cluster.configuration.data.AlertMessage"]$</AlertMessageId>
</WriteAction>
</WriteActions>
</Rule>