Monday, December 17, 2012

suspect db in SQL 2008 R2

The Central Administration website of SharePoint 2010 suddenly stopped working giving a 404 HTTP error.

The following error was showing in the ULS logs

12/17/2012 10:42:12.27 OWSTIMER.EXE (0x1A4C) 0x19C8 SharePoint Foundation Database 880i High System.Data.SqlClient.SqlException: Cannot open database "SharePoint_AdminContent_f24be7ea-1371-473f-86bc-145acf0eae8b" requested by the login. The login failed.  Login failed for user '****\****'.     at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)     at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)     at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)     at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)     at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)     at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)     at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)     at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)     at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)     at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)     at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)     at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)     at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)     at System.Data.SqlClient.SqlConnection.Open()     at Microsoft.SharePoint.Utilities.SqlSession.OpenConnection() ff0c77ca-7b2f-42db-a5eb-4eb9062e42b5

Looking at the Central Administration Admin content database, it was in suspect state after an unexpected shutdown of the SQL server.

After running the query below, the database went back to normal and the Central Administration website worked again.

EXEC sp_resetstatus 'SharePoint_AdminContent_f24be7ea-1371-473f-86bc-145acf0eae8b';
ALTER DATABASE "SharePoint_AdminContent_f24be7ea-1371-473f-86bc-145acf0eae8b" SET EMERGENCY
DBCC checkdb('SharePoint_AdminContent_f24be7ea-1371-473f-86bc-145acf0eae8b')
ALTER DATABASE "SharePoint_AdminContent_f24be7ea-1371-473f-86bc-145acf0eae8b" SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB ('SharePoint_AdminContent_f24be7ea-1371-473f-86bc-145acf0eae8b', REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE "SharePoint_AdminContent_f24be7ea-1371-473f-86bc-145acf0eae8b" SET MULTI_USER

No comments:

Post a Comment