Alex Entrekin

How to Recover SharePoint 2013 Databases from Suspect Mode

January 29th, 2013 | Author: | Filed under: CloudShare, Dev / Test, SharePoint | Tags: , , , , , , , , , ,

I restarted my SharePoint server, opened Central Administration and encountered the following error:

Server Error in ‘/’ Application
Runtime Error
Description: An application error occurred on the server.

01 - SharePoint 2013 Server Error in Application

In order to troubleshoot this issue I had to check couple of thing:

  • Make sure SQL Server services are up and running
  • Make sure the IIS application pools are started
  • Review Windows logs and gather more information about the server. I noticed the following event:

SQL Database ‘SharePoint_Config’ on SQL Server instance ‘C4968397007′ not found. Additional error information from SQL Server is included below.

Cannot open database “SharePoint_Config” requested by the login. The login failed. Login failed for user ‘DC07\SQLSvc’.

02.1 - Windows logs

This event made me suspect something is wrong with my SQL Server. I opened SQL Server management studio and noticed that some of my most critical SharePoint databases are not accessible and set to suspect mode. 02 - SharePoint 2013 databases are in Suspect mode

What is a suspect mode in SQL Server database?

Suspect mode might be caused by many reasons like unavailable or corrupted database files, hardware failure etc.

Don’t worry! This situation is reversible.

Here’s a quick guide of how to recover your SharePoint databases from suspect mode:

Open your SQL Server management studio and execute the following queries one after another:

  • Run the following query. sp_resetstatus command will turn off suspect flag on the database. 

EXEC sp_resetstatus ‘SharePoint_Config';

After executing this query you’ll see the following warning. Don’t worry, this doesn’t mean you did something wrong.

04 - SQL Server reset status of database warning

  • The next step is to set the database to an Emergency mode. This can be done by executing following query:


After executing this query your database should look like this:

06 - SharePoint_config database is set to emergency mode

Once we set the database to an Emergency mode it temporarily becomes a Read Only database.

  • Execute the following query in order to check the logical and physical integrity of the objects in the database.

DBCC checkdb(‘SharePoint_Config’)

  •  To complete the process, run the following queries:

SharePoint_Config SET SINGLE_USER

DBCC CheckDB (‘SharePoint_Config’, REPAIR_ALLOW_DATA_LOSS)


DBCC CheckDB (‘SharePoint_Config’)

Repeat this action for each one of the affected databases.

09 - Everything is back to track

I ran some basic tests to make sure my SharePoint server is working properly again, looks like everything is back to track.


About the author:
As CloudShare’s Business Development Manager, Alex is the (super) everyman for CloudShare’s partners and customers. He moves between development, sales and operations to ensure that everything up in the cloud makes it down to earth. Alex earned a law degree from the UCLA School of Law and has experience building out early stage businesses in tech, specialty finance, and sports. A former professional baseball player, he spends some weekends playing catcher for the San Francisco Pelicans, one of two San Francisco franchises in the Bay Area's 1880's style baseball league.

10 Comments on “How to Recover SharePoint 2013 Databases from Suspect Mode”

  1. […] I restarted my SharePoint server, opened Central Administration and encountered the following error: Server Error in ‘/’ Application Runtime Error Description: An application error occu…  […]

  2. Gizzy
    02/20/13, 1:18 pm

    Do you know why this happened in your particular case?

  3. Henry
    03/11/13, 10:29 am

    Excellent …Thanks a ton !!

  4. Jihane LAZRAG
    03/25/13, 9:00 am


  5. Eric
    04/13/13, 9:36 am


    Yes do you know the cause of this ?
    It happened to me as well but did not find out why…


  6. nnmnnnm
    12/21/13, 4:21 am


  7. […] A quick search on how to resolve this issue brought me to this:  Thanks to Lydia Bronze […]

  8. Hossein
    08/05/14, 10:19 pm


    and Thanks for your Article. I have just done your steps and now my database is in Emergency mode but when I run this query I got this error :

    DBCC checkdb(SharePoint_AdminContent_ac473b5a-af02-4f69-84f3-9ad0fb4a4425′)

    Msg 5245, Level 16, State 1, Line 1

    Object ID 389576426 (object ‘dbo.AllDocVersions’): DBCC could not obtain a lock on this object because the lock request timeout period was exceeded. This object has been skipped and will not be processed.

    DBCC results for ‘SharePoint_AdminContent_ac473b5a-af02-4f69-84f3-9ad0fb4a4425′.

    CHECKDB found 0 allocation errors and 0 consistency errors in database ‘SharePoint_AdminContent_ac473b5a-af02-4f69-84f3-9ad0fb4a4425′.

    what is wrong here??? can I follow other steps?

    and also by going to Emergency mode, I can see all tables inside it and also I can run central administration as well.

    Thanks in advanced

  9. Nadeem Yousuf
    08/22/14, 4:40 am

    Perfect. I got some errors in first DBCC checkdb command but continued to execute all the commands till end and finally had my SharePoint up and running again.

  10. Thai Le
    09/28/14, 8:14 pm

    Thanks :)

Leave a Reply

Your email is kept private. Required fields are marked *