none
Error 29515 - Encryption not supported on client - wtf??

    Question

  • I have tried reinstalling the sqlncl.msi - re-booting etc without success.

    I'm on windows vista beta 2 build 5384.

    Brand spanking new machine (less that 48 hrs old) and I can't beleive my bad luck with sql express.  My xp pro machine works fine.

     

    Hers's the error:

    TITLE: Microsoft SQL Server 2005 Setup
    ------------------------------

    SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=29515&EvtType=lib%5codbc_connection.cpp%40Do_sqlScript%40OdbcConnection%3a%3aconnect%40connect%40x15

    ------------------------------
    BUTTONS:

    &Retry
    Cancel
    ------------------------------

     

    Here's the log:

    Microsoft SQL Server 2005 9.00.2047.00
    ==============================
    OS Version      : Professional  (Build 5384)
    Time            : Sat Jul 01 08:01:37 2006
     
    Machine         : JOHN-PC
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.2047.00
    Install         : Successful
    Log File        : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_SQLSupport_1.log
    --------------------------------------------------------------------------------
    Machine         : JOHN-PC
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.2047.00
    Install         : Successful
    Log File        : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_SQLNCLI_1.log
    --------------------------------------------------------------------------------
    Machine         : JOHN-PC
    Product         : Microsoft SQL Server VSS Writer
    Product Version : 9.00.2047.00
    Install         : Successful
    Log File        : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_SqlWriter_1.log
    --------------------------------------------------------------------------------
    Machine         : JOHN-PC
    Product         : SQL Server Database Services
    Error           : SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
    --------------------------------------------------------------------------------
    Machine         : JOHN-PC
    Product         : Microsoft SQL Server 2005 Express Edition
    Product Version : 9.1.2047.00
    Install         : Failed
    Log File        : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_SQL.log
    Last Action     : InstallFinalize
    Error String    : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
    Error Number    : 29515
    --------------------------------------------------------------------------------

     SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.


    Time            : Sat Jul 01 08:07:48 2006


    List of log files:
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_Core(Local).log
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_SQLSupport_1.log
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_SQLNCLI_1.log
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_SqlWriter_1.log
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_SQL.log
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_Datastore.xml
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_.NET Framework 2.0.log
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_Support.log
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_Core.log
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_SCC.log
     c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0008_JOHN-PC_WI.log
     c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

    Some relevant registry settings:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Native Client]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion]
    "PatchLevel"="9.00.2047.00"
    "Version"="9.00.2047.00"
    "SP"=dword:00000000
    "LCID"=dword:00000409

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Native Client\MSIRefCount]
    "Uninstall"="{11111111-1111-1111-1111-111111111111}"

    and

     

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap]
    "BootstrapDir"="C:\\Program Files\\Microsoft SQL Server\\90\\Setup Bootstrap\\"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCount]
    "Uninstall"="{11111111-1111-1111-1111-111111111111},{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F},{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\Setup]
    "PatchLevel"="9.1.2047"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS\MSSQLServer]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS\MSSQLServer\SuperSocketNetLib]
    "ProtocolList"=hex(7):00,00

     

    SQLSetup0001_JOHN-PC_SQLNCLI_1.log snippet (right at the end) says:

    <snipped>

    MSI (s) (AC:64) [20:59:38:014]: Product: Microsoft SQL Server Native Client -- Configuration failed.

    MSI (s) (AC:64) [20:59:38:014]: Product: Microsoft SQL Server Native Client. Version: 9.00.2047.00. Language: 1033. Configuration change completed with status: 1603.


    </snipped>

     

    and at the end of SQLSetup0001_JOHN-PC_Core(Local).log

    <snipped>

    Running: ReportChainingResults at: 2006/5/30 20:59:42
    Error: Action "ReportChainingResults" threw an exception during execution.
    One or more packages failed to install. Refer to logs for error details. : 1706
            Error Code: 0x800706aa (1706)
    Windows Error Text: The endpoint format is invalid.

      Source File Name: sqlchaining\sqlchainingactions.cpp
    Compiler Timestamp: Mon Jan 16 02:06:13 2006
         Function Name: sqls::ReportChainingResults::perform
    Source Line Number: 3245

    ---- Context -----------------------------------------------
    sqls::HostSetupPackageInstallerSynch::postCommit
    sqls::HighlyAvailablePackage::preInstall
    sqls::HighlyAvailablePackage::manageVsResources
    ce: 29539

    Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_JOHN-PC_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0001.cab" Error Code : 2
    Running: UploadDrWatsonLogAction at: 2006/5/30 21:0:8
    Message pump returning: 1706

    </snipped>

     

    Can anyone advise.  I'm willing to take a "you'll have to re-build your machine" response if I have to.  But I just need to know if this really is required.

    Thank you,

    John.

    Saturday, July 01, 2006 11:21 AM

Answers

  • With the help of a few others I've found that this error seems to be linked to missing or incorrect registry entries at HKLM\Software\Microsoft\MSSQLServer\Client\SNI9.0. There are two suggested resolutions. One is simply to uninstall everything related to SQL that might be on your computer, including:

    1. previous installation all setup files like native client, etc
    2. registry entries HKLM\Software\Microsoft\MSSQLServer
    HKLM\Software\Microsoft\Microsoft SQL Server
    HKLM\SYSTEM\CurrentControlSet\services\MSSQLSERVER
    HKLM\SYSTEM\CurrentControlSet\services\SQLSERVERAGENT

    You would then reboot and ensure that there are no remaining SQL registry entries before you continue. An alternative is to attempt to build out the SNI9.0 registry hive at the point of failure of your setup:

    When you are at the point of the failure, do not cancel the installation, create a
    .REG file with the following data (default client registry values), and import
    it:
    ***********************************************************************************
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\DB-Lib]
    "AutoAnsiToOem"="ON"
    "UseIntlSettings"="ON"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0]
    "ProtocolsSupported"=hex(7):73,00,6d,00,00,00,74,00,63,00,70,00,00,00,6e,00,70, 
    00,00,00,76,00,69,00,61,00,00,00,00,00
    "ProtocolOrder"=hex(7):73,00,6d,00,00,00,74,00,63,00,70,00,00,00,6e,00,70,00, 
    00,00,00,00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags]
    "NumberOfFlags"=dword:00000002

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags\Flag1]

    "Label"="Force protocol encryption"
    "Value"=dword:00000000

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags\Flag2]

    "Label"="Trust Server Certificate"
    "Value"=dword:00000000

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\LastConnect]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\np]
    "DLLname"="SQLNCLI"
    "NumberOfFlags"=dword:00000000
    "NumberOfProperties"=dword:00000001
    "ProtocolName"="Named Pipes"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\np\Property1]
    "Name"="Default Pipe"
    "Value"="sql\\query"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\sm]
    "DLLname"="SQLNCLI"
    "NumberOfFlags"=dword:00000000
    "NumberOfProperties"=dword:00000000
    "ProtocolName"="Shared Memory"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp]
    "DLLname"="SQLNCLI"
    "NumberOfFlags"=dword:00000000
    "NumberOfProperties"=dword:00000003
    "ProtocolName"="TCP/IP"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property1]
    "Name"="Default Port"
    "Value"=dword:00000599

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property2]
    "Name"="KEEPALIVE (in milliseconds)"
    "Value"=dword:00007530

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property3]
    "Name"="KEEPALIVEINTERVAL (in milliseconds)"
    "Value"=dword:000003e8

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\VIA]
    "DLLname"="SQLNCLI"
    "NumberOfFlags"=dword:00000000
    "NumberOfProperties"=dword:00000002
    "ProtocolName"="VIA"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\VIA\Property1]
    "Name"="Default Server Port"
    "Value"="0:1433"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\VIA\Property2]
    "Name"="Default Client NIC"
    "Value"="0"
    *******************************************************************************************

    I don't know if this will work when you are attempting a subsequent setup from an initially failed setup, but you can always fall back to the option of removing everything.

    Let me know how this works.

    Regards,

    Mike Wachal
    SQL Express team

    ----
    Mark the best posts as Answers!


    Monday, July 17, 2006 4:32 PM
    Moderator

All replies

  • Have you found a resolution to this problem?  I'm getting this error on my Windows XP SPK2 now.  Essentially all the same details.  I can't even install SQL Server 2000 on my local machine now.
    Friday, July 07, 2006 4:39 PM
  • We're looking into this error, thanks for being patient.

    Regards,

    Mike Wachal
    SQL Express team

    ----
    Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

    Saturday, July 08, 2006 2:35 AM
    Moderator
  • With the help of a few others I've found that this error seems to be linked to missing or incorrect registry entries at HKLM\Software\Microsoft\MSSQLServer\Client\SNI9.0. There are two suggested resolutions. One is simply to uninstall everything related to SQL that might be on your computer, including:

    1. previous installation all setup files like native client, etc
    2. registry entries HKLM\Software\Microsoft\MSSQLServer
    HKLM\Software\Microsoft\Microsoft SQL Server
    HKLM\SYSTEM\CurrentControlSet\services\MSSQLSERVER
    HKLM\SYSTEM\CurrentControlSet\services\SQLSERVERAGENT

    You would then reboot and ensure that there are no remaining SQL registry entries before you continue. An alternative is to attempt to build out the SNI9.0 registry hive at the point of failure of your setup:

    When you are at the point of the failure, do not cancel the installation, create a
    .REG file with the following data (default client registry values), and import
    it:
    ***********************************************************************************
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\DB-Lib]
    "AutoAnsiToOem"="ON"
    "UseIntlSettings"="ON"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0]
    "ProtocolsSupported"=hex(7):73,00,6d,00,00,00,74,00,63,00,70,00,00,00,6e,00,70, 
    00,00,00,76,00,69,00,61,00,00,00,00,00
    "ProtocolOrder"=hex(7):73,00,6d,00,00,00,74,00,63,00,70,00,00,00,6e,00,70,00, 
    00,00,00,00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags]
    "NumberOfFlags"=dword:00000002

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags\Flag1]

    "Label"="Force protocol encryption"
    "Value"=dword:00000000

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\GeneralFlags\Flag2]

    "Label"="Trust Server Certificate"
    "Value"=dword:00000000

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\LastConnect]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\np]
    "DLLname"="SQLNCLI"
    "NumberOfFlags"=dword:00000000
    "NumberOfProperties"=dword:00000001
    "ProtocolName"="Named Pipes"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\np\Property1]
    "Name"="Default Pipe"
    "Value"="sql\\query"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\sm]
    "DLLname"="SQLNCLI"
    "NumberOfFlags"=dword:00000000
    "NumberOfProperties"=dword:00000000
    "ProtocolName"="Shared Memory"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp]
    "DLLname"="SQLNCLI"
    "NumberOfFlags"=dword:00000000
    "NumberOfProperties"=dword:00000003
    "ProtocolName"="TCP/IP"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property1]
    "Name"="Default Port"
    "Value"=dword:00000599

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property2]
    "Name"="KEEPALIVE (in milliseconds)"
    "Value"=dword:00007530

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\tcp\Property3]
    "Name"="KEEPALIVEINTERVAL (in milliseconds)"
    "Value"=dword:000003e8

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\VIA]
    "DLLname"="SQLNCLI"
    "NumberOfFlags"=dword:00000000
    "NumberOfProperties"=dword:00000002
    "ProtocolName"="VIA"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\VIA\Property1]
    "Name"="Default Server Port"
    "Value"="0:1433"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SNI9.0\VIA\Property2]
    "Name"="Default Client NIC"
    "Value"="0"
    *******************************************************************************************

    I don't know if this will work when you are attempting a subsequent setup from an initially failed setup, but you can always fall back to the option of removing everything.

    Let me know how this works.

    Regards,

    Mike Wachal
    SQL Express team

    ----
    Mark the best posts as Answers!


    Monday, July 17, 2006 4:32 PM
    Moderator
  • I chose method 1, "Clean up the registry", and it worked fine.  I did not have to build out the missing registry entries at the point of failure in my setup.  I deleted the following registry entries, rebooted, then ran the installation for SQL Server 2005 again.

    1. previous installation all setup files like native client, etc
    2. registry entries HKLM\Software\Microsoft\MSSQLServer
    HKLM\Software\Microsoft\Microsoft SQL Server
    HKLM\SYSTEM\CurrentControlSet\services\MSSQLSERVER
    HKLM\SYSTEM\CurrentControlSet\services\SQLSERVERAGENT

    Thanks for your help. 

    Monday, July 17, 2006 6:52 PM
  • I chose method 2 by creating a .Reg file and merging it with the registry. I was able to do it while still having the "Retry" button up and did not have to restart the machine.

    This was on Windows XP Pro SP2.

    Thanks Mike.

    -Andrew

    Tuesday, December 19, 2006 9:39 PM
  • Hi Mike,

     

    I am using the Windows Vista Home Basic in my laptop. I am unable to install the SQL Server 2005. I have got the below error .

     

    Machine         : <your computer name>
    Product         : Microsoft SQL Server 2005
    Install         : Failed
    Log File        : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_MIKEWA-LT_SQL.log
    Last Action     : InstallFinalize
    Error String    : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}{SQL Server}Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
    Error Number    : 29515

    I have tried above steps mentioned by you. However unable to install the SQL Server 2005.

     

    Could you please help me on this regard. Thanks in advance.

     

    Cheers

    Rajanish

    Wednesday, August 08, 2007 2:23 PM
  •  Rajanish G Rao wrote:

    Hi Mike,

     

    I am using the Windows Vista Home Basic in my laptop. I am unable to install the SQL Server 2005. I have got the below error .

     

    Machine         : <your computer name>
    Product         : Microsoft SQL Server 2005
    Install         : Failed
    Log File        : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_MIKEWA-LT_SQL.log
    Last Action     : InstallFinalize
    Error String    : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}{SQL Server}Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
    Error Number    : 29515

    I have tried above steps mentioned by you. However unable to install the SQL Server 2005.

     

    Could you please help me on this regard. Thanks in advance.

     

    Cheers

    Rajanish

    Monday, July 14, 2008 8:35 AM
  • I just want to say that the 2nd option worked for me.  I chose that one because of the amount of time I've already spent and it was rather quick to cut and past the registery update and finish the install.

    Thank you.
    Monday, July 21, 2008 8:57 PM
  • Rebuilding the registry hive fixed the native client so that setup could connect to the SS service and finish the installation. For some reason, neither the setup program nor the sqlncli.msi package would rebuild the hive on its own. My problem was with the SS 2005 dev edition install, so this solution works with other editions besides SS Express.

    Thanks for posting such a detailed answer. I don't think I would have been able to fix this without it.
    Wednesday, January 28, 2009 5:55 AM
  • I too had the same problem while installing on Vista, i choose the option of copying the registry enrty and saving it in a file. Then i imported the file into the registry and clicked on retry.
    it worked ......................:-). SQL Server got installed. 
    i really saved a lot of time.
    Thanks a lot Mike Wachal

    rgds
    Shyam Sundar M.G Answer
    Wednesday, July 08, 2009 4:58 AM
  • I ran into this exact problem while attempting to install SP2 or SP3 for SQL2005 Standard Edition.

     I also chose option#2 , created a registry file, imported it in and retried the SP3 installation.

    It worked fabulous!!!!

    Thanks for providing us the outstanding support!

    Bob
    Monday, October 12, 2009 11:12 PM
  • Man you Just saved us, saved a lot of hours.
    Thanks a lot
    Monday, February 15, 2010 5:13 PM
  • Did not try solution1. My setup had failed and I had not yet dismissed the "retry" button. So solution2 worked perfectly.

    Wednesday, March 10, 2010 10:23 PM
  • Solution 2 worked for me as well.

    i imported the registry settings posted in the solution and then pressed retry

    thanks for the solution

    Friday, July 09, 2010 5:29 PM