FIX: Assertion error occurs when you restart the SQL Server 2016 database

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


Assume that you create a database and a primary transaction log file in Microsoft SQL Server 2016. You run some transactions to grow the files. In this scenario, when you restart the database server, an assertion error occurs. Additionally, the following mini dump file is generated:

DateTime     **Dump thread - spid = 0, EC = 0x0000026FEE9AB2C0
DateTime     ***Stack Dump being sent to FilePath\FileName
DateTime     * *******************************************************************************
DateTime     *
DateTime     *   DateTime
DateTime     *
DateTime     * Location:  FilePath\FileName
DateTime     * Expression:  ret == itFcb->lfcb_fSeqNo
DateTime     * SPID:   36
DateTime     * Process ID: ProcessID
DateTime     Error: 17066, Severity: 16, State: 1.
DateTime     SQL Server Assertion: File: <FilePath\FileName>, line=LineNumber Failed Assertion = 'ret == itFcb->lfcb_fSeqNo'. 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     Error: 3624, Severity: 20, State: 1.
DateTime     A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.


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


Learn about the terminology that Microsoft uses to describe software updates.