Upgrade to SQL 2008 from 2005 (cluster) fails with The cluster group 'SQL GROUP' could not be moved from node 'NODENAME1' to node 'null' , 0x8007139F

Problem

We try to upgrade to SQL 2008 from SQL 2005 in a cluster setup and it fails on the Active node with the following error:

From the Summary.txt

There was an error during the SQL Server upgrade operation. Setup failed to move the failover cluster resource group and bring it online. To continue this upgrade operation, bring the resource group online manually and retry Setup. Reason: The cluster group 'SQL GROUP' could not be moved from node 'NODENAME1' to node 'null'. Error: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)

Environment

SQL Server Name : (Active node) NODENAME1, (Passive node) NODENAME2

Symptoms

·         The upgrade succeeded on the passive node but the upgrade failed on the active node :

Overall summary:

  Final result: SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server using the following command line, and then rerun SQL Server Setup. Uninstall command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLEngine,Replication,FullText

  Exit code (Decimal): -2068643839

  Exit facility code: 1203

  Exit error code: 1

  Exit message: SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server using the following command line, and then rerun SQL Server Setup. Uninstall command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLEngine,Replication,FullText

·         From detail.txt we saw the following errors :

2010-09-03 09:47:08 Slp: There was a problem moving the cluster group to an upgraded node. Message: The cluster group 'SQL GROUP' could not be moved from node ' NODENAME1 ' to node 'null'. Error: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)

2010-09-03 09:47:08 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ShutdownNonInstance and scenario ShutdownNonInstance.

2010-09-03 09:47:08 Slp: There was an error during the SQL Server upgrade operation. Setup failed to move the failover cluster resource group and bring it online. To continue this upgrade operation, bring the resource group online manually and retry Setup. Reason: The cluster group 'SQL GROUP' could not be moved from node ' NODENAME1 ' to node 'null'. Error: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)

2010-09-03 09:47:08 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ShutdownNonInstance and scenario ShutdownNonInstance.

2010-09-03 09:47:08 Slp: Microsoft.SqlServer.Configuration.Cluster.ClusterException: There was an error during the SQL Server upgrade operation. Setup failed to move the failover cluster resource group and bring it online. To continue this upgrade operation, bring the resource group online manually and retry Setup. Reason: The cluster group 'SQL GROUP' could not be moved from node ' NODENAME1 ' to node 'null'. Error: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F) ---> Microsoft.SqlServer.Configuration.Cluster.ClusterException: The cluster group 'SQL GROUP' could not be moved from node ' NODENAME1 ' to node 'null'. Error: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F) ---> System.Runtime.InteropServices.COMException (0x8007139F): The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)

2010-09-03 09:47:08 Slp: at MSClusterLib.ISClusResGroup.Move(Object varTimeout, Object varNode)

2010-09-03 09:47:08 Slp: at Microsoft.SqlServer.Configuration.Cluster.ClusterGroup.Move(Int32 timeout, ClusterNode toNode)

2010-09-03 09:47:08 Slp: --- End of inner exception stack trace ---

2010-09-03 09:47:08 Slp: at Microsoft.SqlServer.Configuration.Cluster.ClusterGroup.Move(Int32 timeout, ClusterNode toNode)

2010-09-03 09:47:08 Slp: at Microsoft.SqlServer.Configuration.ClusterConfiguration.FailoverClusterNamePrivateConfigObject.Upgrade(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb, Version fromVersion)

2010-09-03 09:47:08 Slp: --- End of inner exception stack trace ---

2010-09-03 09:47:08 Slp: at Microsoft.SqlServer.Configuration.ClusterConfiguration.FailoverClusterNamePrivateConfigObject.Upgrade(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb, Version fromVersion)

2010-09-03 09:47:08 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)

2010-09-03 09:47:08 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)

2010-09-03 09:47:08 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)

2010-09-03 09:47:08 Slp: Exception: Microsoft.SqlServer.Configuration.Cluster.ClusterException.

2010-09-03 09:47:08 Slp: Source: Microsoft.SqlServer.Configuration.Cluster.

2010-09-03 09:47:08 Slp: Message: There was an error during the SQL Server upgrade operation. Setup failed to move the failover cluster resource group and bring it online. To continue this upgrade operation, bring the resource group online manually and retry Setup. Reason: The cluster group 'SQL GROUP' could not be moved from node ' NODENAME1 ' to node 'null'. Error: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F).

2010-09-03 09:47:08 Slp: Inner exception:

·         What was interesting in the detail.txt were the following lines:

2010-09-03 09:47:08 Slp: Adding possible owner node 'NODENAME2' to resource 'SQL Network Name (SQL001)'

2010-09-03 09:47:08 Slp: Removing possible owner node 'NODENAME1' from resource 'SQL Network Name (SQL001)'

Resolution

·         We checked the possible owners from the cluster administrator/failover cluster manager for all the resources in the SQLgroup and saw that NODENAME1 is not a possible owner for SQL Network name resource

· It is recommended to Check the dependencies for the SQL IP resource as well.

·         We added the node NODENAME1 back as a possible owner for the SQL Network Name resource.

·         The Active node upgrade went through successfully after this.

Regards,
Amrutha Varshini J

Microsoft SQL support

Reviewed by,

Sudarshan Narasimhan & Shamik Ghosh

TL, Microsoft SQL server support