locked
Error code 1603 - Update 'Service Pack 3 for SQL Server Database Services 2005 ENU (KB955706)' could not be installed RRS feed

  • Question

  •  My error is little a bit different...

    Property(S): SQL200532Hotfix4035 = c:\f89681219d2ad6c047\HotFixSQL\Files\sqlrun_sql.msp
    MSI (s) (40:AC) [12:58:47:087]: Product: Microsoft SQL Server 2005 - Update 'Service Pack 3 for SQL Server Database Services 2005 ENU (KB955706)' 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_KB955706_sqlrun_sql.msp.log.

    MSI (s) (40:AC) [12:58:47:087]: Note: 1: 1729
    MSI (s) (40:AC) [12:58:47:087]: Transforming table Error.

    MSI (s) (40:AC) [12:58:47:087]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (40:AC) [12:58:47:119]: Transforming table Error.

    MSI (s) (40:AC) [12:58:47:119]: Transforming table Error.

    MSI (s) (40:AC) [12:58:47:119]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (40:AC) [12:58:47:119]: Transforming table Error.

    MSI (s) (40:AC) [12:58:47:119]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (40:AC) [12:58:47:119]: Transforming table Error.

    MSI (s) (40:AC) [12:58:47:119]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (40:AC) [12:58:47:119]: Transforming table Error.

    MSI (s) (40:AC) [12:58:47:119]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (40:AC) [12:58:47:150]: Transforming table Error.

    MSI (s) (40:AC) [12:58:47:150]: Transforming table Error.

    MSI (s) (40:AC) [12:58:47:150]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (40:AC) [12:58:47:150]: Transforming table Error.

    MSI (s) (40:AC) [12:58:47:150]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (40:AC) [12:58:47:150]: Transforming table Error.

    MSI (s) (40:AC) [12:58:47:150]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (40:AC) [12:58:47:150]: Product: Microsoft SQL Server 2005 -- Configuration failed.

    MSI (s) (40:AC) [12:58:47:165]: Attempting to delete file c:\WINDOWS\Installer\2fce8c1d.msp
    MSI (s) (40:AC) [12:58:47:165]: Unable to delete the file. LastError = 32
    MSI (s) (40:AC) [12:58:47:212]: Cleaning up uninstalled install packages, if any exist
    MSI (s) (40:AC) [12:58:47:212]: MainEngineThread is returning 1603
    MSI (s) (40:74) [12:58:47:212]: Destroying RemoteAPI object.
    MSI (s) (40:00) [12:58:47:228]: Custom Action Manager thread ending.
    === Logging stopped: 2/15/2009  12:58:47 ===
    MSI (c) (EC:68) [12:58:47:384]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (EC:68) [12:58:47:384]: MainEngineThread is returning 1603
    === Verbose logging stopped: 2/15/2009  12:58:47 ===


    I'd found some explanation but still have no clue

    Error 2262: Not Necessarily a Fatal Error

    Someone wondered if the following found in a Windows Installer log was indeed an error:

    MSI (c) (A8:A0) [14:38:51:427]: Transforming table Error.
    MSI (c) (A8:A0) [14:38:51:427]: Note: 1: 2262 2: Error 3: -2147287038

    Recall from Diagnosing Installation Errors that field 1 in the second line indicates the Windows Installer error. If you look that up in the Windows Installer Error Messages reference documentation you'll see that error 2262 (in English) reads, "Stream does not exist: [2]. System error: [3]." If you format the message using the fields in the second log line you'll read, "Stream does not exist: Error. System error: -2147287038." Convert that error to hexadecimal for easier reference to 0x80030002.

    According to winerror.h as mentioned in Deciphering an HRESULT, 0x80030002 indicates that the error belongs to the OLE storage facility, FACILITY_STORAGE. If you look for the entire error (since it's not a Win32 error, as indicated by the FACILITY_WIN32 facility) in winerror.h - also available online - you'll find that error is defined for STG_E_FILENOTFOUND.

    Since Windows Installer files are OLE structure storage files, this system error can be expected for fatal errors when something isn't available, but the error may not always be fatal. When patching a product, for example, you'll see the second log line from above a lot - especially toward the beginning of the client and server processes. It means that a table wasn't found in the transform contained in an applicable patch. So the first log line actually refers to the Error table, not necessarily that an error occurred - just that the Error table wasn't found in a transform.

     
    • Edited by TomekC Tuesday, February 17, 2009 2:14 PM
    Tuesday, February 17, 2009 1:55 PM

All replies

  • Could you post summary.txt ?
    Prashant [MSFT] -- This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, February 17, 2009 2:02 PM
  • I'd found some explanation but still have no clue

    Diagnosing Installation Errors

    When problems occur when installing, repairing or patching, or uninstalling a product using Windows Installer technology, you need to be able to figure out what happened and why it happened. Dialogs that occur when the user interface is displayed can be helpful sometimes, but many times you need to look at a log to determine the exact cause of the problem.

    The first step in diagnosing a problem using the log is to, of course, enable logging. When performing any actions with an installation package or patch always be sure to pass /L*v filename.log on the command line. This enables verbose logging. You can also use /L*vx which outputs debugging information as well, but this isn't always helpful and can lead to much larger log file sizes than even verbose logs. This option is also only available on Windows Server 2003 and newer. You can also set logging options using the logging policy that will apply to all Windows Installer operations on the machine.

    Now that verbose logging is enabled when an error occurs you can search for "value 3" and in most cases find the return code from a failed standard or custom action. Note that this is not the only indication that a standard or custom action did not run perhaps as expected. An installation that returned prematurely but that did not return an error code from the process would have returned IDIGNORE, so you would have to search for "value 5". In Return Values of JScript and VBScript Custom Actions you can find the return values that can be returned from actions and what they indicate. Of course, it is recommended that you write custom actions in native C++ but this page does list both the #define constants and their values. Another good source of return values for custom actions is Logging of Action Return Values that lists a few more possible return values, as well as what value is returned from the custom action server depending on what values you return from your custom action.

    You should see a line like the following listing the action that returned the error value:

    Action ended 12:00:00: MyCustomAction. Return value 3.

    Now that you've located the error in the log you must determine what really happened since the return value isn't really adequate for determining the cause of the problem. If your custom action failed hopefully you've logged enough information to determine the cause right away. If you used the MsiProcessMessage function to log the error from the Error table, or a standard action failed, you will find the error number in field 1 of the log message a little above where you found "value 3":

    MSI (s) (AC:14) [12:00:00:000]: Note: 1: 1601 2: C: 3: 4096 4: 1024
    MSI (s) (AC:14) [12:00:00:000]: Product: My Product -- Out of disk space -- Volume: 'C:'; required space: 4096 KB; available space: 1024 KB

    The first line lists the error in field 1 as 1601. If you look up the error in Windows Installer Error Messages you will see Windows Installer error 1601 has the English text of "Out of disk space -- Volume: '[2]'; required space: [3] KB; available space: [4] KB". Plus the values of the fields in the first line into that message and you'll end up with the second line in the log. This will give you a much better indication of what error occurred. If the error value isn't in the Windows Installer Error Messages table, be sure to look in the Error table itself since this may be a custom error. Custom errors should be in the range from 25000 to 30000 according to the documentation for the Error table, but this isn't always the case.

    In Logging of Action Return Values return codes from msiexec.exe are paired with error codes returned from custom actions, but msiexec.exe may return other error codes as documented in Error Codes, such as ERROR_UNKNOWN_PRODUCT (1605) if you try uninstalling a product by its ProductCode that is not installed, or ERROR_PATCH_TARGET_NOT_FOUND (1642) if you try applying a patch to a product that is not installed.




    SUMARY.TXT 

    Time: 02/15/2009 13:08:45.513
    KB Number: KB955706
    Machine: KITE
    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: No

    **********************************************************************************
    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.3233.00  x86       ENTERPRISE
    Analysis Services (MSSQLSERVER)           ENU       SP3    2005.090.4035.00  x86       ENTERPRISE
    Reporting Services (MSSQLSERVER)          ENU       SP3       9.00.4035.00  x86       ENTERPRISE
    Notification Services                     ENU       SP3       9.00.4035.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
    MSSQLSERVER           Database Services     Service       NT AUTHORITY\SYSTEM        1612
    RemoteRegistry        Database Services     Service                                  1752
    SQLSERVERAGENT        Database Services     Service       NT AUTHORITY\SYSTEM        2748

    **********************************************************************************
    Product Installation Status
    Product                   : Setup Support Files
    Product Version (Previous): 4035
    Product Version (Final)   : 4035
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------
    Product                   : Database Services (MSSQLSERVER)
    Product Version (Previous): 3233
    Product Version (Final)   :
    Status                    : Failure
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
    Error Number              : 29538
    Error Description         : MSP Error: 29538  SQL Server Setup did not have the administrator permissions required to rename a file: c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
    ----------------------------------------------------------------------------------
    Product                   : Analysis Services (MSSQLSERVER)
    Product Version (Previous): 4035
    Product Version (Final)   : 4035
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB955706_sqlrun_as.msp.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------
    Product                   : Reporting Services (MSSQLSERVER)
    Product Version (Previous): 4035
    Product Version (Final)   : 4035
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\RS9_Hotfix_KB955706_sqlrun_rs.msp.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------
    Product                   : Notification Services
    Product Version (Previous): 4035
    Product Version (Final)   : 4035
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\NS9_Hotfix_KB955706_sqlrun_ns.msp.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------
    Product                   : Integration Services
    Product Version (Previous): 4035
    Product Version (Final)   : 4035
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB955706_sqlrun_dts.msp.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------
    Product                   : SQL Server Native Client
    Product Version (Previous): 4035
    Product Version (Final)   : 4035
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_sqlncli.msi.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------
    Product                   : Client Components
    Product Version (Previous): 4035
    Product Version (Final)   : 4035
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB955706_sqlrun_tools.msp.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------
    Product                   : MSXML 6.0 Parser
    Product Version (Previous): 1099
    Product Version (Final)   : 6.10.1129.0
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_msxml6.msi.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------
    Product                   : SQLXML4
    Product Version (Previous): 4035
    Product Version (Final)   : 4035
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_sqlxml4.msi.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------
    Product                   : Backward Compatibility
    Product Version (Previous): 2312
    Product Version (Final)   : 2312
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SQLServer2005_BC.msi.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------
    Product                   : Microsoft SQL Server VSS Writer
    Product Version (Previous): 4035
    Product Version (Final)   : 4035
    Status                    : Success
    Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlWriter.msi.log
    Error Number              : 0
    Error Description         :
    ----------------------------------------------------------------------------------

    **********************************************************************************
    Summary
         One or more products failed to install, see above for details
         Exit Code Returned: 29538

    Tuesday, February 17, 2009 2:35 PM
  • Ok, I see this error :

    MSP Error: 29538  SQL Server Setup did not have the administrator permissions required to rename a file: c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.

    mssqlsystemresource.ldf is a system resource file probably introduce in SP2 . It should be under the same directory where master.mdf resides.

    Could you double check :
    1.    C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ is a valid location
    2.    C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf exists
    3.    There are no unwanted files in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ means if any database has beend ropped and corresponding mdf/ldf file stioll exists , move it somewhere else.

    If master.mdf exists somewhere else, put mssqlsystemresource.ldf also in the same directory and try installation again.

    If above action doesn't help , search for "Return value 3" in SQL9_Hotfix_KB955706_sqlrun_sql.msp.log and post some 100 lines up/below from that file.


    Prashant [MSFT] -- This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, February 17, 2009 4:24 PM
  • Thank you Prashant Jha that you're trying to help me. I'm apreciate.

    1.    C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ is a valid location  - POSITIVE
    2.    C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf exists - POSITIVE
    3.         master.mdf and mssqlsystemresource.ldf are in the same place


    SQL9_Hotfix_KB955706_sqlrun_sql.msp.log

    Action ended 12:57:50: InstallFinalize. Return value 3.
    MSI (s) (40:AC) [12:57:51:151]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=978282269,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: DialogInfo(Type=0,Argument=1033)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: DialogInfo(Type=1,Argument=Microsoft SQL Server 2005)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
    MSI (s) (40:AC) [12:57:51:151]: Executing op: RegisterBackupFile(File=c:\Config.Msi\2fce8c21.rbf)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: RegisterBackupFile(File=c:\Config.Msi\2fce8c22.rbf)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: RegisterBackupFile(File=c:\Config.Msi\2fce8c23.rbf)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: RegisterBackupFile(File=c:\Config.Msi\2fce8c24.rbf)
    .
    .
    .
    .
    . i'd skipped something about a hundred lines

    MSI (s) (40:AC) [12:57:51:151]: Executing op: RegisterBackupFile(File=c:\Config.Msi\2fce8c83.rbf)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: RegisterBackupFile(File=c:\Config.Msi\2fce8c84.rbf)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: ActionStart(Name=Do_sqlFileRename.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Renaming Files,)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: ProductInfo(ProductKey={EB76B218-8FC5-41DF-9F1F-7FF3E0448383},ProductName=Microsoft SQL Server 2005,PackageName=SqlRun_SQL.msi,Language=1033,Version=151195587,Assignment=1,ObsoleteArg=0,ProductIcon=ARPIcon.ico,PackageMediaPath=\ENGLISH\SQL2005\ENTERPRISE\32BIT\Servers\Setup\,PackageCode={A6BDF070-B4CF-4DD8-A75B-727F96DDBFDC},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: ActionStart(Name=Rollback_sqlFileRename.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Renaming Files,)
    MSI (s) (40:AC) [12:57:51:151]: Executing op: CustomActionRollback(Action=Rollback_sqlFileRename.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1345,Source=BinaryData,Target=Rollback_sqlFileRename,CustomActionData=100Renaming Files200c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource1.ldfc:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.ldf0)
    MSI (s) (40:28) [12:57:51:166]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIA5.tmp, Entrypoint: Rollback_sqlFileRename
    <Func Name='LaunchFunction'>
    Function=Rollback_sqlFileRename
    <Func Name='GetCAContext'>
    <EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
    Doing Action: Rollback_sqlFileRename
    PerfTime Start: Rollback_sqlFileRename : Sun Feb 15 12:57:51 2009
    <Func Name='Rollback_sqlFileRename'>
    Rollback_sqlFileRename. Unable to rename (c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.ldf) to (c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource1.ldf).MoveFileEx returned 32
    <EndFunc Name='Rollback_sqlFileRename' Return='0' GetLastError='0'>
    PerfTime Stop: Rollback_sqlFileRename : Sun Feb 15 12:57:51 2009
    <EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
    MSI (s) (40:AC) [12:57:51:229]: Executing op: ActionStart(Name=StartServices,Description=Starting services,Template=Service: [1])
    MSI (s) (40:AC) [12:57:51:229]: Executing op: ActionStart(Name=CASetLaunchPermissions.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
    MSI (s) (40:AC) [12:57:51:229]: Executing op: ActionStart(Name=CARemoveFTEServiceDependency.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
    MSI (s) (40:AC) [12:57:51:229]: Executing op: ActionStart(Name=CAFTEInstallPerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
    MSI (s) (40:AC) [12:57:51:229]: Executing op: ActionStart(Name=CAFTEAddCertificate.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
    MSI (s) (40:AC) [12:57:51:229]: Executing op: ActionStart(Name=Do_WMISecurity.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Installing WMI registration,)
    Wednesday, February 18, 2009 4:03 PM
  • Is there any file at below location which is having Read-Only attributes ? If yes move it out to othe directory. Add current user to ..\Data directory , grant full premission and allo to inherit to child folder and files by clicking on 'Advanced' option.

    C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\
    Prashant [MSFT] -- This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, February 19, 2009 12:13 AM
  •   I'm trying to install SP3 using Domain Administrator accout, user what is log on is a member of Domain Administrator.
    There is no READ ONLY files in this directory.
    And I have still same error
    Wednesday, February 25, 2009 7:51 PM
  • I had the same problem at a customer - solved by:

    1. Making sure that permission on the Microsoft SQL Server folder contained the SQLServer2005MSSQLUser$... (it is a very long strange stupid name - anyway) - that user was missing in the permissions and I don't know why (a second SQL Server at the same customer was fine and SP3 was installed there successfully).

    2. Make sure that no other service or application is automatically starting SQL Server service(s) when they are not running. Then stop the SQL Server services and install SP3 by hand.
    Thursday, April 9, 2009 8:03 AM
  • I have same issue! I was tryed to install SP3 on my SQL2005 (sp2 + some post sp2 hotfix) with SPS2007 and i got the same error! :(
    Service Pack 3 for SQL Server Database Services 2005 ENU (KB955706)' could not be installed. Error code 1603.
    It couldn't update only database engine - all other component was upgraded fine.
    There are No "read only" files on SQL folder, full r\rw permissions (for everyone) etc. I tryed to stop all SPS2007 services and SQL service too before upgrade - no result!

    Any ideas how i can fix it?
    PS after upgrade Office Server Search don't work. Nice... :(
    Tuesday, May 5, 2009 7:17 AM
  • Help!!!

    My logs:
    ================================
    SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
    MSI (s) (5C:78) [11:52:59:789]: Transforming table Error.

    MSI (s) (5C:78) [11:52:59:789]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (5C:78) [11:52:59:804]: Transforming table Error.

    MSI (s) (5C:78) [11:52:59:820]: Transforming table Error.

    MSI (s) (5C:78) [11:52:59:820]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (5C:78) [11:52:59:820]: Transforming table Error.

    MSI (s) (5C:78) [11:52:59:820]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (5C:78) [11:52:59:820]: Transforming table Error.
    .................
    <Func Name='Do_sqlGroupMember'>
    Failure adding user NT AUTHORITY\SYSTEM to local group domain\SQLServer2005SQLAgentUser$server$MSSQLSERVER (1388)
            Error Code: 0x8007056c (1388)
    Windows Error Text: A new member could not be added to a local group because the member has the wrong account type.
    .................
    MSI (s) (5C!68) [11:55:20:678]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (5C!68) [11:55:20:678]: Transforming table Error.

    MSI (s) (5C!68) [11:55:20:678]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (5C!68) [11:55:20:678]: Product: Microsoft SQL Server 2005 -- Error 29512. SQL Server Setup was unable add user NT AUTHORITY\SYSTEM to local group domain\SQLServer2005SQLAgentUser$server$MSSQLSERVER.

    Error 29512. SQL Server Setup was unable add user NT AUTHORITY\SYSTEM to local group domain\SQLServer2005SQLAgentUser$server$MSSQLSERVER.
    <EndFunc Name='LaunchFunction' Return='1388' GetLast='0'>
    .................
    MSI (s) (5C:78) [11:56:51:834]: Product: Microsoft SQL Server 2005 - Update 'Service Pack 3 for SQL Server Database Services 2005 ENU (KB955706)' 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_KB955706_sqlrun_sql.msp.log.

    ===================================
    Hotfix.log
    05/09/2009 12:07:27.767 Registry: Cannot read registry key value "Debug", error 0
    05/09/2009 12:09:45.673 MSP Error: 29512  SQL Server Setup was unable add user NT AUTHORITY\SYSTEM to local group domain\SQLServer2005SQLAgentUser$server$MSSQLSERVER.
    05/09/2009 12:11:16.094 MSP returned 1603: A fatal error occurred during installation.
    05/09/2009 12:11:16.360 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    05/09/2009 12:11:16.391 Registry: Cannot read registry key value "Debug", error 0
    05/09/2009 12:11:16.891 Copy Engine: Error, unable to install MSP file: d:\7d8af629c7a2a7281b1558c0f8c8\HotFixSQL\Files\sqlrun_sql.msp
    05/09/2009 12:11:16.969 The following exception occurred: Unable to install Windows Installer MSP file  Date: 05/09/2009 12:11:16.969  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp  Line: 807
    ==================================


    Failure adding user NT AUTHORITY\SYSTEM to local group domain\SQLServer2005SQLAgentUser$server$MSSQLSERVER
    Hmm.. Strange error. When SQL server was installed this server was Domain controlle so there was created "domain\SQLServer2005SQLAgentUser$server$MSSQLSERVER" group in AD. Some time ago it was promoted to stand alone server and i recreated all SQL group localy on the server. But it try to use AD group anyway... not local group "server\SQLServer2005SQLAgentUser$server$MSSQLSERVER"
    • Edited by Tolot37 Saturday, May 9, 2009 8:55 AM
    Saturday, May 9, 2009 8:46 AM
  • help... :(
    Wednesday, May 13, 2009 6:53 AM
  • Hi Tolot37,

    Error 29512. SQL Server Setup was unable add user NT AUTHORITY\SYSTEM to local group domain\SQLServer2005SQLAgentUser$server$MSSQLSERVER.


    Just add this account to this group. If this group doesn't exists, just create it and add the account to it. Then re-install, you may encounter an different error.

    Be myself
    Thursday, May 14, 2009 7:09 AM
  • Hi Irene Liu,

    How i can add "NT AUTHORITY\SYSTEM" LOCAL (not domain) account in AD group? It's exist only on the stand-alone servers\pc not in AD!
    But in my error SQL try to add this account exectly in DOMAIN GROUP! (SQL server were domain controller long time ago when ms sql were installed)
    Thursday, May 14, 2009 11:28 AM
  • Any ideas? :(
    Wednesday, May 20, 2009 4:33 PM
  • This is my idea so far

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


    I'll let you know
    • Proposed as answer by Tolot37 Tuesday, May 26, 2009 5:40 PM
    Thursday, May 21, 2009 12:50 AM
  • This is my idea so far

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


    I'll let you know

    This was it for me, I backed up these keys (Just in case something went wrong) then deleted them. After that SP3 installed fine.

    Michael
    Tuesday, May 26, 2009 5:46 PM
  • This is my idea so far

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


    I'll let you know
    YES! I have done it! Thanks a lot!!!
    Tuesday, May 26, 2009 8:00 PM