November 20, 2008 at 9:18 am
I'm trying to lab up SQL Server 2008 in a 2-node Windows 2008 cluster. I've got the Windows cluster running, and I've got SQL Server running on node 1. When I go to node 2 and try to add a node from the SQL installer UI, I get an "invalid SKU" error. Googling around, it seems that this is a known issue for SQL 08 on a Windows 08 cluster on 64-bit hardware (which is, of course, precisely what I'm doing).
The proposed workaround is to run setup from the command line. No problem, I go to do that. Here's the command:
setup.exe /q /ACTION=AddNode
/SQLSVCACCOUNT="MYDOMAIN\MYSERVICEACCOUNT"
/SQLSVCPASSWORD="MYPASSWORD"
/AGTSVCACCOUNT="MYDOMAIN\MYSERVICEACCOUNT",
/AGTSVCPASSWORD="MYPASSWORD"
CRLFs added, obviously, for readability. Note that I also think the single comma is strange - but it's exactly the syntax specified in BOL. When I run this, I get:
Object reference not set to an instance of an object.
Error result: 204557340
Result facility code: 1073
Result error code: 19484
The object reference error text is far too generic to give me much luck in Googling. The error IDs aren't giving me any hits. So - has anyone here successfully added a SQL 2008 node to a Windows 2008 cluster on 64-bit hardware? How'd you do it?
I should add a couple things I've also tried. I've tried making node 2 the active node, but I can't. Windows 08 clustering only allows you to move clutered services, not resources. So I can move the MSDTC service to node 2, but I can't move the entire cluster over. I can't move the SQL Server cluster service over, because it doesn't exist yet on node 2. I tried forcing the entire thing to node 2 by shutting off node 1, to no avail. I can't get the UI far enough into the process to generate an install script to check my work against, because it fails out too early. I can't simulate it on a different machine to avoid the bug, because I don't have another cluster set up in a lab, and I can't run "add node" without an active cluster service running.
______
Twitter: @Control_Group
November 21, 2008 at 4:52 pm
I get this as well. Same setup, same error message.
November 21, 2008 at 5:56 pm
After the Cumulative Update 1 it now gives me...
2008-11-21 16:53:44 Slp: Attempting to retrieve feature element from clustered discovery. Instance Name: 'CLUSTER3WEST1', MSI Feature: 'SQL_Engine_Core_Inst', Clustered State: 'Clustered'
2008-11-21 16:53:44 ACE: Calculate for AddNode: check for instance ID, got: 'MSSQL10.CLUSTER3WEST1'
2008-11-21 16:53:45 Slp: Error: Action "FinalCalculateSettings" threw an exception during execution.
2008-11-21 16:53:45 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Failover instance 'CLUSTER3WEST1' cluster group not found. ---> System.InvalidOperationException: Failover instance 'CLUSTER3WEST1' cluster group not found.
2008-11-21 16:53:45 Slp: at Microsoft.SqlServer.Configuration.Agent.Util.GetClusterGroup(ServiceContainer ctx, String instanceName)
2008-11-21 16:53:45 Slp: at Microsoft.SqlServer.Configuration.Agent.Util.GetClusterActiveNode(ServiceContainer ctx, String instanceName)
2008-11-21 16:53:45 Slp: at Microsoft.SqlServer.Configuration.Agent.AgentConfigurationPublic.Calculate()
2008-11-21 16:53:45 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.FinalCalculateSettingsAction.ExecuteAction(String actionId)
2008-11-21 16:53:45 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2008-11-21 16:53:45 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2008-11-21 16:53:45 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2008-11-21 16:53:45 Slp: --- End of inner exception stack trace ---
2008-11-21 16:53:45 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2008-11-21 16:53:46 Slp: Received request to add the following file to Watson reporting: C:\Users\sysadmin\AppData\Local\Temp\tmpA62A.tmp
2008-11-21 16:53:47 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2008-11-21 16:53:47 Slp: Inner exceptions are being indented
2008-11-21 16:53:47 Slp:
2008-11-21 16:53:47 Slp: Exception type: System.InvalidOperationException
2008-11-21 16:53:47 Slp: Message:
2008-11-21 16:53:47 Slp: Failover instance 'CLUSTER3WEST1' cluster group not found.
2008-11-21 16:53:47 Slp: Stack:
2008-11-21 16:53:47 Slp: at Microsoft.SqlServer.Configuration.Agent.Util.GetClusterGroup(ServiceContainer ctx, String instanceName)
2008-11-21 16:53:47 Slp: at Microsoft.SqlServer.Configuration.Agent.Util.GetClusterActiveNode(ServiceContainer ctx, String instanceName)
2008-11-21 16:53:47 Slp: at Microsoft.SqlServer.Configuration.Agent.AgentConfigurationPublic.Calculate()
2008-11-21 16:53:47 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.FinalCalculateSettingsAction.ExecuteAction(String actionId)
2008-11-21 16:53:47 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2008-11-21 16:53:47 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2008-11-21 16:53:47 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2008-11-21 16:53:47 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\20081121_163851\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2008-11-21 16:53:47 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\20081121_163851\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2008-11-21 16:53:47 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081121_163851\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2008-11-21 16:53:47 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\20081121_163851\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2008-11-21 16:53:47 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\20081121_163851\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2008-11-21 16:53:47 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081121_163851\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2008-11-21 16:53:47 Slp: Sco: Unable to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081121_163851\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_, Win32 error 2
2008-11-21 16:53:48 Slp: The following exception occurred during Watson failure processing: The process cannot access the file 'C:\Users\sysadmin\AppData\Local\Temp\tmpA62A.tmp' because it is being used by another process.
2008-11-21 16:53:48 Slp:
2008-11-21 16:53:48 Slp: ----------------------------------------------------------------------
2008-11-21 16:53:48 Slp:
2008-11-21 16:53:48 Slp: Error result: 2064843076
2008-11-21 16:53:48 Slp: Result facility code: 787
2008-11-21 16:53:48 Slp: Result error code: 324
November 21, 2008 at 9:38 pm
I formatted both machines and started over. I have the whole sequence scripted...no user interaction so I know what I changed.
The only difference this time was that I slip streamed SQL 2008 Cumulative Update 1 into the install files, named the Cluster Groups in clustering the same as the instance name... and I was able to add a node!
Edit: I also changed the features from SQLENGINE, REPLICATION, FULLTEXT, SMSS, ADV_SMSS to SQLENGINE, IS, SMSS, ADV_SMSS
Good times.
November 25, 2008 at 9:20 am
Check.
I've had this on hold for a little while now due to issues in production, but I'll probably have time this week to get back to it. I'll give it a whirl with CU1 slipstreamed in. Thanks for the input. I'll post back with results...
______
Twitter: @Control_Group
April 24, 2010 at 12:48 pm
I AM getting it with Slipstream build.
How can i resolve it?
April 24, 2010 at 3:51 pm
Guys, you get the message 'Current SKU is invalid' because of the licence key.
When you get to the part of node 2 install where you see the licence key, delete the key out making a note of it first. Once you have done this click next with the blank licence key. Now click back and re type the licence key, setup will continue as usual 😎
BTW for future reference this post really belongs in the High availability section 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 17, 2010 at 8:49 am
Thanks its work for me!!
Thanks again.
September 17, 2010 at 10:44 am
this is another good reason to slipstream SP1 at install time. Cures a whole load of issues with the RTM installer!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 27, 2011 at 3:53 pm
Hi Guys
I got the same error problem but with a new instance installation.
I got 2 cluster nodes build on: server MS2008R2
And I try to install SQL 2008R2 slipstreamed with SP1
I am running the sql install by commandline:
setup.exe /IACCEPTSQLSERVERLICENSETERMS /CONFIGURATIONFILE="c:\temp\<inifile>" /SQLSVCPASSWORD="<password>" /AGTSVCPASSWORD="<password>" /SECURITYMODE=SQL /SAPWD="<sapassword>"
Test:
when i run the same command line option as in the section "I am running the sql install by commandline:"
but with two lines in the ini marked out, to follow the installation.
;QUIET="True"
;QUIETSIMPLE="False"
Then the installation succeed with no problem.
Detail file Error codes:
2011-11-27 22:53: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\20111127_225022\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2011-11-27 22:53: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\20111127_225022\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2011-11-27 22:53:38 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111127_225022\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2011-11-27 22:53: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\20111127_225022\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2011-11-27 22:53: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\20111127_225022\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2011-11-27 22:53: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\20111127_225022\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2011-11-27 22:53:38 Slp: Sco: Unable to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111127_225022\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_, Win32 error 2
2011-11-27 22:53:41 Slp: The following exception occurred during Watson failure processing: The process cannot access the file 'C:\Users\g14435a.ND60A620\AppData\Local\Temp\2\tmp3C93.tmp' because it is being used by another process.
2011-11-27 22:53:41 Slp:
2011-11-27 22:53:41 Slp: ----------------------------------------------------------------------
2011-11-27 22:53:41 Slp:
2011-11-27 22:53:41 Slp: Error result: 204557340
2011-11-27 22:53:41 Slp: Result facility code: 1073
2011-11-27 22:53:41 Slp: Result error code: 19484
Buy why do i have this error.?
/Hesselberg
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply