Tuesday, September 9, 2014

Central Admin content DB in Suspect Mode

Central Admin content DB in Suspect Mode
There are a few times when the central admin content DB gets into suspect mode for no reason.However,there is no reason to panic. we need to run a few set of commands to get our central admin back to running status.
In my case the WSS_Content DB went in suspect mode which was giving error in Central Admin page.
Open the SQL server and perform the following steps as below:

It is recommended to take a backup of the databases the .mdf and .ldf files before performing the below actions.

EXEC sp_resetstatus "WSSContentDB"

ALTER DATABASE "WSSContentDB" SET EMERGENCY
DBCC checkdb('"WSSContentDB"')

ALTER DATABASE ""WSSContentDB"" SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB('"WSSContentDB"',REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE "WSSContentDB" SET MULTI_USER

EXEC sp_resetstatus 'WSSContentDB'

 Now, we can go back and check the SQL server ,the suspect mode gets removed and the Central admin page opens successfully.
No data loss has occured.
at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Export Import Content Types in SharePoint using Powershell CSOM In SharePoint, we have lists and libraries for collaboration purposes....

  • Central Admin content DB in Suspect Mode
    Central Admin content DB in Suspect Mode There are a few times when the central admin content DB gets into suspect mode for no reason....
  • (no title)
    Export Import Content Types in SharePoint using Powershell CSOM In SharePoint, we have lists and libraries for collaboration purposes....
  • Deploy solutions in Sharepoint
    We need to deploy solutions in SharePoint through wsps. There are generally 2 commands : First is to Add the solution ,then to instal...