Quantcast
Channel: SQL Server Setup & Upgrade forum
Viewing all articles
Browse latest Browse all 7696

Windows 2016 Server Core - Add node to a SQL Server Failover Cluster

$
0
0

Hello, All.

OK, 2016 Server CORE.
have already Added the Server node to our Failover Cluster Manager.
The next step, is to Add the node to the SQL Server Failover cluster installation.

I found this page, Install SQL Server NODE from the Command Prompt which is helpful. However, I am not able to complete the installation without error.
This is code I wrote, with the help of the link above.

.\Setup.exe /QS /Action=AddNode /IACCEPTSQLSERVERLICENSETERMS=true          
/INSTANCENAME=SQLInstanceNameHere /FAILOVERCLUSTERNETWORKNAME=ClusterNameHere  
/FAILOVERCLUSTERIPADDRESSES=192.168.2.36 /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"  
/CONFIRMIPDEPENDENCYCHANGE=0 /AGTSVCACCOUNT=DomainNameHere.local\sqlagent  
/AGTSVCPASSWORD=******* /SQLSVCACCOUNT=*******




This is the error I receive when it is "Running Rules for Feature Installation"

The following error occurred: 

You have selected a feature that is not supported for Windows Server Core. 
The supported features on Windows Server Core are: Database Engine Services, 
SQL Server Replication, Full-Text and Semantix Extractions for Search, Analysis Services, 
Client Tools Connectivity, Integration Services, and SQL Client Connectivity SDK.

Error result: -2067922334
Result facility code: 1214
Result error code: 61

I found this on the error above. However, it is for 2012, not 2019
You cannot install a SQL Server 2012 Cluster Instance

I went through the installation process on a test server, to see what Features it picks up on, during the installation. And on the 
Cluster Node Configuration - Page.
Features = SQLEngine, SQLEngine\Replication,SQLEngine\FullText, SQLEngine\DQ

Any assistance on installing/Adding node to a Failover cluster.
Please let me know.

Wayne




Viewing all articles
Browse latest Browse all 7696

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>