SQL 2008 and The Setup Failed to Read IIsMimeMap Table
1/6/2009 1:27:40 PM
Decided to install SQL 2008 recently because of it being 2009 and all. What an adventure. Although not near as bad as upgrading from Vista Home Premium to Vista Ultimate, it sucked pretty bad.
I downloaded the 120-day trial Developer Edition as a self-extracting executable because I didn't feel like burning a DVD / using Daemon Toolz. The download was the smoothest part of this whole deal.
From the installer screen I chose the Upgrade from SQL 2000 / 2005 option because I have SQL 2005 Developer Edition installed so this made the most sense. Miserable fail. I kept erroring out when trying to install SQL Reporting Services. The exact error(s) escape me but I remember it having something to do with authentication and the report service. Naturally I thought to manually stop and start the service to see if there was any issue. Good thing because manually starting the service failed. It then dawned on me that between the time I had initially installed SQL 2005 and that very instant I had changed my Windows password. Right-click, 'Properties' and changed it to my current password, restart the service: SUCCESS!
Now let's try upgrading again: FAIL!
After hitting the Google fairly hard I read a couple of blog entries detailing how uninstalling SQL Server 2005 entirely from the Control Panel would remedy the situation. I tried this and received the following error when attempting to uninstall SQL 2005 Reporting Services:

Awesome. Have no idea what this means so I searched Google for it. Apparently no one else does either. There were tons of suggestions as to how to go about remedy'ing this so I tried a couple. These solutions ranged from reconfiguring Reporting Services to uninstalling and reinstalling IIS7. I opted to try and reconfigure Reporting Services only to find that the configuration tools no longer existed on my machine seeing as how that was successfully uninstalled before receiving the error message above. I then tried to uninstall again and received this error message.
Same error, different error code. Weird.
The final solution was to install each component of SQL 2005 one-by-one from Control Panel. As crazy as that sounds it actually ended up being successful.
So, if you are getting these error messages try uninstalling each and every SQL 2005 component one-by-one and then do a clean install of SQL 2008. It worked for me.
SQL
