Symptoms

Assume that you have an Always On Availability Group (AG) that contains many databases in Microsoft SQL Server 2016. Then, you set the Availability Group to use synchronous commit availability mode together with automatic failover mode.

In this scenario, if a failover occurs, some databases may stop synchronizing. Additionally, error messages that resemble the following might be logged in the SQL Server error log on the secondary replica:

Date/Time    Always On Availability Groups connection with primary database established for secondary database DatabaseName on the availability replica InstanceName with Replica ID: ReplicaID. This is an informational message only. No user action is required.

Date/Time The connection to the primary replica is not active.  The command cannot be processed.

Date/Time Error: 35250, Severity: 16, State: 11

Moreover, error messages that resemble the following are continually logged in the SQL Server error log on the primary replica. This may result in a large log file:

Date/Time Always On Availability Groups connection with secondary database established for primary database DatabaseName on the availability replica InstanceName with Replica ID: ReplicaID.  This is an informational message only. No user action is required.

Date/Time DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: FC202A9E-C3A2-4E30-987A-8C24D3FD70BB:1

Date/Time DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: FC202A9E-C3A2-4E30-987A-8C24D3FD70BB:1

Date/Time DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: FC202A9E-C3A2-4E30-987A-8C24D3FD70BB:1

Resolution

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

       Cumulative Update 7 for SQL Server 2016 RTM

       Cumulative Update 4 for SQL Server 2016 SP1

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2016

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 terminologythat Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×