Add Node to SQL Server failover Cluster failed with invalid SKU error - by Ayad Shammout2

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


6
0
Sign in
to vote
ID 363036 Comments
Status Closed Workarounds
Type Bug Repros 9
Opened 8/22/2008 12:21:16 PM
Access Restriction Public

Description

After creating new SQL Server failover cluster node, trying to add the 2nd node to the SQL failover cluster, after entering the product key (same key used for 1st node installation), hit next, I'm getting an error: 

SQL Server Setup encountered the following error:

The current SKU is invalid.

I was able to work around it by running setup.exe from command prompt and it bypass this issue.
Sign in to post a comment.
Posted by Matt.Shadbolt on 2/26/2009 at 9:36 PM
setup.exe /ACTION=AddNode /INSTANCENAME="MSSQLSERVER"
/SQLSVCACCOUNT="<Domain\Account>" /SQLSVCPASSWORD="<Password>"
/AGTSVCACCOUNT="<Domain/Account>", /AGTSVCPASSWORD="<Password>"
/ASSVCACCOUNT="<Account/Password>" /ASSVCPASSWORD=”<Password>” /INDICATEPROGRESS

Wroked for me :)

Matt
http://mattlog.net
Posted by Fraenkel Assaf on 1/11/2009 at 12:23 AM
http://support.microsoft.com/kb/957459/
Posted by Ayad Shammout2 on 9/24/2008 at 11:36 AM
don't use /q after setup to launch the GUI setup and walk from there. It failed when I use setup.exe /q but works without /q.
Posted by dsmith-ServiceU on 9/16/2008 at 12:50 PM
For anyone else facing this issue, see the exact Setup.exe parameters needed to add a node here:
http://msdn.microsoft.com/en-us/library/ms144259.aspx

David
Posted by IgorX on 9/9/2008 at 11:30 AM
running setup.exe has not fixed the problem in my case
Posted by Microsoft on 9/2/2008 at 3:24 PM
Ayad,

This bug should be addressed in our first Cumulative Update for bug fixes for SQL Server 2008. If calling product support about this issue please reference SQL Hotfix bug 50003415.

-Richard Waymire