The computer object associated with a cluster network name resource could not be updated.
Event Details
Event ID: | 1222 |
Source: | Microsoft-Windows-FailoverClustering |
Symbolic Name: | RES_NETNAME_SET_PERMISSIONS_FAILED |
Message: | The computer object associated with cluster network name resource '%1'could not be updated. The text for the associated error code is: %2 The cluster identity '%3'; may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.Search System Error Codes ( http://go.microsoft.com/fwlink/?LinkId=83027). |
These events will be logged if one of the following actions was taken:
There was a change to the shared folders that prevents access by the SYSTEM account.
The shared folder was deleted or changed.
Check Active Directory configuration
If you do not currently have Event Viewer open, see "Opening Event Viewer and view events related to failover clustering." After reviewing event messages, check the following:
Confirm that the cluster nodes can communicate with one or more domain controllers. Confirm that the networks in the nodes are enabled, one or more writeable domain controllers are available on the network, and that elements of the network such as hubs, switches, or bridges appear to be functioning.
On a domain controller, use Active Directory Users and Computers to confirm that a computer account (computer object) exists with the same name as the Network Name resource, and that the account is enabled.
On a domain controller, for the computer account that you confirmed in the previous item, make sure that in the account permissions, Full Control has been assigned to the computer account of the cluster, which will have the same name as the cluster.
To perform the following procedures, 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.
Opening Event Viewer and view events related to failover clustering
If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.
Verify
To perform the following procedures, 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.
Verifying that a Network Name resource can come online
To verify that a Network Name resource can come online:
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.
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.
If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
In the console tree, click a clustered service or application.
In the center pane, view the status of the Network Name resource you want to verify.
If a Network Name resource is offline, to bring it online, in the center pane, right-click the resource and then click Bring this resource online.
Target | Microsoft.Windows.6.2.Cluster.Monitoring.Service | ||
Category | Alert | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
|
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.6.2.Cluster.EventProvider | Default |
WA | WriteAction | Microsoft.Windows.Cluster.GenerateAlertAction.SuppressedByDescription | Default |
<Rule ID="Microsoft.Windows.6.2.Cluster.Management.Monitoring.network.name.resource.failed.to.set.permissions" Enabled="true" Target="Clus8Library!Microsoft.Windows.6.2.Cluster.Monitoring.Service" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.Windows.6.2.Cluster.EventProvider">
<Criteria>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>1222</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>1</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.6.2.Cluster.Management.Monitoring.network.name.resource.failed.to.set.permissions.AlertMessage"]$</AlertMessageId>
</WriteAction>
</WriteActions>
</Rule>