FIX: Access violation occurs when change tracking auto cleanup tries to clean up side tables in SQL Server

Applies to: SQL Server 2016 Service Pack 2SQL Server 2016 DeveloperSQL Server 2016 Enterprise

Symptoms


Consider the following scenario:
  • You enable change tracking on a database in Microsoft SQL Server.
  • The change tracking auto cleanup process cleans up the side tables.
  • When the auto cleanup process is about to clean up thelast side table, and if the user disables change tracking on that table, the process encounters an access violation, andgenerates a dump file.
DateTime spid837s    ***Stack Dump being sent to FilePath/FileName
DateTime spid837s    SqlDumpExceptionHandler: Process 837 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
DateTime spid837s    * *******************************************************************************
DateTime spid837s    *
DateTime spid837s    * BEGIN STACK DUMP:
DateTime spid837s    *   DateTime spid 837
DateTime spid837s    *
DateTime spid837s    *
DateTime spid837s    *   Exception Address = 00007FF9E65FF90D Module(sqlmin+0000000000F0F90D)
DateTime spid837s    *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION
DateTime spid837s    *   Access Violation occurred reading address 0000000000000000

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:
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.