Getting bizarre error while installing SQL 2008 SP2 on standalone server

  • While trying to upgrade a SQL-2008 R2 installation to SQL 2008 SP2 I'm getting the following error in the rule-checking phase of the installation:

    Rule "Not clustered or the cluster service is up and online." failed.

    The machine is clustered, but the cluster is not online or cannot be accessed from one of its nodes.

    To continue determine why the cluster is not online and rerun setup instead of rerunning the rule since

    the rule can no longer detect a cluster environment correctly.

    In the Rule-Check dialog I see these 3 items, among others:

    ...

    - Not clustered or the cluster service is up and online - Status: failed

    - Cluster group owned by local computer - Status: passed

    - Cluster Resource DLL Update Restart Check: passed

    If the server is not clustered, why do I have the last 2 items? It's weird...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • It looks like I ran out of memory while applying the SP (!), so setup assumed there was an actual problem with the server configuration;

    I have restarted the server and will try again:

    See section taken from the Detail.txt file in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20101006_145133:

    2:09 Slp: Initializing rule : Not clustered or the cluster service is up and online.

    2010-10-06 14:52:09 Slp: Rule applied features : ALL

    2010-10-06 14:52:09 Slp: Rule is will be executed : True

    2010-10-06 14:52:09 Slp: Init rule target object: Microsoft.SqlServer.Configuration.Cluster.Rules.ClusterServiceFacet

    2010-10-06 15:00:32 Slp: Out of memory

    2010-10-06 15:00:32 Slp: at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)

    at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.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)

    2010-10-06 15:00:32 Slp: Rule initialization failed - hence the rule result is assigned as Failed

    2010-10-06 15:00:32 Slp: Send result to channel : RulesEngineNotificationChannel

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • After restarting, I can get past that point, so it seems it was an issue with memory resources on the server...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Now I'm getting following error;

    can I not upgrade from SQL 2008 R2 to SQL 2008 SP2?

    There are no SQL Server instances or shared features that can be updated on this computer.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Just curious but how much memory do you have on the server? Is the server do something else other than SQL Server?

    Shawn Melton
    Twitter: @wsmelton
    Blog: wsmelton.github.com
    Github: wsmelton

  • Shawn Melton (10/6/2010)


    Just curious but how much memory do you have on the server? Is the server do something else other than SQL Server?

    48 GB.

    I know, I can't explain what happened with the memory, it's bizarre; I have nothing else running, this server is not even in production yet.

    Anyways, any thoughts on why I'm unable to upgrade from SQL 2008 R2?

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Hmm, it may not be too surprising that I cannot upgrade from SQL 2008 R2 to SQL 2008 SP2.

    SQL 2008 R2 is probably on a different version stream, so it might have its own service packs in future...

    Is it me or are there too many SQL 2008 versions being released?

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Marios Philippopoulos (10/6/2010)


    Hmm, it may not be too surprising that I cannot upgrade from SQL 2008 R2 to SQL 2008 SP2.

    SQL 2008 R2 is probably on a different version stream, so it might have its own service packs in future...

    Is it me or are there too many SQL 2008 versions being released?

    Yeah the SP1 is the only SP so far for SQL Server 2008 R2.

    I don't know that to many versions are being released, there are some cool things in R2 (not that too many people may be using them right off) that could not be implemented by just a service pack for SQL Server 2008.

    Shawn Melton
    Twitter: @wsmelton
    Blog: wsmelton.github.com
    Github: wsmelton

  • Marios Philippopoulos (10/6/2010)Is it me or are there too many SQL 2008 versions being released?

    They were 4 months shy of 2 year gap between release dates:

    SQL Server 2008 -- August 6, 2008

    SQL Server 2008 R2 -- April 21, 2010.

    Shawn Melton
    Twitter: @wsmelton
    Blog: wsmelton.github.com
    Github: wsmelton

  • For a fix you can run the following commands from an administrative command prompt. Locate this directory: %systemroot%\system32\wbem

    Run these commands in sequence & restart your setup.

    regsvr32 cluswmi.dll

    mofcomp.exe ClusWMI.mof

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply