FIX: You cannot add a node to a SQL Server 2008 cluster by running the Setup program if there are multiple instances of different languages installed on the same node

Article ID: 974816 - View products that this article applies to.
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.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You configure Microsoft SQL Server 2008 failover cluster in a Windows Server 2008 cluster environment.
  • You install a non-English version of SQL Server 2008 on one node. For example, you install the German version of SQL Server 2008 on a node.
  • You install an English version of SQL Server 2008 on the same node.
  • You run the Setup program of SQL Server 2008 on another node, and then you perform an Add Node operation to add the installation to the English version of SQL Server 2008 failover cluster.
In this scenario, the Add Node operation fails. The following error messages are logged in the SQL Server 2008 Setup log file.

Error message 1

No mapping between account names and security IDs was done.
Error message 2

The installed language for the SQL_Engine_Core_Inst feature is inconsistent between the nodes of the cluster. To cluster an instance, the language of the instance on each node must be the same.
Back to the top | Give Feedback

CAUSE

If you add a node to a SQL Server 2008 cluster, the Setup program starts a validation process to make sure that the language of features are consistent across all nodes. However, if you have multiple instances of different languages installed on the same node, the validation process does not check the language for each instance. Therefore, the validation process fails.
Back to the top | Give Feedback

RESOLUTION

SQL Server 2008

The fix for this issue was first released in Cumulative Update 7. 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:
973601
(http://support.microsoft.com/kb/973601/ )
Cumulative update package 7 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

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
973602
(http://support.microsoft.com/kb/973602/LN/ )
Cumulative update package 4 for SQL Server 2008 Service Pack 1
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. Microsoft recommends 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:
970365
(http://support.microsoft.com/kb/970365/LN/ )
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

REFERENCES

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
Back to the top | Give Feedback

Properties

Article ID: 974816 - Last Review: September 21, 2009 - Revision: 1.2
APPLIES TO
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
Keywords: 
kbsurveynew kbfix kbqfe kbexpertiseadvanced KB974816
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top