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

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

Status

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

References

Learn about the terminologythat Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×