Locked SQL Server 2005 Express Tools blocking installation

  • Thursday, August 04, 2011 9:34 PM
     
     

    In short, SQL Server 2005 Express Tools are blocking the installation of the Denali CTP3 on my machine.
    There is however NO SQL Server 2005 Express installed, so I'm a little confused by the error message, and frankly I don't know what to make of it.

    My issue is described in detail in this blogpost: http://t-sql.dk/?p=357

    Best regards


    HTH - please mark correct answers

All Replies

  • Saturday, August 06, 2011 3:58 AM
    Moderator
     
     

    Hi Jens, we are investigating whether this rule is needed for Denali altogether.  For a workaround to get installed, you could run setup.exe with the following skiprules value:

    /skiprules=Sql2005SsmsExpressFacet

    This will bypass that specific rule check.


    Thanks,
    Sam Lester (MSFT)

     


    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Wednesday, August 17, 2011 9:32 AM
     
     

    Hi Samuel

    I've now tried to run the installer with the specified parameter, but I'm still not getting past the rule (see blog for documentation).

    On the other hand, we've set up a new virtual machine with Denali CTP3 installed (w/out any issues), so I might not need to install locally anyhow. But the issue still persists.

    Best regards

    Jens


    HTH - please mark correct answers
  • Wednesday, September 07, 2011 2:15 PM
     
     Proposed Answer

    Hey Jens,

    So I hit the same problem today - and similarly, the suggested skiprules switch had no effect.

    I found I had a rogue key in my registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM

    I removed this, and all was good with the world once more.

    Hope this helps!

     

    • Proposed As Answer by DanielMaxwell Tuesday, October 18, 2011 10:10 AM
    •  
  • Tuesday, September 13, 2011 4:22 PM
     
     

    There is a possibility there a few SQL 2005 components might be left over, may be in registry. Retry with the installation, and under installation log folder. This would be %programfiles%\Microsoft SQL Server\110\Setup Bootstrap\Log\

    Look for the summary files, which would give the list of other SQL Server components already installed on this machine.

    I would suggest you to clean up the remains of the previous installations, you can follow : http://support.microsoft.com/kb/909967. Also try : http://blogs.msdn.com/b/astebner/archive/2005/12/08/501885.aspx

    Refer: http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/5fc58507-9f40-4213-acbd-32a57c8822d7/

    Then try with Denali CTP3 installation.

     


    Chaitanya( Twitter | Blogs )

    Any documentation bug? Tell us about it at Connect. Please feel free to add any community comments in any of the MSDN/technet articles.
    This posting is provided "AS IS" with no warranties, and confers no rights.


  • Thursday, September 22, 2011 5:39 PM
     
     

    I tried to remove via uninstall wizard but failed.

    Struggled for 3 days and finally resolved

    Removed following keys(tree)/Folders 

    • HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90
    • HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90
    • HKCU\SOFTWARE\\Microsoft\Microsoft SQL Server\90
    • C:\Program Files (x86)\Microsoft SQL Server\90\
    • C:\Program Files\Microsoft SQL Server\90\

     

    Also removed following registry paths.

    • HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\80
    • HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\80

    Regards,

    Amit Chauhan


  • Tuesday, January 24, 2012 5:47 PM
     
     

    Hey Jens,

    So I hit the same problem today - and similarly, the suggested skiprules switch had no effect.

    I found I had a rogue key in my registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM

    I removed this, and all was good with the world once more.

    Hope this helps!

     

    Appreciate this. It saved me a lot of time. @MS - Why is this installation process such a mess?