Share via


Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted.

Question

Monday, May 27, 2013 3:05 PM

Hi All, 

I'm facing SQL Cluster failover problem, I have 2 server, named: SQL01 and SQL02. currently SQL02 owner of Quorum,  DTC and SQL. Error event ID as follow:

The description for Event ID 1205 from source Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

*The following information was included with the event: *

SQL Server (MSSQLSERVER)

The description for Event ID 1069 from source Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

*The following information was included with the event: *

SQL Network Name (SQLSWITCH)
SQL Server (MSSQLSERVER)

other errors are same, tell that the component that raises this event is not installed on your local computer or the installation is corrupted.

anyone can tell me to fix it?

Thanks.

Endrik

Endrik | blog: itendrik.wordpress.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

All replies (4)

Tuesday, May 28, 2013 7:43 AM ✅Answered

Hi,

> Manual Bring this service online still no luck.

Which service? SQL server service or cluster service?

Is cluster still working?

Please run cluster validation test and post the error messages.

Evicting a cluster node is not a good idea, the only times you should ever evict a node are under the following scenarios:

  • Replacing a node with different hardware.
  • Reinstalling the operating system.
  • Permanently removing a node from a cluster.
  • Renaming a node of a cluster.

Let’s take a look at some very common scenarios where I’ve seen evicting a node used improperly.

Cluster service won’t start on node 2 of a cluster. Node 2 is evicted from the cluster. The original problem with why the cluster service didn’t start is still there but now that same problem also prevents node 2 from coming back into the cluster.

Resources don’t failover to node 2. Every time a failover occurs, the disks don’t come online and fail back to node 1. One of the nodes is evicted and then added back to the cluster. None of this addresses the disk issue so problem still remains.

Please refer to above post mentioned event ID troubleshoot article or following articles to troubleshooting and resolve cluster node issues:

Windows Server 2008 R2: Failover Clustering Troubleshooting Scenarios
http://technet.microsoft.com/en-us/magazine/hh489314.aspx
Windows Server 2008 R2: Troubleshooting Failover Clusters
http://technet.microsoft.com/en-us/magazine/hh472674.aspx

If possible give us some screen capture to help understand your cluster issue.

For more information please refer to following MS articles:

When should I evict a cluster node?
http://blogs.technet.com/b/askcore/archive/2010/03/03/when-should-i-evict-a-cluster-node.aspx

Lawrence

TechNet Community Support


Tuesday, May 28, 2013 5:44 AM

Hi,

This is a two node SQL cluster, two node named SQL01 and SQL 02. What’s the OS version of these cluster node server?

You mentioned SQL02 is the owner of Quorum, which kind of quorum do you use, Node and Disk majority?

The error message “The description for Event ID xxxx from source Microsoft-Windows-FailoverClustering cannot be found” that means system can’t read detailed information of cluster event. But these error messages give us event number.

You can refer to following articles to troubleshoot event ID 1205 and event ID 1069 error:

Event ID 1205 — Clustered Service or Application Availability
http://technet.microsoft.com/en-us/library/cc773525(v=WS.10).aspx
Event ID 1069 — Clustered Service or Application Availability
http://technet.microsoft.com/en-us/library/cc756225(v=WS.10).aspx

Lawrence

TechNet Community Support


Tuesday, May 28, 2013 5:50 AM

OS version: WS 2008 R2 Sp1 Enterprise Edition

Quorum: Node and Disk Majority.

Manual Bring this service online still no luck.

my idea:

1. Evict the server from Cluster

2. Re-join the server to cluster

is it good idea?

Thanks.

Endrik

Endrik | blog: itendrik.wordpress.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


Tuesday, May 28, 2013 8:31 AM

hi Lawrence, 

Download here for the result validation test (offline),

Validation Test Link

Please check it

Thanks.

Endrik

Endrik | blog: itendrik.wordpress.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.