Event ID - 1057

Event Id	1057
Source	Microsoft-Windows-FailoverClustering
Description	The cluster database could not be loaded due to error '%1' on node '%2'. The file may be missing or corrupt. Automatic repair might be attempted.
Event Information	According to Microsoft : Cause : This event is logged when the cluster database could not be loaded due to error on node. Resolution : Ensure that a good copy of the cluster configuration is available to the node When the cluster configuration on a node is missing or corrupt, the Cluster service cannot load the configuration and therefore cannot start. Where possible, the Cluster service will obtain the latest cluster configuration from other nodes in the cluster. Ensure that other nodes are started. If the only node or nodes that can be started appear to have a missing or corrupt cluster configuration database, you will probably need to restore one of the nodes from a system state backup. (For a failover cluster node, the system state backup includes the cluster configuration.) 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." 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: 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. 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: View the event, and note the error code. 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 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 start the Cluster service on a node and confirm that it runs successfully: 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. In the console tree, select Nodes and expand the tree underneath it. In the center pane, view the status for each node. If the status is Up , the Cluster service is started on that node. To start the Cluster service on a node, right-click the node, click More Actions , and then click Start Cluster Service .
Reference Links	Event ID 1057 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