WSS 3.0 – Cannot connect to the configuration database

Cannot connect to the configuration database on WSS 3.0 might be one of the most common problem user had. There are a lot of possibilities on the root cause of this issue and the workaround/solution.

The Symptoms

1. When trying to access the WSS, you get a white page saying “cannot connect to configuration database”.
2. You are getting below event in the event logs

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: General
Event ID: 27745
Date: 06/01/2010
Time: 9:17:00 PM
User: N/A
Computer: AMEENSBS
Description:
The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: #50071: Unable to connect to the database SharePoint_Config on AMEENSBS. Check the database connection information and make sure that the database server is running..
3. Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 18053
Date: 06/01/2010
Time: 9:16:40 PM
User: N/A
Computer: AMEENSBS
Description:
Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
4. Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 5586
Date: 06/01/2010
Time: 9:08:08 PM
User: N/A
Computer: AMEENSBS
Description:
Unknown SQL Exception 233 occured. Additional error information from SQL Server is included below.

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe.)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
5. Named pipes protocol was diasabled in the SQL Server network configuration protocols.

The Solutions

1. If the WSS is in a server farm, use the “SharePoint Products and Technologies Configuration Wizard” to disconnect the server from the farm.
2. go to Start >Program > Microsoft SQL Server 2005 > Configuration Tools >SQL Server Configuration Manager
3. Navigate to SQL Server 2005 Network Configuration > Protocol for MSSQLSERVER
4. Right click Named Pipes and select Enable (if not enabled)
5. Restart SQL Server
6. Join back the server to server farm using “SharePoint Products and Technologies Configuration Wizard” and follow the wizards.

Note:

I haven’t tried skip all the steps and straight way to step no 4 and no 5 and check whether it solves the problem. Anyone can verify this is the only steps needed? Thanks

8 comments

  1. Antony

    Went straight to 3 and found named pipes disabled for Sharepoint database. Enabled, restart, iisreset and worked great – thanks

    An SBS 2011 standard box

Leave a Reply