SQL Server Failover Cluster – Problem Adding a New Node to a SQL Server 2012 Failover Cluster

clusteringfailoversql serversql-server-2012

  • I tried to add a new node to SQL Server (2012 Standard) Failover, that is already installed on another node in Windows2012 Failover Cluster
  • I have an issue with non editable field wiht input for SQL Server Agents Account Name
  • there could be the same AD name as for SQL Server Database Engine (e.i.)
  • my account access haven't AD admin privileges
  • access, account and setting for SQL Server Agent on parent node are accesible and settable

enter image description here

Best Answer

As per your comments in your question, what you need to do is two-fold:

  1. Add SQL Server Agent as a cluster resource type
  2. Add the SQL Server Agent cluster resource to the failover cluster resource group

For the first step, one way to do this is through PowerShell (utilizing the FailoverClusters module):

Import-Module -Name FailoverClusters

$ClusterName = "YourClusterName"
$FciClusterGroupName = "SQL Server (MSSQLSERVER)" # may need to modify to reflect your environment

# check to see if you have the SQL Server Agent cluster resource type
Get-Cluster -Name $ClusterName |
    Get-ClusterResourceType |
    Where-Object {$_.Name -eq "SQL Server Agent"}

# if not, add it
Add-ClusterResourceType -Name "SQL Server Agent" -Dll "sqagtres.dll"

Execute each of those blocks of code separately instead of just all at once. You'll be able to confirm whether or not that cluster resource type exists before just blindly attempting to add it.

Then for the second step, here's what you need to do to add the SQL Server Agent as a resource in your failover cluster resource group:

  1. Right-Click on your FCI resource group within the failover cluster manager
  2. Select "Add a resource" and select the SQL Server Agent resource type
  3. Rename the new cluster resource to "SQL Server Agent"
  4. Go into the new SQL Server Agent resource properties and set the virtual network name and instance name properties
  5. On the dependency tab, set SQL Server as its dependency resource

You may need to go into the registry at the following location and ensure those keys (one will contain the string "AGENT", another "SQL_ENGINE") are set to 1 (this is where it is recorded on what was installed correctly. 1 denotes correct installation):

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\YOURINSTANCE\ConfigurationState

That should get you to a place where you can now install an additional node and have the SQL Server Agent service account appear. Of course, prior to starting ensure that you have a back out here (especially with the registry editing).

Related Question