Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Event ID 1146 — Cluster Service Startup. Updated: December 5, 2007. Applies To: Windows Server 2008. The Cluster service is the essential software component that controls all aspects of failover cluster operation and manages the cluster configuration database. For Windows Server 2012 and Windows Server 2012 R2 cluster. Run PS command: cluster node /status. Is the cluster service continuously running and available on all the nodes? Solution for cluster service is failing. If cluster service is failing, troubleshoot using this article: Windows Server 2008 and 2008R2 Failover Cluster Startup Switches. Assume that you set up a failover cluster in a Windows Server 2008 or Windows Server 2008 R2 environment. However, after the Cluster service runs for a long. Note that the Failover Clustering feature is included in server products such as Windows Server 2008 R2 Enterprise and Windows Server 2008 R2 Datacenter. The Failover Clustering feature is not included in Windows Server 2008 R2 Standard or Windows Web Server 2008 R2. Event id 4869 - User mode health monitoring has detected that the system is not being responsive. The Failover cluster virtual adapter has lost contact with the 'C: Windows Cluster rhs.exe' process with a process ID '0x2154', for '1200' seconds.

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Event ID 1282 — Node Membership in Cluster

Windows Server Failover Clustering

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

Failover cluster nodes must have the ability to start the Cluster service, form a cluster (when a given node starts but no other nodes are up) and join a cluster (when a given node starts and discovers that one or more nodes are already up). This requires that certain conditions be met, for example, failover cluster nodes must run compatible versions of the operating system.

Event Details

Resolve
Confirm that the node can form or join with a cluster

Review the event log for other events associated with this issue. You might be able to correct this issue by restarting the Cluster service. For more information, see “Restarting the Cluster service on a node.”

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.

Restarting the Cluster service on a node

To restart the Cluster service on a node:

Event Id 1146 Failover Clustering Windows 2008 R2 End Of Support

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.
4. Expand the console tree under Nodes.
5. Right-click the node that you want to restart, click More Actions, and then click Stop Cluster Service.
6. Right-click the node that you want to restart, click More Actions, and then click Start Cluster Service.

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 (http://go.microsoft.com/fwlink/?LinkId=83027).
   • Click Start, point to All Programs, click Accessories, click Command Prompt, and then type:

     NET HELPMSG errorcode

Verify

To perform this 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.

Verifying that the Cluster service is started on all the nodes in a failover cluster

To verify that the Cluster service is started on all the nodes in a failover cluster:

Sql Server Failover Clustering

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 click Nodes.
4. View the status for each node. If a node is Up, the Cluster service is started on that node.

Another way to check whether the Cluster service is started is to run a command on a node in the cluster.

Using a command to check whether the Cluster service is started on a node

Event Id 1146 Failover Clustering Windows 2008 R2 Domain Controller

To use a command to check whether the Cluster service is started on a node:

1. On the node that you are checking, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
2. Type:

   CLUSTER NODE /STATUS

   If the node status is Up, the Cluster service is started on that node.

Related Management Information

Event Id 1146 Failover Clustering Windows 2008 R2 To Windows 2012 R2

Related: