Event ID - 1361

Event Id1361
SourceMicrosoft-Windows-FailoverClustering
DescriptionIPv6 Tunnel address resource '%1' failed to come online because it does not depend on an IP Address (IPv4) resource. Dependency on at least one IP Address (IPv4) resource is required.
Event Information According to Microsoft :

Cause :

This event is logged when IPv6 Tunnel address resource failed to come online because it does not depend on an IP Address (IPv4) resource.

Resolution :

Check IP address settings

If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering." If the event contains an error code that you have not yet looked up, see "Finding more information about error codes that some event messages contain." After reviewing event messages, check the following:
  • Check the address, subnet, and network properties of the IP Address resource.
  • If the resource is an IPv6 Tunnel address resource, make sure it depends on at least one IP Address (IPv4) resource.Also make sure the network supports Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunneling.
  • If the IP Address resource appears to be configured correctly, check the condition of network adapters and other network components used by the cluster.
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.

Viewing properties of an IP Address resource in a cluster

To view properties of an IP Address resource in a cluster:
  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, expand the Name listing for the clustered service or application.
  6. Right-click the IP Address resource you want to view, and then click Properties .
  7. View the properties of the resource. If you also want to view the dependencies for the resource, click the Dependencies tab.
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

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 the clustered service or application that uses the IP Address resource that you want to check.
  5. In the center pane, expand the Name listing for the clustered service or application that uses the IP Address resource that you want to verify. View the status of the IP Address resource.
  6. If an IP Address resource is offline, to bring it online, 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 1361 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.