What does this guide do?

Help you solve some of the common issues you may run into when working with AlwaysOn Configuration on SQL server.

Who is it for?

SQL server admins who need to create, configure and manage AlwaysOn Availability groups.

How does it work?

We’ll begin by asking you the SQL issue that you are facing. Then we’ll take you through a series of steps that are specific to your situation.

Estimated time of completion:

15-30 minutes.

What issues are you facing?


What issues are you facing?


I need pointers on setting up AlwaysOn Availability groups

If you are looking for documentation on setting up AlwaysOn configuration please review the following documents:

Getting Started with AlwaysOn Availability Groups (SQL Server) - The document provides answers to many questions you may have related to Availability groups, setup etc. Following all the steps in this doc and reviewing Prerequisites, Restrictions, and Recommendations for AlwaysOn Availability Groups (SQL Server) will help prevent a lot of issues that you may run into with setting up and maintaining availability groups in your environment.

Additional resources:

Is this information helpful?

I am having problems configuring AlwaysOn Availability groups

Typical configuration problems include AlwaysOn Availability Groups are disabled, accounts are incorrectly configured, the database mirroring endpoint does not exist, the endpoint is inaccessible (SQL Server Error 1418), network access does not exist, and a join database command fails (SQL Server Error 35250). Review the following document for help on troubleshooting these issues.

Troubleshoot AlwaysOn Availability Groups Configuration (SQL Server)

Additional links:

Did this resolve your issue?

I am having issues with Listener configuration

One of the most common configuration issues customers encounter is availability group listener creation. The errors are similar to the following:

Msg 19471, Level 16, State 0, Line 2The WSFC cluster could not bring the Network Name resource with DNS name '' online. The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible. Use a different DNS name to resolve name conflicts, or check the WSFC cluster log for more information.      
Msg 19476, Level 16, State 4, Line 2The attempt to create the network name and IP address for the listener failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator.

The majority of time, listener creation failure resulting in the messages above are due to a lack of permissions for the Cluster Name Object (CNO) in Active Directory to create and read the listener computer object. For troubleshooting this problem, please review the following articles:

Additional links:

Create or Configure an Availability Group Listener (SQL Server)

Did this resolve your issue?

Automatic Failover is not working as expected

If you notice that the automatic failover is not working as expected either during testing or in production, review the following articles:

Did this resolve your issue?

I am having issues connecting to AlwaysOn Availability groups

After you configure the availability group listener for an AlwaysOn Availability Group in Microsoft SQL Server 2012, you may be unable to ping the listener or connect to it from an application. You may get an error that is similar to the following:

Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

To troubleshoot this and similar errors review the following:

Additional information:

Did this resolve your issue?

I am having issues configuring AlwaysOn Availability groups in my Azure VM (IaaS)
  1. Lot of issues related to AlwaysOn occur due to improper configuration of the listener. If you are having connection issues to the listener,
    1. Ensure you read all the limitations of ILB listener and followed all the steps documented in the following article paying particular attention to dependency configuration, IP address, and various other parameters in the PowerShell script.
      Configure an ILB listener for AlwaysOn Availability Groups in Azure
    2. If unsure, you may want to delete and recreate the listener as per the above document.
  2. If you recently moved your VM to a different service or if the IP addresses changed, you need to update the value of the IP address resource to reflect the new address and you need to recreate the load balanced endpoint for your AG. You can update the IP address using the Get/Set commands as follows:
    Get-ClusterResource "IPResourceName" | Set-ClusterParameter -name Address –value “w.x.y.z”

Recommended docs:

Did this resolve your issue?

It takes a long time to failover from primary to secondary or vice-versa

After an automatic failover or a planned manual failover without data loss on an availability group, you may find that the failover time exceeds your recovery time objective (RTO). To troubleshoot the causes and potential resolutions review the following Troubleshooting guide on MSDN:

Did this resolve your issue?

Changes on the Primary Replica are not Reflected on the Secondary Replica

You may notice that changes on primary replica are not getting propagated to secondary in a timely manner. To troubleshoot and resolve these problems, review the following troubleshooter on MSDN:

Did this resolve your issue?

How to manage the size of transaction log for my AG databases ?

You can reduce the transaction log sizes by configuring regular backups at either primary or secondary servers. Review the following topics for additional information:

Is this information helpful?


Congratulations! We are glad this guide is helpful and your issue is resolved.


We're sorry you cannot solve the issue by this guide. For more information about AlwaysOn Availability Groups , please see the following:


رقم الموضوع: 10179 - آخر مراجعة: 03‏/03‏/2016 - المراجعة: 14