asked on

SQL 2008 R2 Cluster instance will not install

So I am trying to install SQL 2008 R2 to a fail over cluster. My cluster is already configured and looks good. I start the SQL setup and proceed through the initial checks, I agree to the license terms and enter my kicense key and everything continues to look good.

The inital setup finishes and the Setup support Rules dialog comes up. I click install and all the checks come back sucessful. I click next and .... nothing. The dialog closes and nothing else happens.

Star Gazr1

I haven't setup this instance of SQL Server but is there a log file you can check for errors?
I think on SQL Server 2008 it would be:
%programfiles%\Microsoft SQL Server\100\Setup Bootstrap\Log
I posted a link (sorry couldn't offer more specifics at this stage)
http://support.microsoft.com/kb/955396

sobergfell

ASKER

I check those logs and I could not find anything that would indicate an error. I have attached them here.

Also, as a test, i tried to install a stand-alone instance of SQL, removing the Cluster as a factor, and got the same results.
20130507-181033.zip

SOLUTION

Star Gazr1

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sobergfell

ASKER

So i went throught the painful process of purging the registry of everything related to SQL. I have been able to progress to the next step, but now I get the following error:

TITLE: SQL Server Setup failure.
------------------------------

SQL Server Setup has encountered the following error:

Attempted to read or write protected memory. This is often an indication that other memory is corrupt..

------------------------------

When I look in the detailed log I see this:

2013-05-09 13:23:36 Slp: Parameter 5 : Install_SqlWriter

2013-05-09 13:23:38 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130509_131135\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2013-05-09 13:23:38 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130509_131135\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2013-05-09 13:23:38 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130509_131135\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2013-05-09 13:23:38 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130509_131135\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2013-05-09 13:23:38 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130509_131135\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2013-05-09 13:23:38 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130509_131135\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2013-05-09 13:23:42 Slp: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
2013-05-09 13:23:42 Slp: Watson bucket for exception based failure has been created
2013-05-09 13:23:42 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2013-05-09 13:23:42 Slp: Sco: Attempting to open registry subkey
2013-05-09 13:23:42 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2013-05-09 13:23:42 Slp: Sco: Attempting to get registry value DW0201
2013-05-09 13:23:45 Slp: Submitted 1 of 1 failures to the Watson data repository
2013-05-09 13:23:45 Slp:
2013-05-09 13:23:45 Slp: ----------------------------------------------------------------------
2013-05-09 13:23:45 Slp:
2013-05-09 13:23:45 Slp: Error result: 1525394837
2013-05-09 13:23:45 Slp: Result facility code: 747
2013-05-09 13:23:45 Slp: Result error code: 44437

Anyone got any ideas?

ASKER CERTIFIED SOLUTION

Star Gazr1

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sobergfell

ASKER

Ended up having to delete any reference to SQL in the registrty and run the Windows MSI clean-up tool.

Star Gazr1

thanks for the points even though you figured it out yourself. I know it can be real headache having to deal with issues like this -- but for me I find it good practice and learning to struggle through it.