Resolving "SQL Server detected a logical consistency.." SharePoint Error

Microsoft SharePoint Server uses MS SQL Server database, which is extremely powerful and advanced. However, under some situations, this database may become inaccessible due to logical corruption and lead to severe data loss. SharePoint can not recognize the database after corruption and you need to opt for SharePoint tools to get your mission critical data back.

Consider this scenario as a real example of database corruption in MS SharePoint Server. You cannot access and perform any operation on your database and see the following errors in Event Log of MS SQL Server-

“SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:80; actual 0:0). It occurred during a read of page (1:80) in database ID 11 at offset 0x000000000a0000 in file ‘G:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATASharedServices_Search_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.”

In order to fix this problem with SharePoint database, you need to identify the actual reason of this problem and perform recovery for SharePoint by fixing it.

Root of the problem-

This problem usually occurs when you try to fix database consistency issues using DBCC CHECKDB command, due to any of the following reasons-

  • SQL Server database is logically damaged and it is unreadable.
  • The database was created in earlier version and can not be attached with newer version of SharePoint. Thus it throws I/O errors.


You can try for the following solutions to SharePoint recover site-

  • Create complete backup of the database and then run DBCC CHECKDB to fix integrity issues.
  • Install compatible version of MS SharePoint. Application version compatibility is a major factor of read/write errors with SQL Server database.
  • Restore SQL Server database from the most recent backup. If you suspect that backup is not complete, then you should not restore the database.

When all other solutions fail to work, SharePoint recovery software come for your rescue. These are advanced third-party applications, which methodically scan whole database and repair damaged database in all corruption scenarios.

Stellar Phoenix SharePoint Server Recovery is the most efficient solution to recover corrupt databases of MS SharePoint 2010 and 2007.

Source by Tanvi Sharma