Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 12245670
KB4340730 - FIX: Assertion error occurs when a query that uses a linked server is cancelled in SQL Server 2016 and 2017 - Microsoft Support
Last update date:
6/21/2022
Affected products:
SQL Server 2016 Service Pack 1
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2017 Developer on Windows
SQL Server 2017 Enterprise on Windows
SQL Server 2017 Enterprise Core on Windows
SQL Server 2017 Standard on Windows
Affected releases:
build lower than 14.0.3038.14
Fixed releases:
14.0.3038.14
Description:
Symptoms
Assume that you execute a query that uses a linked server in Microsoft SQL Server 2016 and 2017. When the query is cancelled during execution an assertion error may occur rarely and SQL Server may shut down unexpectedly. Additionally, you will receive an error message that resembles the following: DateTime spid82 Error: 17066, Severity: 16, State: 1. DateTime spid82 SQL Server Assertion: File:FileName\FilePath, line=LineNumber Failed Assertion = 'pilb->m_cRef == 0'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. DateTime spid82 Error: 3624, Severity: 20, State: 1.
Resolution
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 11 for SQL Server 2017 Cumulative Update 10 for SQL Server 2016 SP1
