Microsoft SQL Server - Defect ID: 14662889

An assertion failure occurs in tempdb during the rollback of transactions, and triggers a server shutdown. The following dump file is generated: <DateTime> **Dump thread - spid = 0, EC = 0x000004849143B870 <DateTime> ***Stack Dump being sent to FilePath\FileName <DateTime> * *******************************************************************************<DateTime> *<DateTime> * BEGIN STACK DUMP: <DateTime> * DateTime <DateTime> * <DateTime> * Location: FilePath\FileName <DateTime> * Expression: Dependencies.CommitDepCountOut >= 1 <DateTime> * SPID: SPID <DateTime> * Process ID: ProcessID <DateTime> * <DateTime> * Input Buffer 26 bytes - <DateTime> * ‰ 16 00 00 00 12 00 00 00 02 00 89 01 00 00 90 0f 00 00 <DateTime> * 01 00 00 00 07 00 00 00 <DateTime> SQL Server Assertion: File: < FilePath\FileName >, line=LineNumber Failed Assertion = 'Dependencies.CommitDepCountOut >= 1'. 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.<DateTime> Error: 3314, Severity: 21, State: 3. <DateTime> During undoing of a logged operation in database 'DatabaseName' (page (1:139) if any), an error occurred at log record ID (3692:89591460:155). Typically, the specific failure is logged previously as an error in the operating system error log. Restore the database or file from a backup, or repair the database.