If the SQL Server install fails... and the uninstall as well

DZone 's Guide to

If the SQL Server install fails... and the uninstall as well

· Database Zone ·
Free Resource

Yesterday I decided to install Micosoft SQL Server 2008 R2. The regular precedure included downloading the ISO image from MSDN and installing directly from it. It is the Standard version and I previopusly had no problems with it, therefore I expected the same smooth installation experience to happen this time as well. But it wasn't the case.

The problem started when an error message popped up and told me that there is an error installing a 64-bit component. Fine, let's say that at this moment I don't need this component - after all I can do a repair when the server is completely installed. Once I clicked on Continue, the installer crashed.

No big deal, I just had to uninstall the package and install it again - maybe there was an unexpected glitch. But there was a problem - I couldn't uninstall any SQL Server 2008 R2 components because of an error connected to setup.rll. This library is included in the installation package in resources/1033 and is also copied locally to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\Resources\1033. So let's start the setup again then - the same error is still there.

To my surprise, when I opened the local folder where the file should be located, I saw this:

The file size is 0 bytes - no wonder there is an error accessing its contents. All you have to do is copy the file from the installation package and replace the zero-sized instance.

Soon enough I found that there is an actual error with the installation package reported on the Microsoft Connect website. I ended up downloading the Express edition for now and the Developer edition is now downloading. Some people mentioned that the setup goes right from actual physical media (DVD). Since I don't receive MSDN content on DVDs, I am not able to test it for now and my final recommendation would be:

Download either the Developer edition or try working with Express - a fix should be available later on.

PS: Tested on a Windows 7 64-bit system.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}