FIX: Access violation occurs and data movement is suspended for databases in Availability Group in SQL Server 2017

Applies to: SQL Server 2017 Developer on WindowsSQL Server 2017 Enterprise on WindowsSQL Server 2017 Enterprise Core on Windows More

Symptoms


Assume that you use AlwaysOn Availability Groups feature in SQL Server 2017. An access violation may occur and the data movement is suspended for databases in an Availability Group. Additionally, you may receive error messages that resemble the following in the SQL Server error log:

DateTime spid#    AlwaysOn Availability Groups data movement for database 'SSISDB' has been suspended for the following reason: "system" (Source ID #; Source string: ‘#’). To resume data movement on the database, you will need to resume the database manually. For information about how to resume an availability database, see SQL Server Books Online.

Error: 3313, Severity: 21, State: 2.

DateTime spid#   During redoing of a logged operation in database 'SSISDB', an error occurred at log record ID (638:319687:1). Typically, the specific failure is previously logged as an error in the operating system error log. Restore the database from a full backup, or repair the database.

Status


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

Resolution


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

About cumulative updates for 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. Check out the latest cumulative updates for SQL Server:

References


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