Symptoms
Assume that you have a change tracking enabled database in SQL Server 2014, 2016 and 2017. You may encounter a situation where change tracking auto cleanup task may report error message 22122/22123 with table name as garbled characters, or it may hit an access violation when you print the error message. Additionally, you may notice that stack dump occurs. The error log is as follows:
<DateTime> spid# Error: 22123, Severity: 16, State: 1.
<DateTime> spid# Change Tracking autocleanup is blocked on side table of "". If the failure persists, check if the table "" is blocked by any process .
<DateTime> spid# ***Stack Dump being sent to <FileLocation>
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 updates for SQL Server:
Cumulative Update 14 for SQL Server 2017
Cumulative Update 6 for SQL Server 2016 SP2
Cumulative Update 4 for SQL Server 2014 SP3
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:
Latest cumulative update for SQL Server 2017
Latest cumulative update for SQL Server 2016
Latest cumulative update for SQL Server 2014
Workaround
To work around the issue, you can enable trace flag 8293.
References
Learn about the terminology that Microsoft uses to describe software updates.
