Symptoms
Assume that you use Always On Availability Groups (AG) in Microsoft SQL Server. When you set automatic seeding for secondary replica or Distributed Availability Group replica, access violations and unhandled exceptions may occur.
Resolution
This issue is fixed in the following cumulative updates for SQL Server:
Cumulative Update 13 for SQL Server 2017
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 2017 Latest cumulative update for SQL Server 2016
Workaround
To work around this issue, use one of the following methods:
-
Do not use automatic seeding.
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 that Microsoft uses to describe software updates.
