none
Upgrading x64 SQL 2005 SP4 from 9.0.5292 to 9.0.5324 fails - why?

    Question

  • I've tried installing Security Update for SQL Server 2005 Service Pack 4 (KB2716427) to our SQL Server 2005 Server which is currently runing 9.0.5292, but it fails.

    It manages to install the Integration Services and Tools, but Database services fails to install with this message:

    Product Installation Status
    Product                   : SQL Server Database Services 2005 (MSSQLSERVER)
    Product Version (Previous): 5292
    Product Version (Final)   :
    Status                    : Failure
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2716427_sqlrun_sql.msp.log
    Error Number              : 11032
    Error Description         : Unable to install Windows Installer MSP file

    Looking in HotFix.Log I can see:

    03/05/2013 12:05:06.018 Copy Engine: Error, unable to install MSP file: f:\f728e69179bd8bda133a04855b7de1cf\HotFixSQL\Files\sqlrun_sql.msp
    03/05/2013 12:05:06.080 The following exception occurred: Unable to install Windows Installer MSP file  Date: 03/05/2013 12:05:06.080  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp  Line: 807

    And then in the actual sql.msp.log file itself:

    MSI (s) (0C:88) [12:05:05:488]: Product: Microsoft SQL Server 2005 (64-bit) - Update 'Hotfix 5324 for SQL Server Database Services 2005 (64-bit) ENU (KB2716427)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2716427_sqlrun_sql.msp.log.

    MSI (s) (0C:88) [12:05:05:488]: Windows Installer installed an update. Product Name: Microsoft SQL Server 2005 (64-bit). Product Version: 9.4.5000.00. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: Hotfix 5324 for SQL Server Database Services 2005 (64-bit) ENU (KB2716427). Installation success or error status: 1603.

    MSI (s) (0C:88) [12:05:05:519]: Note: 1: 1729
    MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:534]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:534]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:534]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:534]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

    MSI (s) (0C:88) [12:05:05:534]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (0C:88) [12:05:05:534]: Product: Microsoft SQL Server 2005 (64-bit) -- Configuration failed

    I can't see any other relevant error messages - I have a 7MB Log file but it's not at all clear what is causing the error. Any ideas?


    Tuesday, March 05, 2013 2:28 PM

All replies

  • Thanks, but: Had seen the first link already (already done some serious Googling), it refers to a missing FTData folder which my log file makes no mention of.

    The second refers to Windows Installer 3.0 - our server is currently on version 5.0.

    Tuesday, March 05, 2013 3:14 PM

  • Status                    : Failure
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2716427_sqlrun_sql.msp.log
    Error Number              : 11032
    Error Description         : Unable to install Windows Installer MSP file


    Hi Gareth Spring,

    This problem occurs because the Ftdata folder does not exist when you install a SQL Server 2005 service pack. For example, you may have manually deleted the folder before the installation. By default, the Ftdata folder is located in the following folder:

    SQLServerInstallPath\Microsoft SQL Server\MSSQL.X\MSSQL\FTDATA\

    Could you see this folder?

    To resolve this problem, create the Ftdata folder if the folder does not exist. Then, reinstall the SQL Server 2005 service pack.

    For more information, please refer to:
    The SQL Server 2005 service pack installation stops unexpectedly, and the following error message is logged in the setup log file: "Unable to install Windows Installer MSP file": http://support.microsoft.com/kb/926622?wa=wsignin1.0.

    If you have any feedback on our support, please click here.

    Thanks.


    Maggie Luo
    TechNet Community Support

    Wednesday, March 06, 2013 6:58 AM
    Moderator
  • No, the FTdata folder is not there. I will create and retry the install (easier said than done given our uptime obligations)

    Thanks.

    Wednesday, March 06, 2013 12:24 PM
  • Can you try repairing installed instance before applying the patch ?

    FAQ
    ----
    Regards,
    Ahmed Ibrahim
    SQL Server Setup Team
    My Blog
    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you.
    This can be beneficial to other community members reading the thread.
    View Ahmed Ibrahim's profile on LinkedIn

    Thursday, March 07, 2013 12:04 AM
    Moderator
  • Hi Gareth,

    I’m writing to follow up with you on this post. Was the problem resolved?

    If you are satisfied with our solution, I’d like to mark this issue as "Answered". Please also feel free to unmark the issue, with any new findings or concerns you may have.  

    Thanks.


    Maggie Luo
    TechNet Community Support

    Thursday, March 14, 2013 8:44 AM
    Moderator
  • I have not been permitted to take the server down for patching yet, as I said - we have uptime obligations.

    When I have tried the solution you suggested I will mark as the answer if it works. Will know within the next 10 days I hope.

    Thanks.


    Thursday, March 14, 2013 3:21 PM
  • So, I will be trying this on Saturday.
    Thursday, March 21, 2013 2:21 PM
  • Hi Gareth,

    Any progress?

    Thanks.


    Maggie Luo
    TechNet Community Support

    Sunday, March 24, 2013 4:11 PM
    Moderator
  • Unfortunately, it's been put back a week. As soon as I can confirm either way I'll provide you with an update.

    Thanks,

    Gareth

    Monday, March 25, 2013 11:27 AM