Consider the following scenario:
- You create a Microsoft SQL Server 2005 failover cluster on a Windows Server 2008 cluster.
- The nodes within the cluster have computer names that have all lowercase characters or that have mixed case characters.
- You apply service packs or other hotfixes on this SQL Server 2005 failover cluster.
In this scenario, you encounter one of the following symptoms.Symptom 1
After you apply service packs or other hotfixes, an error message that resembles the following is logged in the service pack setup log or the hotfix setup log:
MSI (s) (<number>!<number>) [<number>:<number>:<number>:<number>]: PROPERTY CHANGE: Adding SqlClusterSec property. Its value is '1'.
When you try to create a maintenance plan, you receive the following error messages:
Invalid column name 'from_msx'.
Invalid column name 'has_targets'. (Microsoft SQL Server, Error: 207)
When you try to perform a DatabaseMail operation, you receive the following error message:
The activated proc [dbo].[sp_sysmail_activate] running on queue msdb.dbo.ExternalMailQueue output the following: 'Error executing extended stored procedure: Invalid Parameter'
These problems occur when the node names are in lowercase. The datastore of the SQL Server Setup program also presents these node names in lowercase. However, Windows Installer presents the node names in all uppercase. The Setup program determines that the package is run on the passive node. So, the Setup program does not upgrade the resource database and other system databases.
Therefore, the problems that are mentioned in the "Symptoms" section occur.Note
You can find the node names by right-clicking My Computer
, and then selecting Properties
from the popup menu.
The fix for this issue was first released in Cumulative Update 9 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative update package 9 for SQL Server 2005 Service Pack 3
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 2005 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:
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
This cumulative update updates the mssqlsystemresource
database. Additionally, it runs other upgrade scripts that were not run during the original service pack installation.
When this problem occurs, the SQL Server error log file indicates that the resource database has an earlier build version than the correct build version. The error log file resembles the following:
<DateTime> Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
<DateTime> spid5s Starting up database 'mssqlsystemresource'.
<DateTime> spid5s The resource database build version is 9.00.2047. This is an informational message only. No user action is required.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To confirm that this update is installed successfully, use one of the following methods.Method 1
Check the value of the SqlClusterSec
property that is in the update setup log file for the active node. If the value of the SqlClusterSec
property is 0, the update is installed correctly. The log entry resembles the following:
PROPERTY CHANGE: Adding SqlClusterSec property. Its value is '0'.Method 2
Verify that the resource database version is changed to <9.00.CU9BuildNumber> after you install this update. To do this, run the following query:
For more information about how to view and read SQL Server setup log files,
visit the following Microsoft Developer Network (MSDN) Web site:
For information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for SQL Server 2005
For more information about new features and improvements in SQL Server 2005 Service Pack 3, visit the following Microsoft Web site:
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:
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:
Description of the standard terminology that is used to describe Microsoft software updates