Event ID - 1053

Event Id1053
SourceMicrosoft-Windows-FailoverClustering
DescriptionCluster File Share '%1' cannot be brought online because the share could not be created.
Event Information According to Microsoft :

Cause :

This event is logged when Cluster File Share cannot be brought online because the share could not be created.

Resolution :

Confirm file share configuration

Check the following items for more information about why the share could not be created:
  • If possible, determine whether the path to the share has been changed. If so, recreate the share with the correct name.
  • Review event logs, especially for errors related to networks. If a network problem exists, correct the network problem. Ensure that domain controllers are accessible.
  • View all the resources in the clustered file server instance to ensure that they are coming online, and review the dependencies among the resources. Reconfigure as necessary to correct any problems. For more information, see "Viewing properties for a clustered resource," later in this topic.
  • As necessary, get more information about the problem by viewing the event in Event Viewer and looking up the error code. If there is a problem with the configuration of the share, recreate the share. For more information about viewing events and error codes, 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.
Viewing properties for a clustered resource

To view properties for a clustered resource:
  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, 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. 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 states of the clustered resources. If you cannot see the clustered resource that you want to view, expand one or more visible resources until you see the clustered resource.
  6. Right-click the resource you want to view, and then click Properties .
  7. As needed, click tabs to view more resource properties.
  8. To see a diagram of the dependencies configured in the clustered service or application, click Cancel and then, in the Action pane, click Show Dependency Report . Scroll down in the report to see the diagram.
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 :

Verify that the clustered file server can come online, and observe whether additional events are logged regarding resources in the clustered file server.

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.

To verify that a clustered file server 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, 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. If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications .
  4. Click the clustered file server that you want to view. In the center pane, view the status of the clustered file server and its associated resources. As needed, expand one or more visible resources until you see all the clustered resources you want to view.
  5. To bring a clustered file server online, in the console pane, right-click it, and then click Bring this service or application online . You can observe the status of the associated clustered resources as the Cluster service attempts to bring them online.
Reference LinksEvent ID 1053 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.