Thursday, February 15, 2007

Cannot connect to the configuration database Sharepoint page and central administration

Problem Definition:


Sharepoint page throws 'Cannot connect to the configuration database'
Error :


Reason:




backend database is down or authentication failed.




Fix:




To fix this problem, you need to know the database server's name. If you know the server's name, you can skip the below and follow the step 1.




Database server name will be specified on the Sharepoint central administration's home page. But, if this error occurs, SCA will be also down. So the only way you will come to know is through logs. Default location of the logs is 'C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\Logs'




In the logs, you will see some thing like this:




Critical Cannot connect to SQL Server. 'Your DB server name' not found. Additional error information from SQL Server is included below. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. OWSTIMER.EXE (0x09C4) 0x127C Windows SharePoint Services Database




System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)




Once you got the server name, follow the below steps:




  1. Check whether the database server is down. If it is down, start the server.


  2. Check whether Database server's MSSQLSERVER service is stopped. If stopped, start the service
    Start -> Programs -> admin tools -> Services -> MSSQLSERVER -> Right click -> Start
    (Note: Some servers will have MS$SHAREPOINTSERVER)


  3. Check whether the MSSQLSERVER service id/pwd is same as the sharepoint Application pool identity or not.

    steps to know the MSSQLSERVER identity:
    Start -> Programs -> admin tools -> Services -> MSSQLSERVER -> Double click -> Logon

    steps to know the Application Pool identity:
    Start -> Programs -> admin tools -> IIS ->right click on the specific application pool that your application is running on -> Properties -> Identity

    If these two Id/pwds are not same, then make it same.
    Also check whether the password is expired/changed.












1 comment:

  1. Hi Umakanth,
    This is Shabana, The info is very useful.

    Thanks,
    Shabana

    ReplyDelete