FIX: Stack Dump occurs in the change tracking cleanup process in SQL Server 2014, 2016 and 2017

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


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 onside table of "岝縋잭橦䱂䭃Y". If the failure persists,check if the table "岝縋잭橦䱂䭃Y" is blocked by any process.

<DateTime> spid#   ***Stack Dump being sent to <FileLocation>


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


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

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


To work around the issue, you can enable trace flag 8293.


Learn about the terminology thatMicrosoft uses to describe software updates.