SQL Server cluster failover fails with Error Code: 0x80071398
I have installed a 3-node SQL Server 2012 failover cluster on Windows Server 2012 few days ago, and it has been running very well. Until today, I found that I could not manually failover the SQL cluster service from node 3 to node 1, and failed with the following information:
The operation has failed
The action 'Move' did not complete
The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group
Here is a screenshot:
The error is a bit strange to me as I can see the Node 1 was listed there when I performed the Move operation, and the cluster installation was successfully on all 3 nodes. At this point, I did some research, and found someone mentioned that the Node 1 might be not a possible owner for one or more of SQL Server failover cluster dependencies. After several clicks, I found that the failed Node 1 was not a possible owner of IP address of SQL Server virtual server name like below, once I selected it back, the failover succeeded.
Hope this helps :-)
Comments
Anonymous
March 04, 2014
Thanks a lot! This helped me to solve the same issue.Anonymous
April 25, 2014
I have the same problem as you!You topic help me to solve.Thanks a lot!Anonymous
May 02, 2014
Thanks!Problem solved.Anonymous
June 21, 2014
Hi, The same issue is happening for me when I tried to move the resource manully.My server is windows 2008 R2. I could see the preferrec owner but i was unable to view possible owner list. Can you pls help me to found the owner and fix the issue.Anonymous
July 20, 2014
Thank you very much! Solve my problem.Anonymous
November 13, 2014
Спасибо, помогло. Всё время забываю это проверять.Anonymous
March 27, 2015
Thank you so much. We have the same issue and this information helps solve the issue.Anonymous
April 07, 2015
I have the same problem as you! You topic help me to solve. Thanks a lot! :)Anonymous
August 06, 2015
Just saved me a ton of time, thanks :)Anonymous
November 02, 2015
Thank you, it solved my problem too.