Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

SQL Server Error 19471: Create failed for Availability Group Listener

by | May 13, 2021

Often while configuring Always On Availability Group on the database server, it displays Microsoft SQL Server error 19471.

As a part of our Server Management services, we help to fix similar SQL-related errors regularly.

Today, let us see how our Support Engineers fix this error.


 

What is “SQL Server Error 19471”?

Recently we received a support request that the customer was receiving an error while configuring Always On Availability Group again on the database server. We noticed that the listener failed to create during AOAG configuration and it displayed Microsoft SQL Server error 19471.

SQL Server Error 19471

On checking the AlwaysOn High Availability folder on any of the replica, everything was working fine. AOAG was configured successfully and working fine, but listener was not configured due to above error.

There is no listener showing in their respective folder of the AOAG configuration. When tried creating Listener name from “Add Listener…” wizard, it failed with same error.
 

How to fix “SQL Server Error 19471”?

To solve this error, we can follow the steps given below to add the listener.

  • Create a Client Access Point (CAP) for the AOAG listener in Failover Cluster Manager.
  • Bring CAP Online.
  • Repair the CAP, if it is not coming ONLINE.
  • Once CAP comes online, remove it from the failover cluster manager.
  • Add a listener to AOAG in SQL Server Management Studio (SSMS).

We have to remove CAP after adding, repairing, and bring it online. Creating CAP and bringing it online is to just verify that everything is fine or not. If CAP will not come online, then there might be some issue at a certain level that needs to be fixed first before creating a listener.

Launch failover cluster manager and click on the Roles tab from the left side pane. Here we can see our availability group role in the right-side pane. Right-click on this role and select “Add Resources”. Then click on “Client Access Point“.

We will get a screen to enter listener details. Enter listener name into name section and listener IP into Address section. On clicking the Next button to proceed, it resulted in the error given below:

'Listener_name' listener is already in use in Active Directory.

The listener name and IP address should be unique and unused. So we need to remove these listener details from Active Directory.

Once listener details will be cleared from Active Directory, go ahead and try to add listener name to the existing AlwaysOn Availability Group. This time we will be able to create the listener name.
 

Failed to add Listener after clearing DNS entries and DNS Status showing “The handle is invalid”

If we are still facing the same issue during adding listener or configuring AlwaysOn Availability Group, then there is a possibility of some entries in AD for the listener name and IP during our failed attempts to create the listen to name. If there is no entry, then follow the steps given below:

We will create a Client Access Point in the failover cluster manager for the Availability Group role. Right-click on Availability Group role, select “Add Resources” and then “Client Access Point”. We will get a screen to enter the listener name and corresponding IP address. Click on the Next button to proceed post entering the listener details.

We will get a screen to proceed, once we click on the next button.

Click on Finish button to create the Client Access Point in failover cluster manager for this listener.

Once we will click on finish button, Client Access Point for our listener will be created in the failover cluster manager. The Availability Group role was running fine. But after adding Client Access Point, it has changed into Partial Running mode.

We can see CAP is showing as offline, due to which Availability Group role has changed into Partial Running mode. Now we will bring it online manually. Right click on Listener CAP and click on “Bring Online” option.

We can see Listener IP has come online whereas listener name failed to come online. Let us check the properties of the client access point (CAP).

Right click on Listener Name and choose Properties option. We will get a screen where we can see NetBIOS, DNS and Kerberos status. NetBIOS and Kerberos status is showing OK. But DNS status is not OK and showing “The handle is invalid.” This is the issue that needs to be fixed to create listener.
 

“The handle is invalid” Error

When we checked the cluster events, we saw below error details:

Cluster network name resource ‘Cluster Name’ failed registration of one or more associated DNS name(s) for the following reason:
The handle is invalid.

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.

To fix this DNS issue (The handle is invalid), we will repair this CAP. Right click on Listener Name showing in failover cluster manager, click on “More Actions” and then click on Repair.

Once we will click on Repair, it will come online and then go in offline. Now right click on Listener name again and click on Bring Online button. This time Listener Name will come online if CAP has been repaired successfully. We can repeat the repair, if CAP is not coming online. If we are still facing issue, then we can again contact to domain admin to look into Active Directory server.

Now we can see Client Access Point for the listener is showing online. If we go to the property of this Listener CAP, we can see NetBIOS, DNS and Kerberos status is showing OK.

Close above property window. The next step is to remove this Client Access Point for this Listener and create the listener in SSMS that will create Listener client access point (CAP) automatically in the failover cluster manager.

Once we click on remove button, another window will come to proceed. Click on OK to proceed.
 

Adding Listener

Once this CAP is removed, then connect to primary replica of the AOAG configuration. Expand the AlwaysOn High Availability folder and then Availability Group Listeners folder. We will not be able to see anything as there is no listener as of now. Right click on Availability Group Listeners folder and click on “Add Listener…” option.

We will get New Availability Group Listener Wizard to enter the listener details. Enter the Listener DNS Name then followed port by choosing Network Mode. Click on Add button to enter Listener IP Address. Once we are done with all details, click on OK button to apply this changes. Add Listener wizard will disappear if listener will be created successfully. Otherwise, it will give the error on the same wizard.

As we have created Availability Group Listener for this AOAG configuration, we can go ahead and verify this in SSMS by expanding Availability Group Listeners folder. We can see the same listener name is showing under Availability Group Listeners folder on both primary as well as secondary replica.

 
[Need any further assistance to fix SQL errors? – We’re available 24*7]

Conclusion

In short, “SQL Server Error 19471” can trigger while configuring Always On Availability Group again on the database server. Today, we saw how our Support Engineers fix this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

SEE SERVER ADMIN PLANS

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF