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.
Note The SkipRules parameter for setup is not a documented feature. You should not use this parameter unless Microsoft CSS Escalation directs you to do this.
Symptoms
Consider the following scenario:
-
The standard Windows Management Instrumentation (WMI) classes are replaced with custom subclasses on a Windows cluster environment.
For example, you download and then install Fujitsu NT-Agent software on a cluster node.
Note To download the Fujitsu NT-Agent software, visit the following Web site: -
You try to set up a Microsoft SQL Server 2008 cluster in this Windows cluster environment.
-
The WMI service pre-check succeeds.
In this scenario, the Setup program fails during the WMI service check phase of the installation process of the SQL Server 2008 cluster. Additionally, you receive the following error message:
“Windows Management Instrumentation (WMI) service” check failed.
Additionally, the following error message is logged in a SQL Server 2008 Setup log file (Detail.txt):
<Date Time> Slp: Rule 'Cluster_IsWMIServiceOperational' detection result: WMI Operational Results WMIServiceIsInstalled =True; WMIServiceIsRunning =True; OSWorkingCheck =True; ComputerSystemWorkingCheck =False; ProcessorWorkingCheck =True; on Machine Node1
<Date Time> Slp: Evaluating rule : Cluster_IsWMIServiceOperational
<Date Time> Slp: Rule running on machine: Node1
<Date Time> Slp: Rule evaluation done : Failed
<Date Time> Slp: Rule evaluation message: The WMI service is not running on the cluster node.
Cause
The Cluster_IsWMIServiceOperational rule usually checks whether the WMI service is running correctly on the node. This problem occurs because the Cluster_IsWMIServiceOperational rule cannot detect the custom WMI service even though the WMI service is running.
Resolution
SQL Server 2008
The fix for this issue was first released in Cumulative Update 9. 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:
977444 Cumulative update package 9 for SQL Server 2008Note 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 The SQL Server 2008 builds that were released after SQL Server 2008 was released
SQL Server 2008 SP1
The fix for this issue was first released in Cumulative Update 7 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:
979065 Cumulative update package 7 for SQL Server 2008 Service Pack 1Note 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:
970365 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.
Workaround
To work around this problem, use one of the following methods.
Method 1
Run following command to install the SQL Server 2008 cluster.
Setup /SkipRules=Cluster_IsWMIServiceOperational /Action=InstallFailoverCluster
Method 2
Before you set up the SQL Server 2008 cluster, unregister the custom WMI classes. Then, register the WMI classes again after you finish setting up the SQL Server 2008 cluster.
Method 3
If you installed the Fujitsu NT-Agent software, remove the software before you set up the SQL Server 2008 cluster. Then, reinstall the Fujitsu NT-Agent software after you finish setting up the SQL Server 2008 cluster.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
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:
822499New 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 Description of the standard terminology that is used to describe Microsoft software updates
