SQL Server 2005 Cluster upgrade to SP3 with No passive nodes were successfully patched Exit Code Returned: 11009

  • Attempted to install SP3 on a SQL Server 2005 Cluster, and the attempt failed. Here is my request. I need some help finding offical microsoft documentation on testing that a SQL Cluster is talking back and forth. Can someone point me in the right direction for this type information.

    Background:

    I attempted to update a SQL cluster running SQL Server 2005 SP2. I followed all the nice pretty boxes. and when the upgrade attempt was completed the update to SQL Server engine had failed with a error.

    Exit Code Returned: 11009

    ------- Summary.txt

    Time: 06/11/2009 17:20:52.558

    KB Number: KB955706

    Machine: EGLSQLTEST1

    OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790)

    Package Language: 1033 (ENU)

    Package Platform: x86

    Package SP Level: 3

    Package Version: 4035

    Command-line parameters specified:

    Cluster Installation: Yes

    Log Location on Passive Nodes:

    (EGLSQLTEST1) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix

    (EARSQLTEST1) C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix

    **********************************************************************************

    Prerequisites Check & Status

    SQLSupport: Passed

    **********************************************************************************

    Products Detected Language Level Patch Level Platform Edition

    Setup Support Files ENU 9.3.4035 x86

    Database Services (MSSQLSERVER) ENU SP2 2005.090.3077.00 x86 ENTERPRISE

    Integration Services ENU SP3 9.00.4035.00 x86 ENTERPRISE

    SQL Server Native Client ENU 9.00.4035.00 x86

    Client Components ENU SP3 9.3.4035 x86 ENTERPRISE

    MSXML 6.0 Parser ENU 6.20.1099.0 x86

    SQLXML4 ENU 9.00.4035.00 x86

    Backward Compatibility ENU 8.05.2312 x86

    Microsoft SQL Server VSS Writer ENU 9.00.4035.00 x86

    **********************************************************************************

    Products Disqualified & Reason

    Product Reason

    **********************************************************************************

    Processes Locking Files

    Process Name Feature Type User Name PID

    msftesql Database Services Service 2708

    resrcmon.exe Database Services Application MTGA\ClusterAdmin 3452

    **********************************************************************************

    Product Installation Status

    Product : Setup Support Files

    Product Version (Previous): 4035

    Product Version (Final) :

    Status : Not Selected

    Log File :

    Error Description :

    ----------------------------------------------------------------------------------

    Product : Database Services (MSSQLSERVER)

    Product Version (Previous): 3077

    Product Version (Final) :

    Status : Failure

    Log File :

    Error Number : 11009

    Error Description : No passive nodes were successfully patched

    ----------------------------------------------------------------------------------

    Summary

    No passive nodes were successfully patched

    Exit Code Returned: 11009

    There was no hotfix.log generated..

    Just need to now how to ensure this does not happen in production at somepoint

  • Hi oscar-powell,

    I'm having the same situation in an UAT cluster configured as Active/Passive. I wanted to install SP3 last sunday and I got the same error: No passive nodes were successfully patched.

    What I do found (but didn't try it yet) was a workaround. That was to go into the Cluster Admin, go to the SQL Server resource and remove all the available servers but one, so you serve the resource with only one server (no actual cluster there...). Then, perform the update on each server. Because you don't have the instance in a cluster environment, the SP3 will not try to update the passive node. Finally, go back to the resources and set everything as you have before....

    I know this is not a good way, but perhaps this can help...

    Cheers,

    Alejandro

    Alejandro Pelc

  • The solution worked for me is removing the possible owners of other nodes and keeping only the node which to applied Service pack

    Sivaprasad S - [ SIVA ][/url]http://sivasql.blogspot.com/[/url]

  • Please refer the Article:

    http://support.microsoft.com/kb/929151

Viewing 4 posts - 1 through 3 (of 3 total)

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