Quantcast
Viewing all articles
Browse latest Browse all 7627

SQL Server 2008 R2 SP1 Fails on Rule "Not clustered or the cluster service is up and online"

We have a consolidated stand-alone server running multiple instances on SQL Server 2008 R2.  Some instances are RTM and some are SP1.  I created a new instance and wanted to upgrade it to SP1 but when I executed the installer the check screen failed on rule "Not clustered or the cluster service is up and online."

When I check out c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121015_130216\Detail.txt the pertinent section is below.

2012-10-15 13:02:59 Slp: Initializing rule      : Not clustered or the cluster service is up and online.
2012-10-15 13:02:59 Slp: Rule applied features  : ALL
2012-10-15 13:02:59 Slp: Rule is will be executed  : True
2012-10-15 13:02:59 Slp: Init rule target object: Microsoft.SqlServer.Configuration.Cluster.Rules.ClusterServiceFacet
2012-10-15 13:09:02 Slp: Unexpected error 
2012-10-15 13:09:02 Slp:    at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at Microsoft.SqlServer.Configuration.Cluster.Rules.WMIInterop.Service.ServiceCollection.ServiceEnumerator.MoveNext()
   at Microsoft.SqlServer.Configuration.Cluster.Rules.ClusterServiceFacet.Microsoft.SqlServer.Configuration.RulesEngineExtension.IRuleInitialize.Init(String ruleId)
   at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.Execute(Boolean stopOnFailure)

2012-10-15 13:09:02 Slp: Rule initialization failed - hence the rule result is assigned as Failed

I tried searching a bit and found some discussion of WMI however when I check the authorities for WMI everything comes back OK.  Plus, like I said, we have instances on the server at SP1 already.

Any ideas are appreciated :-)

- Dave


Viewing all articles
Browse latest Browse all 7627

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>