Event ID - 1226

Event Id1226
SourceMicrosoft-Windows-FailoverClustering
DescriptionNetwork Name resource '%1' (with associated network name '%2') has Kerberos Authentication support enabled. Failed to add required credentials to the LSA - the associated error code '%3' indicates insufficient privileges normally required for this operation. The required privilege is 'Trusted Computing Base' and must be locally enabled on each node comprising the cluster.
Event Information According to Microsoft :

Cause :

This event is logged when Network Name resource has Kerberos Authentication support enabled.

Resolution :

Confirm proper privileges

For the Network Name resource, the privileges needed to add the network name credentials to the local security policy are not assigned. Get more information about the problem by viewing the event in Event Viewer and looking up the error code, so that you can assign the necessary privileges to the appropriate account or accounts. For more information, see "Opening Event Viewer and viewing events related to failover clustering" and "Finding more information about error codes that some event messages contain," later in this topic.

Important : You must stop and restart the Cluster service when you perform this procedure, and you might need to perform this procedure on all nodes in the cluster. For more information, see "Restarting the Cluster service on a node," later in this topic.

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 viewing events related to failover clustering

To open Event Viewer and view events related to failover clustering:
  1. 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 .
  2. In the console tree, expand Diagnostics, expand Event Viewer , expand Windows Logs , and then click System .
  3. 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 .
  4. To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.
Finding more information about the error codes that some event messages contain

To find more information about the error codes that some event messages contain:
  1. View the event, and note the error code.
  2. Look up more information about the error code in one of two ways:
  • Search System Error Codes.
  • Click Start , point to All Programs , click Accessories , click Command Prompt , and then type:
NET HELPMSG errorcode

Restarting the Cluster service on a node

To restart the Cluster service on a node:
  1. 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, in the console tree, make sure Failover Cluster Management is selected. Then under Management , click Validate a Configuration .
  3. If the console tree is collapsed, expand the tree under the cluster you want to manage.
  4. Expand the console tree under Nodes .
  5. Right-click the node that you want to start and then click More Actions . If Stop Cluster Service is available, click it. Otherwise, skip to the next step.
  6. Right-click the node that you want to start, click More Actions, and then click Start Cluster Service.
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 an IP Address resource can come online

To verify that an IP Address resource can come online:
  1. 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, in the console tree, make sure Failover Cluster Management is selected. Then under Management , click Validate a Configuration .
  3. If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications .
  4. In the console tree, click a clustered service or application.
  5. In the center pane, view the status of the Network Name resource you want to verify.
  6. 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 .
To perform a quick check on the status of a resource, you can run the following command.

Using a command to check the status of a resource in a failover cluster

To use a command to check the status of a resource in a failover cluster:
  1. On a node in the cluster, click Start , point to All Programs , click Accessories , right-click Command Prompt , and then click Run as administrator .
  2. Type:
    CLUSTER RESOURCE ResourceName /STATUS
    If you run the preceding command without specifying a resource name, status is displayed for all resources in the cluster.
Reference LinksEvent ID 1226 from Microsoft-Windows-FailoverClustering

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.
 Refresh