April 11, 2012 at 9:26 am
Doing 2 installations of SQL Server 2008 Failover cluster. The hung halfway through the first node. The second succeeded on the first node, and is hung halfway through the second node. Both are hung in the exact same place- from detail.txt:
2012-04-11 08:44:24 Slp: ----------------------------------------------------------------------
2012-04-11 08:44:24 Slp: Running Action: SQL_DTS_VSTAConfiguration_install_Cpu64
2012-04-11 08:44:24 Slp: Action Data:
2012-04-11 08:44:24 Slp: Feature = SQL_DTS_Full_sql_is_Cpu64
2012-04-11 08:44:24 Slp: Scenario = install
2012-04-11 08:44:24 Slp: Timing = ConfigNonRC
2012-04-11 08:44:24 Slp: ConfigObjectType = Microsoft.SqlServer.Configuration.SSIS.VSTAConfigurationPrivate
2012-04-11 08:44:24 Slp: FeatureName = SQL_DTS_Full
2012-04-11 08:44:24 Slp: FeatureCpuType = Cpu64
2012-04-11 08:44:24 Slp: FeaturePackageId = sql_is
2012-04-11 08:44:24 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2012-04-11 08:44:24 Slp: Sco: Attempting to open registry subkey
2012-04-11 08:44:24 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5
2012-04-11 08:44:24 Slp: Sco: Attempting to get registry value InstallPath
2012-04-11 08:44:24 SSIS: Running: C:\WINDOWS\Microsoft.NET\Framework\v3.5\AddInUtil.exe -PipelineRoot:"C:\Program Files (x86)\Common Files\microsoft shared\VSTA\Pipeline" -Rebuild
2012-04-11 08:44:25 SSIS: Application succeded: C:\WINDOWS\Microsoft.NET\Framework\v3.5\AddInUtil.exe -PipelineRoot:"C:\Program Files (x86)\Common Files\microsoft shared\VSTA\Pipeline" -Rebuild
2012-04-11 08:44:25 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2012-04-11 08:44:25 Slp: Sco: Attempting to open registry subkey
2012-04-11 08:44:25 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VSTA\9.0
2012-04-11 08:44:25 Slp: Sco: Attempting to get registry value InstallDir
2012-04-11 08:44:25 SSIS: Running: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\vsta.exe /hostid SSIS_ScriptTask /setup
Been this way for several hours- it's not going to go anywhere. I'm waiting for a call back from MS but wondered if anyone has seen this before. I dont want to kill the setup obviously if there is any way to get it to resume or even "cancel" gracefully since I know the cleanup is not an easy task.
anyone seen this or anythign like it during an install?
April 11, 2012 at 12:17 pm
This turned out to be an issue with setup running on systems with > 32 processors. Described here: http://support.microsoft.com/kb/2251397
Resolutino was to kill setup, remove nodes, and run setup again this time specifying one processor affinity by launching setup from the command line with:
Start /affinity ffff setup.exe
April 11, 2012 at 12:29 pm
How many CPU Does your node have?
April 11, 2012 at 12:37 pm
40
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply