Friday, August 07, 2009

Can't Uninstall SQL Server 2005 Express Tools:- Error while installing Sql Server Management Studio Express 2008

The SQL Server 2005 Express Tools are installed. To continue, remove the SQL Server 2005 Express Tools.

If you are getting the above error while installing Sql Server Management Studio 2008 then probably you might try the below given solutions one by one to fix this error.

I m not certain what will work for you but i have added all the options which i found after spending some time on the net which various people have given and for me the most common one worked which also i have listed below.

  1. Rename the key “HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90”. This worked for me i renamed the whole folder to “old” and then the installation started passing all the test. For x64 Windows Server 2008, the reg key needed is: “HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90” ( Thanks to adam).

Once Sql server Management Studio is installed successfully, then restart your system sql server installation will automatically ask you for a restart.

After restarting you will see that your sql server 2005 instance will stop working because you played with the 90 directory and if you try to rename old to 90 then the system will not allow you to do so as it already created an entry name 90 for you having “Tools” and “Shell”.

So now we are in deep trouble what to do next, what i did was i again renamed the 90 entry which it created to 70 and the entry for sql server 2005 which we renamed as old, again back to 90 and voila everything works fine now.

Both sql server installations are running side by side and both management studios are also running side by side anyways we can open old database in SSMS 2008 so there is no need to have SSMS 2005 unless and until there is some special requirement.

This was the hit and trial method and it worked for me for the first time but i would not suggest this method to be done on any full fledged install although you may test this on your virtual pc or vmware installation as it might corrupt your sql server 2005 installation in some cases.

2.Try uninstalling any redgate products if you have installed any especially Red Gate Sql Prompt, this also caused issues to some users.

3.Try uninstalling sql server Management Studio 2005 before installing SSMS 2008

Above listed three ways will do the task for you, if you have resolved the problem in some other easy and concrete way then please do post your comment.

Happy Programming!!!!!!!!!!!!!!

Submit this story to DotNetKicks

del.icio.usSave Total0 users

8 comments:

Fabio Soares said...

I did exactly what you did, but I am stuck getting this error
provider failure 0x80041004
please help me!!!!!!

Aashish said...

@Fabio
Hi Fabio could you please tell me what is the system configuration you are using and what Operating System are you using and where exactly are you getting this provider error is it for Sql server 2005 or sql server 2008.
And also once please check the regedit that you have the required entries.
If the problem persists let me know, i will try my best to resolve the issue

Aashish said...

@Fabio
If you have done everything correct then you should also have a look at this link
http://support.microsoft.com/kb/893606

LYP said...

Thanks for your sharing ....
Now, I can solved my problem about that ...
and i can running Sql Server 2005 Express and Sql Server 2008 Standard together ...

Adam said...

For x64 Windows Server 2008, the reg key needed is:
HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90

The reg key in this article has no effect on x64 Windows...

I found this on another forum and thought this may help someone else fighting this issue!

Anonymous said...

Thank you very much for the "fix it" information illustrated in this post. By changing “HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90” to something other than "90" helped me to progress through the the SBS 2008 install.

Jim said...

Uninstalling SQL Server Management Studio worked for me. Thanks!

Anonymous said...

As I did not have either SQL Prompt or SQL Search installed, removing the SSMS Tools Pack add-in did the trick for me.

Post a Comment