November 22, 2011 at 7:57 am
Wonder if you guys can help. I am running a clustered environment on Windows Server 2008 R2 with the 64 Bit Edition of SQL Server 2008 Enterprise /w Service Pack 1. The cluster is installed and working fine, the fail over is working. I have done the Advanced Cluster Preperation on (Server 1) and the setup ran without any issues. However, on (Server 2), the installation bombs out after installing the Setup Support Files with no errors, it just drops you back to the Installation Centre. There was a corrupt install of SQL Server 2008 on this machine which bombed out with errors and because it wouldn't uninstall properly, I was forced to manually uninstall it. Everything is now removed and back without a trace of SQL installed. No errors are populated in the Event Log and the installation logs only show the following:
2011-11-22 14:39:52 Slp: C:\SQLServer2008_FullSP1\x64\FixSqlRegistryKey_x86.exe exit code: 0
2011-11-22 14:39:52 Slp: Completed Action: FixSqlRegistryKey, returned True
2011-11-22 14:39:52 Slp: ----------------------------------------------------------------------
2011-11-22 14:39:52 Slp: Running Action: FinalizeProgressStatus
2011-11-22 14:39:52 Slp: Completed Action: FinalizeProgressStatus, returned True
2011-11-22 14:39:52 Slp: ----------------------------------------------------------------------
2011-11-22 14:39:52 Slp: Running Action: RebootMessageAction
2011-11-22 14:39:52 Slp: Completed Action: RebootMessageAction, returned True
2011-11-22 14:39:52 Slp: ----------------------------------------------------------------------
2011-11-22 14:39:52 Slp: Running Action: Close
2011-11-22 14:39:52 Slp: Stop Action
2011-11-22 14:39:52 Slp: Completed Action: Close, returned True
2011-11-22 14:39:52 Slp: ----------------------------------------------------------------------
2011-11-22 14:39:52 Slp: Running Action: PassPidBackFromComponentUpdate
2011-11-22 14:39:52 Slp: Pass the flag CuPidDisplayed to the main setup
2011-11-22 14:39:52 Slp: PID value specified, trying to pass the value to main setup
2011-11-22 14:39:53 Slp: Completed Action: PassPidBackFromComponentUpdate, returned True
2011-11-22 14:39:53 Slp:
2011-11-22 14:39:53 Slp:
2011-11-22 14:39:53 Slp: ----------------------------------------------------------------------
2011-11-22 14:39:53 Slp:
2011-11-22 14:39:53 Slp: Setup result: 0
2011-11-22 14:38:44 Slp: Saved to directory.......C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111122_143804\SystemConfigurationCheck_Report.htm
2011-11-22 14:38:44 Slp: Sco: Attempting to create directory C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111122_143804\resources
2011-11-22 14:38:44 Slp: Sco: Attempting to create directory C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111122_143804\resources, security descriptor
2011-11-22 14:38:44 Slp: Sco: Attempting to set directory full path
2011-11-22 14:38:44 Slp: Sco: Attempting to normalize directory path C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111122_143804\resources
2011-11-22 14:38:44 Slp: Sco: Directory 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111122_143804\resources' already exists, skipping creation, moving to set security descriptor.
2011-11-22 14:38:44 Slp: Sco: Attempting to set security descriptor for directory C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111122_143804\resources, security descriptor
2011-11-22 14:38:44 Slp: Sco: Attempting to check if directory C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111122_143804\resources exists
2011-11-22 14:38:44 Slp: Sco: SDDL is NULL/empty and overwriteSecurityDescriptor is false, so nothing to do, return.
2011-11-22 14:38:44 Slp: Generating HTML report by applying XsltTransformation and saving to Log folder...
2011-11-22 14:38:44 Slp: Rules evaluation report is available now at C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111122_143804\SystemConfigurationCheck_Report.htm
2011-11-22 14:38:46 Slp: Completed Action: GatherUserSettings, returned True
2011-11-22 14:38:46 Slp: ----------------------------------------------------------------------
2011-11-22 14:38:46 Slp: Running Action: Progress
2011-11-22 14:38:46 Slp: Completed Action: Progress, returned True
2011-11-22 14:38:46 Slp: ----------------------------------------------------------------------
2011-11-22 14:38:46 Slp: Running Action: Close
2011-11-22 14:38:46 Slp: Stop Action
2011-11-22 14:38:46 Slp: Completed Action: Close, returned True
2011-11-22 14:38:47 Slp:
2011-11-22 14:38:47 Slp:
2011-11-22 14:38:47 Slp: ----------------------------------------------------------------------
2011-11-22 14:38:47 Slp:
2011-11-22 14:38:47 Slp: Setup result: 0
I have exhausted all I can investigate from both a cluster and SQL Server perspective. I have failed the cluster over so SQL is ready to install, but I think the problem lies with the after effects of the corrupt install.
Can anyone suggest anything different to look for?
Cheers.
November 22, 2011 at 8:04 am
I assume you have gone through this article.
Before Installing Failover Clustering
http://msdn.microsoft.com/en-us/library/ms189910.aspx
If No, please go through it now & try again.
If Yes, verify each of your steps with the article given below. You might have missed on something trivial.
How to: Create a New SQL Server Failover Cluster (Setup)
November 22, 2011 at 8:20 am
Thanks for the reply.
Everything has been checked and double checked, it's not the 1st time I have installed SQL in a clustered environment.
Both (Server1) and (Server2) are identical in every way. This has to be tied in some way to the failed SQL Server installation which left quite a few things behind. I have done a standard cleanup on the registry, the folders, services etc so there is no trace of SQL left on the server.
I can work my way through errors and such, but the fact it is now firing back with nothing worries me.
November 22, 2011 at 8:26 am
Everything has been checked and double checked, it's not the 1st time I have installed SQL in a clustered environment.
I would say it overconfidence. Overconfidence results in ignorance and that’s why you should crosscheck again. Anyone can commit mistake.
November 23, 2011 at 11:05 am
alik_therock (11/22/2011)
Thanks for the reply.Everything has been checked and double checked, it's not the 1st time I have installed SQL in a clustered environment.
Both (Server1) and (Server2) are identical in every way. This has to be tied in some way to the failed SQL Server installation which left quite a few things behind. I have done a standard cleanup on the registry, the folders, services etc so there is no trace of SQL left on the server.
I can work my way through errors and such, but the fact it is now firing back with nothing worries me.
have you checked the storage is presented on the 2nd node correctly
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 28, 2011 at 1:35 pm
Sounds like an issue with BitLocker.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply