Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After installing the Service Pack 2 of Microsoft SQL Server 2008, the SQL Server failed to start. Trying to repair this, I've done some stupid things, which results now in the situation in which I cannot even install a fresh copy of SQL Server.

Here's actually what happens during setup:

  • Setup Support Rules screen (all passed, no warnings),
  • Product Key screen (entered a valid product key),
  • License Terms screen (accepted),
  • Setup Support Files screen (clicked Install).

Than the setup window closes, and nothing happens, no errors, nothing at all. No logs seem to be saved.

What are the steps to clean up the mess and to be able to install the SQL Server without being required to reinstall the whole OS?

share|improve this question
up vote 4 down vote accepted

I would follow this article, and then once done, I would run CCleaner.
SQL Server 2008 installation fails when you try to install SQL Server a second time

Then try to reinstall (make sure you use the same instance name).

share|improve this answer

another option - use FIX IT utility of Microsoft:

Fix problems that programs cannot be installed or uninstalled

I've removed all the Microsoft 2008 components via this utility and was able to install it correctly afterwards.

share|improve this answer
+1 for the suggestion. Still note that on Windows 8 Consumer Preview, "We're sorry, but your operating system is not supported by Microsoft Fix it at this time" message is shown. – MainMa May 21 '12 at 13:56

In addition to the answer by KCotreau to this question, for those who are experiencing the same issue, here what I did to be able to make a clean install:

  1. Tried to uninstall the old installation with setup.exe,
  2. Removed directories related to SQL Server from Program Files (including x86),
  3. Removed all references to those directories from the registry. This must be done manually: in some situations, it seems better to remove the whole parent key; in others, only the value must be removed; finally, in some situations you don't have to remove anything, since those keys/values are not intended to be used during setup,
  4. Rebooted.
  5. Setup started to work, but encountered MsiGetProductInfo failed to retrieve ProductVersion for package during install error, which can be solved either by removing the specified keys (since there are hundreds or thousands of them, be ready to spend hours), or by doing a backup of HKEY_CLASSES_ROOT\Installer\UpgradeCodes, removing the whole key, then restoring it after the clean install is made.

I would still recommend in such situation restoring the last system backup, or reinstalling Windows (both things were impossible in my specific case) if you want to do things correctly.

share|improve this answer
You mentioned restoring. My own upgrade from SQL 2005 to 2008 on my server went wrong, and I was able to get it back with no effort thanks to using Acronis Backup and Recovery imaging software. I highly recommend not just any old backup, but an imaging solution for any critical server. Glad you finally recovered. – KCotreau Jun 21 '11 at 11:01
+1: Having similar issue. Thanks for the specific list of actions on removing. Instead of deleting anything manually, I will give a try for CCleaner. My next comment will tell the results as soon as I get them. – mico Jul 14 '11 at 9:28

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .