Solutions:
1. Restore a backup of the Content database.
Caution: Below steps may cause to lose data that's why it is extremely dangerous to execute. I will recommend you to try all other better solutions including calling to Microsoft Support, third party SharePoint Recovery Software etc.
2. To resolve the issue, use following steps in order as mentioned:
– Use the Master database
– Verify that database has issues
EXEC sp_resetstatus ‘SharePoint_Config’
– Put the database in emergency mode
ALTER DATABASE SharePoint_Config SET EMERGENCY DBCC checkdb(‘SharePoint_Config’)
– Set the database in single user mode
ALTER DATABASE SharePoint_Config SET SINGLE_USER WITH ROLLBACK IMMEDIATE
–Repair the database with data loss
DBCC CheckDB (‘SharePoint_Config’, REPAIR_ALLOW_DATA_LOSS)
–Set the database in multi-user mode
ALTER DATABASE SharePoint_Config SET MULTI_USER
–Verify that database is reset
EXEC sp_resetstatus ‘SharePoint_Config’
After running the above steps on the Master database, I Fixed Suspected SharePoint_Config database & Now I am able to access the content web application.
This post first appeared on An Informative Blog About SharePoint, please read the originial post: here
