Issue Adding Node to a SQL Server Failover Cluster – Greyed Out Service Account – How to Resolve

Hi friends! In this post, which is related to SQL Server failover clustering, we will talk about how you can resolve the issue of not being able to add a node to a Server failover cluster, due to the fact that one of the service accounts (i.e. SQL Server or SQL Server Agent, or both) is greyed out during the installation wizard process, meaning that you cannot proceed with the add node operation.

Issue Adding Node to a SQL Server Failover Cluster - Greyed Out Service Account - How to Resolve - Article on SQLNetHub

Greyed out service account in SQL Server Add Failover Cluster Node wizard

Under certain circumstances, after launching the “Add Node to a SQL Server Failover Cluster” wizard from within SQL Server’s installation center, during the process where you need to set the credentials for the service accounts (i.e. SQL Server and/or SQL Server Agent service account), you observe that one of those service accounts is greyed out, meaning that you cannot set it up in the wizard. This has as an effect, not to be able to continue with the installation.

Below, you can find some useful tips, on how you can resolve the issue.

 

How to Resolve the issue

In order to resolve the issue, you can try the following, via the Failover Cluster manager tool.

In the list of resources, under the SQL Server failover cluster role, right-click on the SQL Server service you have trouble configuring its credentials in the add failover cluster node wizard. This can be either the “SQL Server” service, or “SQL Server Agent” or even both. Let’s see below both cases.

So, what you need to fix here in any of the two cases, is the “InstanceName” property in the cluster resources.

Below, we explain what you can try for each one of the two SQL Server services in the cluster.

 

Fixing the issue on the “SQL Server” cluster resource

Within the Failover Cluster Manager, under the SQL Server failover cluster role, right-click on the “SQL Server” resource, select “Properties“, and then again, navigate to the “Properties” tab of the dialog that opens.

Then, in the “InstanceName” property, you will need to make sure that the proper SQL Server instance name is there.

For example, if you are working on a default clustered instance of SQL Server, then, the default instance name would be “MSSQLServer“. In a different case (i.e. you are using a named clustered instance of SQL Server), again, you will need to make sure that the named instance is in the “InstanceName” field.

 

Fixing the issue on the “SQL Server Agent” cluster resource

Within the Failover Cluster Manager, under the SQL Server failover cluster role, right-click on the “SQL Server Agent” resource, select “Properties“, and then again, navigate to the “Properties” tab of the dialog that opens.

Then, in the “InstanceName” property, you will need to make sure that the proper SQL Server instance name is there.

Just like in the first case above, if you are working on a default clustered instance of SQL Server, then, the default instance name would be “MSSQLServer“. In a different case (i.e. you are using a named clustered instance of SQL Server), again, you will need to make sure that the named instance is in the “InstanceName” field.

 

 

Strengthen your SQL Server Administration Skills – Enroll to our Online Course!

Do not miss to enroll to our online course on Udemy titled “Essential SQL Server Administration Tips(special limited-time discount included in link).

Via the course, you will learn essential hands-on SQL Server Administration tips on SQL Server maintenance, security, performance, integration, error handling and more. Many live demonstrations and downloadable resources included!

Essential SQL Server Administration Tips - Online Course with Live Demonstrations and Hands-on Guides
(Lifetime Access/ Live Demos / Downloadable Resources and more!)

Enroll Now with Discount!

 

Featured Online Courses:

 

Read Also:

 

Recommended Software Tools

Snippets Generator: Create and modify T-SQL snippets for use in SQL Management Studio, fast, easy and efficiently.

Snippets Generator - SQL Snippets Creation Tool

Learn more

 

Dynamic SQL Generator: Convert static T-SQL code to dynamic and vice versa, easily and fast.

Dynamic SQL Generator: Easily convert static SQL Server T-SQL scripts to dynamic and vice versa.

Learn more

 


Learn essential SQL Server development tips! Enroll to our Online Course!

Check our online course titled “Essential SQL Server Development Tips for SQL Developers
(special limited-time discount included in link).

Sharpen your SQL Server database programming skills via a large set of tips on T-SQL and database development techniques. The course, among other, features over than 30 live demonstrations!

Essential SQL Server Development Tips for SQL Developers - Online Course
(Lifetime Access, Certificate of Completion, downloadable resources and more!)

Enroll Now with Discount!


Subscribe to our newsletter and stay up to date!

Subscribe to our YouTube channel (SQLNetHub TV)

Easily generate snippets with Snippets Generator!

Secure your databases using DBA Security Advisor!

Generate dynamic T-SQL scripts with Dynamic SQL Generator!

Check our latest software releases!

Check our eBooks!

 

Rate this article: 1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)

Loading...

Reference: SQLNetHub.com (https://www.sqlnethub.com)

© SQLNetHub