FIX: You receive error messages when you run a query that uses tempdb in SQL Server
You run a query on an instance of Microsoft SQL Server 2012. If the query uses tempdb, you might receive the following error messages:
- Error: 5180, Severity: 22, State: 1.
Could not open File Control Block (FCB) for invalid file ID 0 in database 'tempdb'.
- Error: 17066, Severity: 16, State: 1.
SQL Server Assertion: File:< Alloc.cpp>, line=2697 Failed Assertion = 'IAM_pg_id != PageId_NULL'.
- Error: 3624, Severity: 20, State: 1.
A system assertion check has failed. Check the SQL Server error log for details.
- Error: 605, Severity: 21, State: 3.
Attempt to fetch logical page (19:31824) in database 2 failed. It belongs to allocation unit 0 not to 720680216393744384.
This issue may occur when you use one of the following features:
- Optimistic transaction isolation levels
- Online indexing
- Multiple active result sets (MARS)
This issue was first fixed in the following cumulative update of SQL Server:
- Cumulative Update 10 for SQL Server 2012 Service Pack 2
- Cumulative Update 1 for SQL Server 2012 Service Pack 3
Recommendation: Install the latest cumulative update for SQL Server
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included in the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Note You can find information about the latest SQL Server builds from Where to find information about the latest SQL Server builds.
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.
Article ID: 3125526 - Last Review: 01/25/2016 08:32:00 - Revision: 2.0
Microsoft SQL Server 2012 Service Pack 3, Microsoft SQL Server 2012 Service Pack 2
- kbqfe kbfix kbexpertiseinter kbsurveynew KB3125526