FIX: Availability databases in incorrect initializing/synchronizing state after failover of SQL Server 2014 AlwaysOn availability group

Symptoms

A failover of a SQL Server 2014 AlwaysOn availability group occurs. In this case, the databases in the availability group at the new primary may show as not synchronizing, and the databases in the availability group at the new secondary may show as Initializing/Synchronizing after the failover. Additionally, error messages that resemble the following are logged in the SQL Server error log:

Error: 35278, Severity: 17, State: 4.
Availability database database_name, which is in the secondary role, is being restarted to resynchronize with the ResyncWithPrimary - Damaged [9] - EOL: 00000047:00000F58:0001 Recovery: FFFFFFFF:FFFFFFFF:0001 Undo: 00000047:00000F70:005F current primary database. This is an informational message only. No user action is required.
ResyncWithPrimary - No Undo Needed [9] - EOL: 00000047:00000F58:0001 Recovery: FFFFFFFF:FFFFFFFF:0001 Undo: 00000047:00000F70:005F

Resolution

This issue is fixed in the following cumulative update for SQL Server:


About cumulative updates for SQL Server
About cumulative updates for SQL Server

Status

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

References

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

Article ID: 3206299 - Last Review: Dec 28, 2016 - Revision: 1

Feedback