Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


Assume that you create more than one availability group in Microsoft SQL Server 2014 or 2016, and each node owned one AG group. When you shut down or power off one node suddenly, and you click failover on an availability group that's in the resolving state, in this situation, you cannot select any replica in grid, and the Current Primary Replica is wrong.


This issue occurs because the following statement returns the wrong primary replica for the resolving AG, it should be null. However, the following statement returns the active node:select * from master.sys.dm_hadr_availability_group_states


The issue was fixed in the following cumulative update of SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:


To work around this issue, use the following Transact-SQL command to fail over manually:ALTER AVAILABILITY GROUP xxx FORCE_FAILOVER_ALLOW_DATA_LOSS;


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!