Article ID: 955949 - Last Review: March 19, 2009 - Revision: 3.0 FIX: Cluster upgrade to SQL Server 2008 fails when SQL Server 2005 cluster nodes have different installed featuresBug #: 50003411 (SQL Hotfix) Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. SYMPTOMSConsider the following scenario:
The SQL Server instance 'InstanceName' which was already upgraded on machine 'ComputerName' has an Instance ID 'InstanceID' that is different than the specified Instance ID 'InstanceID'. Specifying more than one Instance ID for the nodes of clustered SQL Server instance is not supported. Correct this by providing the same Instance ID as on the upgraded node. CAUSEThe Setup program tries to make sure that the features on all the nodes have the same instance ID. However, across the nodes, the Setup program interprets the instance ID for the installed feature as different from the instance ID for the missing feature. RESOLUTIONThe fix for this issue was first released in Cumulative Update 1.
For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956717
(http://support.microsoft.com/kb/956717/
)
Cumulative update package 1 for SQL Server 2008
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released
WORKAROUNDTo work around this issue, remove the mismatched features of SQL Server 2005 that are installed in the cluster environment. Then, run the Setup program again to upgrade the clustered instance of SQL Server 2005 to SQL Server 2008. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base: 956717
(http://support.microsoft.com/kb/956717/LN/
)
Cumulative update package 1 for SQL Server 2008 REFERENCESFor more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates | Article Translations
|
Back to the top
