Failover Cluster Fails To Fail Over

If you have a 2008/R2 failover cluster then it’s possible you may come across the following errors at some point after an unplanned failover:

Unable to obtain the primary cluster name identity token

An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client

As a result, your clustered resources may refuse to start.

Now, assuming that you haven’t done something stupid, like deleting the cluster computer account from AD, you should be able to resolve this problem by right-clicking on the failed CNO on the Summary page of the Failover Cluster Manager, go to “More Options” and then “Repair Active Directory Object”. You should then be able to start all the cluster resources successfully. Thanks to for pointing me in the right direction.

As to what might have caused this problem in the first place? Well that’s still something of a mystery to me at the moment…

8 Replies to “Failover Cluster Fails To Fail Over”

  1. That has saved me from a dead disk nightmare.

    Looks like when I copied the non-o/s responsive disk something had gone wrong with the cluster when the disk failed. (Yeah I know it should be morrored, but it’s clustering dev on a shoe string!)

    Many thanks!!

  2. It is working!!! So simple!!! Thaqnk you very much!!!
    There are a lot of different suggestion in the internet regarding this issue. But the right solution I’ve found only here. An it is so simple. Thank you again.

  3. Repairing the active directory object as directed above fixed my issue. Thanks very much

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.