July 24, 2017 at 5:05 pm
I have a 2 node windows cluster set up. node 1 (active node) fails to roll over to node 2 (passive node) after I have upgrade sql to 2016 from 2015. Using Windows Server 2012. Here is below error message I get from the SQL roll looking at it's Critical Events error message. Anybody experiencing the same issue? No serious error messages i see from Event Viewer either. Let me know appreciate the help.
"Move of cluster role 'SQL Server (MSSQLSERVER)' for drain could not be completed. The operation failed with error code 0x138D."
July 25, 2017 at 4:05 am
check the cluster events for more info and the sql server error log
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 25, 2017 at 11:00 am
The Cluster events has the same error message. Nothing from SQL Error logs.
July 25, 2017 at 3:42 pm
Found more detailed error message as described above? I have read that this message is because the "Possible Owners" was not selected and I doubled checked an in my case both nodes are checked. Anybody?
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
July 26, 2017 at 2:52 am
Can you please give more information on how you did the upgrade. I assume that on the passive node, had you already run the sql installation media and done "add node to cluster" right?
Also check the properties on all objects within the group (e.g server name, ip address, disks etc) and make sure they all have both nodes as possible owners
July 26, 2017 at 5:40 am
JP10 - Tuesday, July 25, 2017 3:42 PMFound more detailed error message as described above? I have read that this message is because the "Possible Owners" was not selected and I doubled checked an in my case both nodes are checked. Anybody?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
On what resources did you check the possible owners list?
Please return the results of the following
Get-ClusterResource | Get-ClusterOwnerNode
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 26, 2017 at 6:15 am
This was removed by the editor as SPAM
July 26, 2017 at 11:05 am
Yes the node is already included in the cluster. Also, yes to checking if server name, ip address, disks are all checked for "Possible Owners".
I ran the command you posted and noticed that the "SQL Network Name ()" only has one of the two nodes. My sys admin does not know why everything looks good on his end and both nodes are all checked as "Possible Owners". Any reason why this would occur? The SQL role failed over fine before I upgraded the passive node to SQL 2016 from 2014.
Appreciate the help guys.
July 26, 2017 at 12:34 pm
Found the issue guys. I was not checking the "Possible Owner" setting under the SQL Server Role. In FailOver Cluster Manager click on left hand side Roles then click on the SQL Server Role. Below you will see Server Name right click server name\Advanced Policies and sure enough the second node was unchecked. For some reason after the SQL 2016 upgrade this was unchecked. Note to self CHECK FOR THIS FOR CLUSTERS! =) Fyi this was checked before because I tested a failover before the upgrade. Thanks all for your help!
July 27, 2017 at 5:38 am
JP10 - Wednesday, July 26, 2017 11:05 AM@perry,I ran the command you posted and noticed that the "SQL Network Name ()" only has one of the two nodes.
And that's exactly what i was expecting to see returned 😉
JP10 - Wednesday, July 26, 2017 11:05 AM
My sys admin does not know why everything looks good on his end and both nodes are all checked as "Possible Owners". Any reason why this would occur? The SQL role failed over fine before I upgraded the passive node to SQL 2016 from 2014.Appreciate the help guys.
Well i'll tell you shall I.
Failover of the instance is controlled by the possible owners list on the SQL server network name, it's dynamic too and is modified by the sql server installer.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 27, 2017 at 5:49 am
JP10 - Monday, July 24, 2017 5:05 PMI have a 2 node windows cluster set up. node 1 (active node) fails to roll over to node 2 (passive node) after I have upgrade sql to 2016 from 2015. Using Windows Server 2012. Here is below error message I get from the SQL roll looking at it's Critical Events error message. Anybody experiencing the same issue? No serious error messages i see from Event Viewer either. Let me know appreciate the help."Move of cluster role 'SQL Server (MSSQLSERVER)' for drain could not be completed. The operation failed with error code 0x138D."
can you detail how you did the upgrade, step by step
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 27, 2017 at 10:30 am
Hey Perry,
I basically ran Data Migration Assistant first on the active node, then ran the SQL upgrade on the passive node, rebooted passive node, then failed over to the passive node. Why do you ask is there something I missed?
July 28, 2017 at 3:38 am
JP10 - Thursday, July 27, 2017 10:30 AMHey Perry,
I basically ran Data Migration Assistant first on the active node, then ran the SQL upgrade on the passive node, rebooted passive node, then failed over to the passive node. Why do you ask is there something I missed?
have you run the upgrade on both nodes?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply