DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2152734 - Last Review: May 7, 2014 - Revision: 4.0

Symptoms

You might encounter the following error messages when an application submits a query

Msg 605, Level 21, State 3, Line 1
Attempt to fetch logical page (1:224) in database 11 failed. It belongs to allocation unit 72058253744865280 not to 72057594040287232

2009-11-02 15:46:42.90 spid51      Error: 824, Severity: 24, State: 2. 2009-11-02 15:46:42.90 spid51      SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:43686; actual 0:0). It occurred during a read of page (1:43686) in database ID 23 at offset 0x0000001554c000 in file 'H:\MSSQL.SQL2008\MSSQL\DATA\my_db.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

Msg 5180, Level 22, State 1, Line 1
Could not open File Control Bank (FCB) for invalid file ID 255 in database 'mydb'. Verify the file location. Execute DBCC CHECKDB.

Msg 7105, Level 22, State 6, Line 1
The Database ID 11, Page (255:177), slot 1 for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE

2009-12-09 04:53:49.170 spid25s      Error: 823, Severity: 24, State: 2. 
2009-12-09 04:53:49.170 spid25s      The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000132000 in file 'D:\tempdb\tempdb_data.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.



You may also notice these error messages recorded in the SQL Server error log and the Windows Application event log.


Cause

These messages report a inconsistency encountered while attempting to execute queries or internal operations. The cause for these vary depending upon the situations. Refer to the Resolution section for more information about the possible cause for each one of these errors.

Resolution

In order to find the cause and resolve these problems, refer to the following articles that discuss each one of these error messages in detail.


How to troubleshoot Msg 605 with SQL Server (http://support.microsoft.com/?kbid=2015739)

How to troubleshoot Msg 824 in SQL Server (http://support.microsoft.com/?kbid=2015756)

How to troubleshoot Msg 5180 in SQL Server (http://support.microsoft.com/?kbid=2015747)

How to troubleshoot Msg 7105 in SQL Server (http://support.microsoft.com/?kbid=2015760)

How to troubleshoot a Msg 823 error in SQL Server (http://support.microsoft.com/?kbid=2015755)



More information

For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table:
Collapse this tableExpand this table
Rule software

Rule title

Rule description

Product versions against which the rule is evaluated
SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)





Critical SQL database inconsistency errors found






The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect situations where databases encountered critical consistency errors [605, 824, 5180, 7105, 823]. The SQL Server 2008 R2 BPA supports both SQL Server 2008 and SQL Server 2008 R2. 

If you run the BPA tool and encounter an Error with the title of Database Engine - Critical SQL database inconsistency errors found, then you need to follow the recommendations from the resolution section of this article. You have to examine each instance of the errors and perform necessary corrective action.
SQL Server 2008
SQL Server 2008 R2







SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA)




Critical SQL database inconsistency errors found




The SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect situations where databases encountered critical consistency errors [605, 824, 5180, 7105, 823].

If you run the BPA tool and encounter an Error with the title of Database Engine - Critical SQL database inconsistency errors found, then you need to follow the recommendations from the resolution section of this article. You have to examine each instance of the errors and perform necessary corrective action.
SQL Server 2012









Applies to
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Express
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Express
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Web
  • Microsoft SQL Server 2008 R2 Workgroup
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Express
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Web
  • Microsoft SQL Server 2014 Developer
  • Microsoft SQL Server 2014 Enterprise
  • Microsoft SQL Server 2014 Express
  • Microsoft SQL Server 2014 Standard
  • Microsoft SQL Server 2014 Web
Keywords: 
KB2152734
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support