SQL 2012 Cluster "AddNode" on Win8 Error: The following error occurred: Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$
Wednesday, April 11, 2012 9:36 AM
With regards to MS SQL 2012 and Clustering on Win8 (8250). I can successfully create a two node Win8 server cluster and in one of the nodes I can perform a cluster install of SQL 2012 Ent, this install completes ok. When I try and perform an AddNode on a second server in the Win8 Cluster I receive the following error message. The same error is generated via the Wizard and via command line install. The error in the wizard is generated on the page where it should show the service account details.
The error message is:
The following error occurred: Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$DPM$; Error result: -2061828095 Result facility code: 1307 Result error code: 1 Please review the summary.txt log for further details Microsoft (R) SQL Server 2012 11.00.2100.60
I have tried installing the primary SQL server with and without the Full_Text option in the FEATURES switch, and yet I still receive this error. Although even if I do specify the Full_Text option this switch seems to be ignored when in cluster mode.
The Database path is a SMB 2 Share on a HA File server.
I have also specified the FTSVCACCOUNT and FTSVCPASSWORD, as I think the problem is that there is a setup rule that tries to obtain the Account details for the Full Text engine, even though it is not installed on initial SQL Cluster server.
The command line I use for installing the first SQL instance is:
/ACTION="InstallFailoverCluster" /IAcceptSQLServerLicenseTerms /INSTANCENAME="DPM$" /INSTANCEID="DPM$" /ENU="True" /QUIET="TRUE" /UpdateEnabled="True" /UpdateSource="MU" /HELP="False" /INDICATEPROGRESS="False" /X86="False" /SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS" /FEATURES=SQLENGINE,REPLICATION,RS,BC,BIDS,Conn,ADV_SSMS /SQLSVCACCOUNT="Dev\ServiceSPSQLF01Servi" /SQLSVCPASSWORD="APassword1234" /SQLSYSADMINACCOUNTS="Dev\Administrator" /FTSVCACCOUNT="Dev\ServiceSPSQLF01Servi" /FTSVCPASSWORD="APassword1234" /AGTSVCACCOUNT="Dev\ServiceSPSQLF01Agent" /AGTSVCPASSWORD="APassword1234" /INSTALLSHAREDDIR="D:\Program Files\Microsoft SQL Server" /INSTALLSHAREDWOWDIR="D:\Program Files (x86)\Microsoft SQL Server" /INSTANCEDIR="D:\Program Files\Microsoft SQL Server\DPM$" /INSTALLSQLDATADIR=\\sdc001\SQL$\DPM\Farm01\CDPMSQL001SQL /SQMREPORTING="False" /FAILOVERCLUSTERGROUP="SQL Server (DPM$)" /FAILOVERCLUSTERIPADDRESSES="IPv4;220.127.116.11;Cluster Network 1;255.255.0.0" /FAILOVERCLUSTERNETWORKNAME="CDPMSQL001SQL" /COMMFABRICPORT="0" /COMMFABRICNETWORKLEVEL="0" /COMMFABRICENCRYPTION="0" /MATRIXCMBRICKCOMMPORT="0" /SkipRules=Cluster_VerifyForErrors
The command line for the AddNode is:
/ACTION="AddNode" /IAcceptSQLServerLicenseTerms /ENU="True" /QUIET="TRUE" /INSTANCENAME="DPM$" /SQLSVCACCOUNT="DEV\ServiceSPSQLF01Servi" /SQLSVCPASSWORD="APassword1234" /AGTSVCACCOUNT="DEV\ServiceSPSQLF01Agent" /AGTSVCPASSWORD="APassword1234" /FTSVCACCOUNT="DEV\ServiceSPSQLF01Servi" /FTSVCPASSWORD="APassword1234"
Any help of pointers would be great.
Thursday, April 12, 2012 1:32 PMAnswerer
While I don't have a solution, I actually had this same issue happen to me. I opened a case with MS but the end result was that they weren't sure what went wrong and it wasn't taking the correct code path. In order to get this to work I had to use the advanced prep/completion options. I do want to point out that my issue was with SQL Server 2008 R2/Windows Server 2008 R2.
If you find out any more detail on the issue please reply to the thread!
Thursday, January 03, 2013 1:09 AM
I know this has been a while since you posted this, but did you ever find a solution for this? I am having the same issue when trying to install a second instance for PowerPivot (the first instance of SQL/AS installed without any issues). For this second instance, Node1 installed without issue, but when I try to add Node2, I get the error when going to the service account details page.SQL Server Setup has encountered the following error:
Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$POWERPIVOT
Error code 0x851B0001.
Even though it was Windows/SQL 2008 R2, you mentioned that you got around this issue by using the advanced prep/completion options... Would you be able to offer any additional details or steps? I've never done the advanced prepare or advanced completion options from the SQL install.
Thanks in advance for your help!
Thursday, January 03, 2013 6:06 AM
Have you verified your cluster validation test results.
Let me know if you are successful in your test?
Thursday, January 03, 2013 1:58 PM
This is actually a second instance of SQL/AS that I'm trying to install. The first (default) instance installed on both nodes without any issues at all.
I'm trying to install PowerPivot on a pre-existing cluster, as a named instance. The first node installed without issue, but I am getting the above error when trying to go through the wizard to add the 2nd node.
If I run the cluster validation wizard now, I will get errors because not all of the resources are owned by both nodes. This will definitely stay that way until I get the 2nd node added.
Friday, January 04, 2013 11:09 AM
The issue I had has been identified as a bug in SQL Setup. The logic to handle instance name with a “$” is not correct, and the installation on the first node didn’t succeed for FullText service! The install completed successfully once we used an instance name without a '$' in it. Although (and this is just my two cents) we have since moved away from SQL Clustering and instead use the SQL Always-On feature, requires twice the shortage but I find it less fiddly, still requires Windows Cluster Services but only for handling the VIP end point.
Sunday, January 06, 2013 5:26 PMAnswerer
Wednesday, January 09, 2013 11:18 AM
Antony, Windows Clustering actually used for slightly more than the "VIP end point" -which I presume you mean Listener (which is an optional component of AlwaysOn AGs anyway). In actual fact WFC is used for 2 main reasons:
- To provide a Quorum mechanism
- To provide an HA backbone for the Availability Group Resource (and optional Listener).
Whilst much easier to setup and validate than when installing SQL FCI, it still has many similar considerations and introduces its own share of them :)
Regards,Contact me through (twitter|blog|SQLCloud)
Please click "Propose As Answer" if a post solves your problem
or "Vote As Helpful" if a post has been useful to you
Watch my sessions at the PASS Summit 2012
Friday, March 08, 2013 8:55 AM
We had exact same scenario (SQL 2012 Power Pivot Named SQL Instance AddNode failed after installing SQL 2012 Default instance) and managed to resolve this, for the benefit of everyone here are the steps to fix this.
For reference the Named SQL instance (SQL 2012) that I am using is POWERPIVOT, and on a 2-node cluster, let's call it Node A (active) and node B (passive)
1. What happened is that in the first place the MSSQLFDLauncher$POWERPIVOT reg entry was already failed when you setup your named Power Pivot SQL instance on Node A (keep this in mind), but somehow the setup of the named sql instance will not tell you that it had failed to setup the 'SQL Full-text Filter Daemon Launcher (POWERPIVOT)' service (you can check this to prove it)
2. So when you try to do 'AddNode' from the setup it searched for MSSQLFDLauncher$POWERPIVOT in the Node A and failed, when this happened the setup will simply abort stating Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$POWERPIVOT
3. OK, that explains what happened, it looks like a bug to me for Microsoft to fix
1. The fix is to trick the 'AddNode' installer into beleving that MSSQLFDLauncher$POWERPIVOT has been successfully installed on the Node A.
2. To do this, on the Node A, stop the 'SQL Full-text Filter Daemon Launcher (MSSQLSERVER)' service (this represents the successful setup on your default instance)
3. Rename the following registry key (or folder) from MSSQLFDLauncher (this represents the successful setup on your default instance) to MSSQLFDLauncher$POWERPIVOT
Resulting Registry is HKEY_CURRENT_USER\System\CurrentControlSet\Services\MSSQLFDLauncher$POWERPIVOT
4. Run 'AddNode' setup from Node B and this time it should be Successful(!!!)
5. Once done, patch the named sql instance on the Node B as required (e.g. SQL 2012 SP1 and CUs)
6. Ok, everything's good now (I can imagine you are smiling at this stage), but don;t forget to change back the reg entry on Node A (Rename MSSQLFDLauncher$POWERPIVOT back to MSSQLFDLauncher and start 'SQL Full-text Filter Daemon Launcher (MSSQLSERVER)' service
All Good =)
- Edited by Alexanwah Friday, March 08, 2013 8:56 AM typo
Thursday, April 25, 2013 1:36 PM
I too have been having this issue with a 2012 SQL cluster. I followed you steps above although, once I get to the Service Accounts step in the process I get an error that The credentials you provided for the Full-text service are invalid.
The Account Name and Password fields are not editable...