Share via

problem when installing SQL 2005 “SP3 SQLServer2005SP3-KB955706-x86-ENU.exe” onto a W2003 SP2 MS cluster sharing disks on a EVA SAN

Anonymous
2010-11-02T08:40:34+00:00

1)     We are now in inconsistent state where the SP3 patch has been partially installed due to combinations of supported install method, full C: drive disk and failing every time at the stage of adding domain user to domain group. The server nodes describe that product version are very different including the database services that were roll backed successfully every time. Does this make sense ?

We think we have found a solution http://support.microsoft.com/kb/925976and need to know if such fix is your recommendation or other solution ? the failure description for error 295512 is not a perfect match.

The below chart describe the software components version. I have marked the one in red as the ones that are different and the highest.

Cluster node A:

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

Products Detected                         Language  Level  Patch Level       Platform  Edition

Setup Support Files                       ENU                     9.3.4035  x86      

Database Services (SHDB1)                 ENU       SP2   2005.090.3042.00  x86       STANDARD

Database Services (WISE)                  ENU       SP3    2005.090.4035.00  x86       STANDARD

SQL Server Native Client                  ENU                 9.00.4035.00  x86      

Client Components                         ENU       SP1           9.1.2047  x86       STANDARD

MSXML 6.0 Parser                          ENU                  6.20.2003.0  x86      

SQLXML4                                   ENU                 9.00.2047.00  x86      

Backward Compatibility                    ENU                    8.05.1704  x86      

Microsoft SQL Server VSS Writer           ENU                 9.00.2047.00  x86      

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

Cluster node B:

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

Products Detected                         Language  Level  Patch Level       Platform  Edition

Setup Support Files                       ENU                     9.3.4035  x86      

Database Services (SHDB1)                 ENU       RTM    2005.090.1399.00  x86       STANDARD

Database Services (WISE)                  ENU       SP1    2005.090.2047.00  x86       STANDARD

SQL Server Native Client                  ENU                 9.00.4035.00  x86      

Client Components                         ENU       SP3          9.3.4035  x86       STANDARD

MSXML 6.0 Parser                          ENU                  6.20.2003.0  x86      

SQLXML4                                   ENU                9.00.4035.00  x86      

Backward Compatibility                    ENU                               x86      

Backward Compatibility                    ENU                   8.05.2312  x86      

Microsoft SQL Server VSS Writer           ENU                               x86      

Microsoft SQL Server VSS Writer           ENU                9.00.4035.00  x86      

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

2)     When database packages are running on server node B: the backup is not working for one of the instances WISE. Working OK for instance SHDB1. Backup from node A: have not been tested yet.

The below error is shown in management studio when executing the job manually or looking at job definition. It could be the reason of the client components being upgraded on node B and fully completed. The backup has not been tested on A: yet since we need to shut down and move database for that. We do have a full backup of all database instances before the upgrade time that are not critical if reverting back to.

Question 2. Should solution X ? be tried before solution of the original SP3 installation problem ? As of now a new fullback cannot be done prior to new SP3 patching attempt. Can be working if moving database packages to node A running the higher client component version but “database services” version is higher there as well and could cause a new more severe problem !.

Windows for home | Other | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2010-11-02T15:07:17+00:00

    Try re-posting in the SQL Server Setup & Upgrade forum for appropriate assistance: http://social.msdn.microsoft.com/forums/en-US/sqlsetupandupgrade/threads/

    ~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft

    Was this answer helpful?

    0 comments
  2. Doug Robbins - MVP - Office Apps and Services 323.1K Reputation points MVP Volunteer Moderator
    2010-11-02T08:57:23+00:00

    This forum is for feedback on the Answers Forums, not for obtaining technical assistance.

    For the issue that you are having, you should probably post your question in the following forum:

    http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/threads

    -- Hope this helps.

    Doug Robbins - Word MVP,

    dkr[atsymbol]mvps[dot]org

    Posted via the Community Bridge

    "pere mitjavila" wrote in message news:*** Email address is removed for privacy ***...

    1)     We are now in inconsistent state where the SP3 patch has been partially installed due to combinations of supported install method, full C: drive disk and failing every time at the stage of adding domain user to domain group. The server nodes describe that product version are very different including the database services that were roll backed successfully every time. Does this make sense ?

    We think we have found a solution http://support.microsoft.com/kb/925976and need to know if such fix is your recommendation or other solution ? the failure description for error 295512 is not a perfect match.

    The below chart describe the software components version. I have marked the one in red as the ones that are different and the highest.

    Cluster node A:

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

    Products Detected                         Language  Level  Patch Level Platform  Edition

    Setup Support Files                       ENU                     9.3.4035 x86

    Database Services (SHDB1)                 ENU       SP2   2005.090.3042.00 x86       STANDARD

    Database Services (WISE)                  ENU       SP3 2005.090.4035.00  x86       STANDARD

    SQL Server Native Client                  ENU                 9.00.4035.00 x86

    Client Components                         ENU       SP1           9.1.2047 x86       STANDARD

    MSXML 6.0 Parser                          ENU                  6.20.2003.0 x86

    SQLXML4                                   ENU                 9.00.2047.00 x86

    Backward Compatibility                    ENU                    8.05.1704 x86

    Microsoft SQL Server VSS Writer           ENU                 9.00.2047.00 x86

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

    Cluster node B:

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

    Products Detected                         Language  Level  Patch Level Platform  Edition

    Setup Support Files                       ENU                     9.3.4035 x86

    Database Services (SHDB1)                 ENU       RTM 2005.090.1399.00  x86       STANDARD

    Database Services (WISE)                  ENU       SP1 2005.090.2047.00  x86       STANDARD

    SQL Server Native Client                  ENU                 9.00.4035.00 x86

    Client Components                         ENU       SP3          9.3.4035 x86       STANDARD

    MSXML 6.0 Parser                          ENU                  6.20.2003.0 x86

    SQLXML4                                   ENU                9.00.4035.00 x86

    Backward Compatibility                    ENU x86

    Backward Compatibility                    ENU                   8.05.2312 x86

    Microsoft SQL Server VSS Writer           ENU x86

    Microsoft SQL Server VSS Writer           ENU                9.00.4035.00 x86

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

    2)     When database packages are running on server node B: the backup is not working for one of the instances WISE. Working OK for instance SHDB1. Backup from node A: have not been tested yet.

    The below error is shown in management studio when executing the job manually or looking at job definition. It could be the reason of the client components being upgraded on node B and fully completed. The backup has not been tested on A: yet since we need to shut down and move database for that. We do have a full backup of all database instances before the upgrade time that are not critical if reverting back to.

    Question 2. Should solution X ? be tried before solution of the original SP3 installation problem ? As of now a new fullback cannot be done prior to new SP3 patching attempt. Can be working if moving database packages to node A running the higher client component version but “database services” version is higher there as well and could cause a new more severe problem !.

    Doug Robbins - Word MVP dkr[atsymbol]mvps[dot]org

    Was this answer helpful?

    0 comments