118570: SQL Server

2 replies [Last post]
Eric Greer
Joined: 2016-05-17
Posts: 1

I get 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

What’s wrong?       

Ekaterina Surkova
Ekaterina Surkova's picture
Forum Administrator
Joined: 2013-07-15
Posts: 1698


Thank you for your posting. Could you please provide more information on the issue:

  • exact product name and build you are using
  • when exactly the error message appears, if possible attach a screenshot
  • please attach the whole error message

Thank you,


Ekaterina Surkova | Acronis Customer Central | Acronis Backup Software | For more answers to your questions, try our Knowledge Base and Video Tutorials. | Check our Corporate and Consumer Handbooks and Online Documentation for help on managing your account, products and support. | Our mission is to create Customer success. Our management team welcomes your comments and suggestions on how we can improve the overall support we provide to you. Please send your comments, suggestions, or concerns to Managers or submit your feedback here.

Coondada Coondada
Joined: 2016-05-25
Posts: 1

If DBCC CHECKDB or CHECKTABLE reports an error (which should be Msg 2533), then the page is damaged or an incorrect page. You should restore from a backup to resolve the problem. If you cannot restore from a backup, use the repair options with DBCC CHECKDB. To find the cause of this problem you should use techniques as you would with other database corruption errors including:

Check for hardware or system level problems (A tool such as SQLIOSIM can be helpful to do this. SQLIOSIM ships with SQL Server 2008 and SQL Server 2008 R2 and does not require a separate download)

Ensure you have the PAGE_VERIFY=CHECKSUM database option turned on. While it is possible to still encounter a Msg 605 error with checksum enabled (Ex. "scribbler" problem or incorrect page provided from I/O system), enabling checksum can provide definitive proof that the page was modified incorrectly within the I/O system.

Try to restore a database backup you know that will be "clean" (no errors from CHECKDB) and transaction log backups you know span the time when the error was encountered. If you can "replay" this problem by restoring a "clean" database backup and transaction logs then contact Microsoft Technical Support for assistance.

For more information about database corruption problems see here: https://www.fixtoolbox.com/sqlserverfix.html SQL Server Fix Toolbox