SQL Server cluster failover fails with Error Code: 0x80071398
2015-02-09 14:52
726 查看
今天遇到一个问题,手动Failover SQL Cluster 到另外一台Node失败,错误:
SQL Server cluster failover fails with Error Code: 0x80071398
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
原因是:IP 资源里面Possabile Node丢失了,重新加上就OK了。下面这篇文章讲的很详细: http://blogs.msdn.com/b/alexfeng/archive/2013/07/23/sql-server-cluster-failover-fails-with-error-code-0x80071398.aspx
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.
SQL Server cluster failover fails with Error Code: 0x80071398
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
原因是:IP 资源里面Possabile Node丢失了,重新加上就OK了。下面这篇文章讲的很详细: http://blogs.msdn.com/b/alexfeng/archive/2013/07/23/sql-server-cluster-failover-fails-with-error-code-0x80071398.aspx
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.
相关文章推荐
- MS SQL错误:SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems
- The module ... was loaded but the call to DllRegisterServer failed with error code 0x80070005
- Sql Server Error: No error message available, result code: DB_E_ERRORSOCCURRED(0x80040E21).
- sqlserver errorcode
- SQL1159 Initialization error with DB2 .NET Data Provider, reason code 2;reason code 10
- Error: Application server fails to start with the following error WSNAT_CAT:1008: ERROR: Could not establish listening address o
- 安装了VS2010 sp1 后再安装ASP.NET MVC 3.0的问题(Final Result: Installation failed with error code: (0x80070643), "安装时发生严重错误 " (Ela)
- Couldn't register ***.**** with the bootstrap server. Error: unknown error code
- (WSFC) resource control API returned error code 5057 & Microsoft SQL Server, Error: 41009
- SQL SERVER Error code: 0x80004005
- (SQL2005 Server Express服务启动失败,关闭VIA协议就好了)TDSSNIClient initialization failed with error 0x7e, status code 0x60.
- EF Code First - Add-Migration fails with Could not load file or assembly error
- SQL - A connection was successfully established with the server, but then an error occurred during the pre-login handsha
- Error while preforming database login with the "sqlserver" driver Unable to create...
- 解决 OpenSSH - “ Error: Connection closed by server with exitcode 128 ” 错误(ZT)
- Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection. [SQLSTATE 28000] (Error 18452). The st
- Windows CE: LoadLibrary Fails with Error Code 193
- MySQL:Foreign key fails with error Error Code: 1452.
- .SQLErrorCodeSQLExceptionTranslator - Unable to translate SQLException with Error code '0', will no
- Couldn't register com.X.XX with the bootstrap server. Error: unknown error code.