SQL Server Performance

Problem Installing SP1 on SQL2005 64bit

Discussion in 'SQL Server 2005 General DBA Questions' started by mickjf, Mar 21, 2007.

  1. mickjf New Member

    Hi there,

    Am trying to install SP1 on SQL2005 on Win2003 in a 64 bit environment and am getting this problem:

    Microsoft SQL Server 2005 Service Pack 1 Setup
    Product: Database Services (64-bit)
    Instance: MSSQLSERVER
    Status: Failure

    I did have problems authenticating during the SP1 install which was eventually resolved by restarting the server (???) and starting again. Am not sure if that played any role...

    Have restarted the server post running of SP1 and tried it again, but am getting the same problem.

    I was wondering if anyone could suggest what to try/do to resolve this issue. I am a newbie on SQL and haven't come across this before...

    A check of the version of SQL at C:program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlservr.exe is 2005.90.1399.0 which confirms this is not SP1 - am I correct?

    Many thanks in advance...


    The full error log is posted below.

    03/22/2007 10:13:23.582 ================================================================================
    03/22/2007 10:13:23.582 Hotfix package launched
    03/22/2007 11:01:36.047 Attempting to install instance: SQL Server Native Client (64-bit)
    03/22/2007 11:01:36.047 Attempting to install target: AUSQHAWKSQL
    03/22/2007 11:01:36.047 Attempting to install file: sqlncli.msi
    03/22/2007 11:01:36.063 Attempting to install file: \AUSQHAWKSQLd$f0e170a436dc18d943HotFixSqlncliFilessqlncli.msi
    03/22/2007 11:01:36.063 Creating MSI install log file at: C:WINDOWSHotfixRedist9LogsRedist9_Hotfix_KB913090_sqlncli.msi.log
    03/22/2007 11:01:36.063 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
    03/22/2007 11:01:36.063 Failed to read registry key: Debug
    03/22/2007 11:01:49.469 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
    03/22/2007 11:01:49.485 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
    03/22/2007 11:01:49.485 Failed to read registry key: Debug
    03/22/2007 11:01:49.485 Pending reboot, successfully installed file: \AUSQHAWKSQLd$f0e170a436dc18d943HotFixSqlncliFilessqlncli.msi
    03/22/2007 11:01:49.485 Successfully installed target: AUSQHAWKSQL
    03/22/2007 11:01:49.485 Successfully installed instance: SQL Server Native Client (64-bit)
    03/22/2007 11:01:49.500
    03/22/2007 11:01:49.500 Product Status Summary:
    03/22/2007 11:01:49.500 Product: SQL Server Native Client (64-bit)
    03/22/2007 11:01:49.500 SQL Server Native Client (64-bit) (RTM )- Reboot Required
    03/22/2007 11:01:49.500
    03/22/2007 11:01:49.500 Product: Setup Support Files (64-bit)
    03/22/2007 11:01:49.500 Setup Support Files (64-bit) (RTM )- Not Applied
    03/22/2007 11:01:49.500
    03/22/2007 11:01:49.500 Product: Database Services (64-bit)
    03/22/2007 11:01:49.500 Database Services (64-bit) (RTM 1399 ENU)- Not Applied
    03/22/2007 11:01:49.500 Analysis Services (64-bit) (RTM 1399 ENU)- Not Applied
    03/22/2007 11:01:49.500 Reporting Services (64-bit) (RTM 1399 ENU)- Not Applied
    03/22/2007 11:01:49.500
    03/22/2007 11:01:49.500 Product: Notification Services (64-bit)
    03/22/2007 11:01:49.500 Notification Services (64-bit) (RTM 1399 ENU)- Not Applied
    03/22/2007 11:01:49.500
    03/22/2007 11:01:49.500 Product: Integration Services (64-bit)
    03/22/2007 11:01:49.500 Integration Services (64-bit) (RTM 1399 ENU)- Not Applied
    03/22/2007 11:01:49.500
    03/22/2007 11:01:49.500 Product: Client Components (64-bit)
    03/22/2007 11:01:49.500 Client Components (64-bit) (RTM 1399 ENU)- Not Applied
    03/22/2007 11:01:49.500
    03/22/2007 11:01:49.500 Product: MSXML 6.0 Parser (64-bit)
    03/22/2007 11:01:49.500 MSXML 6.0 Parser (64-bit) (RTM )- Not Applied
    03/22/2007 11:01:49.500
    03/22/2007 11:01:49.500 Product: SQLXML4 (64-bit)
    03/22/2007 11:01:49.500 SQLXML4 (64-bit) (RTM )- Not Applied
    03/22/2007 11:01:49.500
    03/22/2007 11:01:49.500 Product: Backward Compatibility (64-bit)
    03/22/2007 11:01:49.500 Backward Compatibility (64-bit) (RTM )- Not Applied
    03/22/2007 11:01:49.500
    03/22/2007 11:01:49.500 Product: Microsoft SQL Server VSS Writer (64-bit)
    03/22/2007 11:01:49.500 Microsoft SQL Server VSS Writer (64-bit) (RTM )- Not Applied
    03/22/2007 11:01:49.500
  2. MohammedU New Member

    Run the following to check the version/buid...post the results..

    select serverproperty('Productversion')
    select serverproperty('ProductLevel')


    MohammedU.
    Moderator
    SQL-Server-Performance.com
  3. Luis Martin Moderator

    Windows installer 1.0?.

    Can you confirm that?


    Luis Martin
    Moderator
    SQL-Server-Performance.com

    All in Love is Fair
    Stevie Wonder


    All postings are provided “AS IS” with no warranties for accuracy.



  4. mickjf New Member

    select serverproperty('Productversion')
    select serverproperty('ProductLevel')
    ====================================
    Results:
    9.00.1399.06
    RTM



    Windows Installer versions
    ==========================
    c:windowssystem32msiexec.exe 3.1.4000.1830
    c:windowssyswow64msiexec.exe 3.1.4000.1830
    Does that answer your question Luis?
  5. MohammedU New Member

    Did you try reinstalling SP1? if not try again and make sure your login has sufficienct access.

    SP2 also released, so is there any reason to use SP1? If is OK try installing SP2 instead of SP1.

    MohammedU.
    Moderator
    SQL-Server-Performance.com
  6. mickjf New Member

    Tks for the replies.

    Yes - I have tried to install it three times now (with a reboot in between) and am repeatedly getting this error in the install logs. I am using Domain Admin account.

    We have not yet approved SP2 for release within our organisation. FYI - I have installed SP1 on a number of servers today without problems - except for this one.
  7. egsj New Member

  8. MohammedU New Member


    HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL
    ServerMSSQL.2SetupResume

    Check the Resume key value and change it from 1 to
    0 and then run the setup
    If you don't find MSSQL.2 folder or resume key not exists... then the key in MSSQL.1 folder.

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL
    ServerMSSQL.1SetupResume

    Note: Please backup your registry before changing the values...

    http://www.eggheadcafe.com/aspnet_answers/SQLServersetup/Apr2006/post26622096.asp


    MohammedU.
    Moderator
    SQL-Server-Performance.com
  9. mickjf New Member

    Guys,


    Re: Modifying the Setup/Resume registry key. The registry key was already set to 0, so I can't make any changes. Checked the MSSQL.2 and .3 folders as well, but there was no Resume key there.



    Re: "Download Windows Installer CleanUp Utility..." This installer update is only for the Office product sutie. (see below)

    APPLIES TO
    • Microsoft Office Standard Edition 2003
    • Microsoft Office XP, All Editions
    • Microsoft Office 2000 Standard Edition
    • Microsoft Office Access 2003
    • Microsoft Access 2002 Standard Edition
    • Microsoft Access 2000 Standard Edition
    • Microsoft Office Excel 2003
    • Microsoft Excel 2002 Standard Edition
    • Microsoft Excel 2000 Standard Edition
    • Microsoft Office FrontPage 2003
    • Microsoft FrontPage 2002 Standard Edition
    • Microsoft FrontPage 2000 Standard Edition
    • Microsoft Office InfoPath 2003
    • Microsoft Office OneNote 2003
    • Microsoft Office Outlook 2003
    • Microsoft Outlook 2002 Standard Edition
    • Microsoft Outlook 2000 Standard Edition
    • Microsoft Office PowerPoint 2003
    • Microsoft PowerPoint 2002 Standard Edition
    • Microsoft PowerPoint 2000 Standard Edition
    • Microsoft Office Publisher 2003
    • Microsoft Publisher 2002 Standard Edition
    • Microsoft Publisher 2000 Standard Edition
    • Microsoft Office Visio Professional 2003
    • Microsoft Office Visio Standard 2003
    • Microsoft Visio 2002 Professional Edition
    • Microsoft Visio 2002 Standard Edition
    • Microsoft Visio 2000 Professional Edition
    • Microsoft Visio 2000 Standard Edition
    • Microsoft Office Word 2003
    • Microsoft Word 2002 Standard Edition
    • Microsoft Word 2000 Standard Edition
    • Microsoft Office Project Professional 2003
    • Microsoft Office Project Standard 2003
    • Microsoft Project 2002 Standard Edition
    • Microsoft Project 2000 Standard Edition
  10. mickjf New Member

    I have identified another log file which might provide further clues. I have trimmed it as the errors just repeat themselves on a per file basis.

    At one point in the log file it says that the user cancels installation. This is not true. I let it run through to completion.

    Any other ideas anyone?


    03/26/2007 11:35:15.471 ================================================================================
    03/26/2007 11:35:15.471 Hotfix package launched
    03/26/2007 11:35:16.502 Product discovery successfully completed during the install process for MSSQLSERVER
    03/26/2007 11:35:16.502 SP Level check successfully completed during the install process for MSSQLSERVER
    03/26/2007 11:35:16.502 Product language check successfully completed during the install process for MSSQLSERVER
    03/26/2007 11:35:16.502 Product version check successfully completed during the install process for MSSQLSERVER
    03/26/2007 11:35:16.502 Command-line instance name check completed during the install process
    03/26/2007 11:35:16.502 Baseline build check completed during the install process
    03/26/2007 11:35:32.565 Attempting to install instance: MSSQLSERVER
    03/26/2007 11:35:32.611 Attempting to install target: AUSQHAWKSQL
    03/26/2007 11:35:32.611 Attempting to stop service: MSSQLServer
    03/26/2007 11:35:34.611 Successfully stopped service: MSSQLServer
    03/26/2007 11:35:34.611 Attempting to check for locked files: sqlrun_sql.msp
    03/26/2007 11:35:34.627 Attempting to check for locked files: \AUSQHAWKSQLC$ mpSQLx64Sp1HotFixSQLFilessqlrun_sql.msp
    03/26/2007 11:35:34.627 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out
    03/26/2007 11:35:42.924 MSP returned 1602: The user cancels installation.
    03/26/2007 11:35:42.939 Successfully checked file: \AUSQHAWKSQLC$ mpSQLx64Sp1HotFixSQLFilessqlrun_sql.msp
    03/26/2007 11:35:42.939 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
    03/26/2007 11:35:42.939 Failed to read registry key: PendingFileRenameOperations
    03/26/2007 11:35:42.939 Failed to read associated hotfix build information for the following file: C:program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll
    03/26/2007 11:35:42.955 Failed to read associated hotfix build information for the following file: C:program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll
    03/26/2007 11:35:42.955 Failed to read associated hotfix build information for the following file: C:program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll
  11. MohammedU New Member

  12. mickjf New Member

    There is over 20GB of free disk space on C drive where SQL is installed and more than 20GB on all other partitions as well. There is no mention of disk space in any of the errors I receive.
  13. MohammedU New Member

  14. mickjf New Member

    This has been resolved (finally!!!)<br /><br />The error was shown in "SQL9_Hotfix_KB913090_sqlrun_sql.msp.log" file:<br /><br />MSI (s) (A0!7<img src='/community/emoticons/emotion-11.gif' alt='8)' /> [11:32:50:959]: Product: Microsoft SQL Server 2005 (64-bit) -- Error 29506. SQL Server Setup failed to modify security permissions on file C:program FilesMicrosoft SQL ServerMSSQL.1MSSQLData for user au-cs-power. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.<br /><br />Once I granted my account full control access to all database files in that folder, it worked like a charm. <br /><br />Many many thanks for your help (especially MohammedU) in pointing me in the right direction to get this one resolved!!<br /><br />Mick

Share This Page