Comments on The EXPTA {blog}: Failure of FSW Causes Cluster Group to Failover

After installing the failover clustering tools, I ...

2010-02-17T04:34:51.418-08:00

After installing the failover clustering tools, I try and run the "Clsuet Res" command and I get the following error message:

System error 1060 has occurred (0x00000424). The specified service does not exist as an installed service.

I installed the Failover clustering tools, and I c...

2010-02-17T04:14:31.918-08:00

I installed the Failover clustering tools, and I can't launch cluster.exe on the server.

In a previous version of this article, I recommend...

2009-08-18T18:14:05.156-07:00

In a previous version of this article, I recommended unchecking "If restart is unsuccessful, fail over all resources in this service or application" to prevent the FSW from going offline. This is NOT recommended. Doing so will eliminate the cluster's ability to fail the cluster group to another node when there is actually an issue with the witness not related to reboot.

Fanstastic post. I've been looking for this s...

2009-06-15T07:19:21.308-07:00

Fanstastic post. I've been looking for this solution for a while as every time we reboot our hub transports the active CCR node fails over. Coming from Exchange 2003 shared storage style clustering CCR has seemed less robust when we have failovers like this. Great solution, thanks.