Cannot connect to the configuration database

Problem:

When connecting to Sharepoint website via web browser, following message is
displayed: "Cannot connect to the configuration database."

After a few weeks of running fine, all of a sudden the Sharepoint app is
unable to connect to the WMSDE database, and there are no obvious
indiciations as to the problem. The MSSQL$SHAREPOINT service starts up fine
and no errors are logged in ERROLOG or NT event log, however it is impossible
to connect to the database using the Sharepoint user or admin website, OSQL,
or the sharepoint STSadmn tool.

The only way that I have been able to temporarily resolve the problem is to:
- uninstall Sharepoint
- uninstall WMSDE
- reinstall Sharepoint and WMSDE
- restore the Sharepoint db using the command STSADM.EXE -o restore

Everything then works fine again for a weeks util the same problem
resurfaces. This is the 4th time that it has occurred

The following Microsft KB articles did not resolve or were not relevant to
the problem

http://support.microsoft.com/?id=823287
http://support.microsoft.com/default.aspx?kbid=833183


Server Configuration:

Cleanly installed server dedicated to running Sharepoint

OS: Windows 2003 Server
SP ver: Windows SharePoint Services with Service Pack 1 (SP1)
db: WMSDE (installed with Sharepoint Microsoft SQL Server 2000 - 8.00.884)
other installed software: Symantic A/V 10, NetVault backup agent

Mike
Fri Jul 29 09:46:09 CDT 2005

Sorry that I didn't spot this before

> db: WMSDE (installed with Sharepoint Microsoft SQL Server 2000 -
> 8.00.884)

Does this mean that you already had SQL Server 2K installed on this server
and that when you installed WSS you selected the default install (which
installs WMSDE) ?

I.e. that your WSS installation is using WMSDE as its database instance?

Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please reply to the newsgroup

"Cambio Del Arte" <parisit@nospam.nospam> wrote in message
news:FA6FA10C-F23C-475C-8CE5-FBE79BC6605E@microsoft.com...
> Problem:
>
> When connecting to Sharepoint website via web browser, following message
> is
> displayed: "Cannot connect to the configuration database."
>
> After a few weeks of running fine, all of a sudden the Sharepoint app is
> unable to connect to the WMSDE database, and there are no obvious
> indiciations as to the problem. The MSSQL$SHAREPOINT service starts up
> fine
> and no errors are logged in ERROLOG or NT event log, however it is
> impossible
> to connect to the database using the Sharepoint user or admin website,
> OSQL,
> or the sharepoint STSadmn tool.
>
> The only way that I have been able to temporarily resolve the problem is
> to:
> - uninstall Sharepoint
> - uninstall WMSDE
> - reinstall Sharepoint and WMSDE
> - restore the Sharepoint db using the command STSADM.EXE -o restore
>
> Everything then works fine again for a weeks util the same problem
> resurfaces. This is the 4th time that it has occurred
>
> The following Microsft KB articles did not resolve or were not relevant to
> the problem
>
> http://support.microsoft.com/?id=823287
> http://support.microsoft.com/default.aspx?kbid=833183
>
>
> Server Configuration:
>
> Cleanly installed server dedicated to running Sharepoint
>
> OS: Windows 2003 Server
> SP ver: Windows SharePoint Services with Service Pack 1 (SP1)
> db: WMSDE (installed with Sharepoint Microsoft SQL Server 2000 -
> 8.00.884)
> other installed software: Symantic A/V 10, NetVault backup agent
>
>

parisit
Fri Jul 29 10:32:04 CDT 2005

SQL 2000 was never installed, Sharepoint is definately using WMSDE. The
version number you see was extracted from the WMSDE ERRORLOG file. I presume
that this version number implies that it is the "WMSDE" version of SQL2000.

"Mike Walsh" wrote:

> Sorry that I didn't spot this before
>
> > db: WMSDE (installed with Sharepoint Microsoft SQL Server 2000 -
> > 8.00.884)
>
> Does this mean that you already had SQL Server 2K installed on this server
> and that when you installed WSS you selected the default install (which
> installs WMSDE) ?
>
> I.e. that your WSS installation is using WMSDE as its database instance?
>
> Mike Walsh, Helsinki, Finland
> WSS FAQ at http://wss.collutions.com
> Please reply to the newsgroup
>
> "Cambio Del Arte" <parisit@nospam.nospam> wrote in message
> news:FA6FA10C-F23C-475C-8CE5-FBE79BC6605E@microsoft.com...
> > Problem:
> >
> > When connecting to Sharepoint website via web browser, following message
> > is
> > displayed: "Cannot connect to the configuration database."
> >
> > After a few weeks of running fine, all of a sudden the Sharepoint app is
> > unable to connect to the WMSDE database, and there are no obvious
> > indiciations as to the problem. The MSSQL$SHAREPOINT service starts up
> > fine
> > and no errors are logged in ERROLOG or NT event log, however it is
> > impossible
> > to connect to the database using the Sharepoint user or admin website,
> > OSQL,
> > or the sharepoint STSadmn tool.
> >
> > The only way that I have been able to temporarily resolve the problem is
> > to:
> > - uninstall Sharepoint
> > - uninstall WMSDE
> > - reinstall Sharepoint and WMSDE
> > - restore the Sharepoint db using the command STSADM.EXE -o restore
> >
> > Everything then works fine again for a weeks util the same problem
> > resurfaces. This is the 4th time that it has occurred
> >
> > The following Microsft KB articles did not resolve or were not relevant to
> > the problem
> >
> > http://support.microsoft.com/?id=823287
> > http://support.microsoft.com/default.aspx?kbid=833183
> >
> >
> > Server Configuration:
> >
> > Cleanly installed server dedicated to running Sharepoint
> >
> > OS: Windows 2003 Server
> > SP ver: Windows SharePoint Services with Service Pack 1 (SP1)
> > db: WMSDE (installed with Sharepoint Microsoft SQL Server 2000 -
> > 8.00.884)
> > other installed software: Symantic A/V 10, NetVault backup agent
> >
> >
>
>
>

DaveBone
Fri Jul 29 11:15:02 CDT 2005

Hi,

Could it be the account that WMSDE uses to start? In SQL Server if you use
an account and the account password changes then you get connection errors.

I have a SQL Server database on a test platform that uses my personal
active directory account. We have to periodically change the password on our
accounts and when I do if I do not change the password in SQL Server then it
fails to start.

Check in the services Log On properties for WMSDE to see which account it
uses. It should probably use a Local System account


Dave

"Cambio Del Arte" wrote:

> SQL 2000 was never installed, Sharepoint is definately using WMSDE. The
> version number you see was extracted from the WMSDE ERRORLOG file. I presume
> that this version number implies that it is the "WMSDE" version of SQL2000.
>
> "Mike Walsh" wrote:
>
> > Sorry that I didn't spot this before
> >
> > > db: WMSDE (installed with Sharepoint Microsoft SQL Server 2000 -
> > > 8.00.884)
> >
> > Does this mean that you already had SQL Server 2K installed on this server
> > and that when you installed WSS you selected the default install (which
> > installs WMSDE) ?
> >
> > I.e. that your WSS installation is using WMSDE as its database instance?
> >
> > Mike Walsh, Helsinki, Finland
> > WSS FAQ at http://wss.collutions.com
> > Please reply to the newsgroup
> >
> > "Cambio Del Arte" <parisit@nospam.nospam> wrote in message
> > news:FA6FA10C-F23C-475C-8CE5-FBE79BC6605E@microsoft.com...
> > > Problem:
> > >
> > > When connecting to Sharepoint website via web browser, following message
> > > is
> > > displayed: "Cannot connect to the configuration database."
> > >
> > > After a few weeks of running fine, all of a sudden the Sharepoint app is
> > > unable to connect to the WMSDE database, and there are no obvious
> > > indiciations as to the problem. The MSSQL$SHAREPOINT service starts up
> > > fine
> > > and no errors are logged in ERROLOG or NT event log, however it is
> > > impossible
> > > to connect to the database using the Sharepoint user or admin website,
> > > OSQL,
> > > or the sharepoint STSadmn tool.
> > >
> > > The only way that I have been able to temporarily resolve the problem is
> > > to:
> > > - uninstall Sharepoint
> > > - uninstall WMSDE
> > > - reinstall Sharepoint and WMSDE
> > > - restore the Sharepoint db using the command STSADM.EXE -o restore
> > >
> > > Everything then works fine again for a weeks util the same problem
> > > resurfaces. This is the 4th time that it has occurred
> > >
> > > The following Microsft KB articles did not resolve or were not relevant to
> > > the problem
> > >
> > > http://support.microsoft.com/?id=823287
> > > http://support.microsoft.com/default.aspx?kbid=833183
> > >
> > >
> > > Server Configuration:
> > >
> > > Cleanly installed server dedicated to running Sharepoint
> > >
> > > OS: Windows 2003 Server
> > > SP ver: Windows SharePoint Services with Service Pack 1 (SP1)
> > > db: WMSDE (installed with Sharepoint Microsoft SQL Server 2000 -
> > > 8.00.884)
> > > other installed software: Symantic A/V 10, NetVault backup agent
> > >
> > >
> >
> >
> >

v-wdxu
Sat Jul 30 04:46:55 CDT 2005

------=_NextPart_0001_20FAC185
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi,

There is one kb article introducing one possible cause for this.
883547 You receive an "Unable to connect to database" error message when you
http://support.microsoft.com/?id=883547

I'd suggset please troubleshoot this issue based on this article. If it
remains, please feel free to let me know.

My pleasure to be of any assistance!

Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.

------=_NextPart_0001_20FAC185
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\froman\fprq2\fcharset0 Georgia;}}
\viewkind4\uc1\pard\lang2052\f0\fs23 Hi,
\par
\par There is one kb article introducing one possible cause for this.
\par 883547 You receive an "Unable to connect to database" error message when you
\par http://support.microsoft.com/?id=883547
\par
\par I'd suggset please troubleshoot this issue based on this article. If it remains, please feel free to let me know.
\par
\par My pleasure to be of any assistance!
\par
\par Best Regards,
\par Wei-Dong XU
\par Microsoft Product Support Services
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par }
------=_NextPart_0001_20FAC185--

parisit
Mon Aug 01 03:57:02 CDT 2005

The MSSQL$SHAREPOINT service is configured to start using the Local system
Account (default setting). As per the SQL log file, the service starts
without incident and it remains running, yet I am unable to connect.

However, upon further inspection of this log file, I see that it is skipping
startup of "clean databases" and I do not see anywhere the startup of the
Sharepoint databases. Perhaps this is part of the problem?

---------------------
2005-08-01 10:48:18.38 server Microsoft SQL Server 2000 - 8.00.884
(Intel X86)
Nov 29 2003 20:52:47
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: Service Pack 1)

2005-08-01 10:48:18.38 server Copyright (C) 1988-2002 Microsoft
Corporation.
2005-08-01 10:48:18.38 server All rights reserved.
2005-08-01 10:48:18.38 server Server Process ID is 3044.
2005-08-01 10:48:18.38 server Logging SQL Server messages in file
'F:\wmsdedata\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
2005-08-01 10:48:18.40 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2005-08-01 10:48:18.46 server SQL Server configured for thread mode
processing.
2005-08-01 10:48:18.46 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-08-01 10:48:18.58 spid4 Starting up database 'master'.
2005-08-01 10:48:18.75 server Using 'SSNETLIB.DLL' version '8.0.880'.
2005-08-01 10:48:18.75 spid5 Starting up database 'model'.
2005-08-01 10:48:18.77 spid4 Server name is 'TW-FS01-PAR\SHAREPOINT'.
2005-08-01 10:48:18.77 spid4 Skipping startup of clean database id 4
2005-08-01 10:48:18.77 spid4 Skipping startup of clean database id 5
2005-08-01 10:48:18.77 spid4 Skipping startup of clean database id 6
2005-08-01 10:48:18.82 server SQL server listening on Shared Memory.
2005-08-01 10:48:18.82 server SQL Server is ready for client connections
2005-08-01 10:48:18.88 spid5 Clearing tempdb database.
2005-08-01 10:48:19.27 spid5 Starting up database 'tempdb'.
2005-08-01 10:48:19.36 spid4 Recovery complete.
2005-08-01 10:48:21.40 spid4 SQL global counter collection task is
created.
----------------------------


"Dave Bone" wrote:

> Hi,
>
> Could it be the account that WMSDE uses to start? In SQL Server if you use
> an account and the account password changes then you get connection errors.
>
> I have a SQL Server database on a test platform that uses my personal
> active directory account. We have to periodically change the password on our
> accounts and when I do if I do not change the password in SQL Server then it
> fails to start.
>
> Check in the services Log On properties for WMSDE to see which account it
> uses. It should probably use a Local System account
>
>
> Dave
>
> "Cambio Del Arte" wrote:
>
> > SQL 2000 was never installed, Sharepoint is definately using WMSDE. The
> > version number you see was extracted from the WMSDE ERRORLOG file. I presume
> > that this version number implies that it is the "WMSDE" version of SQL2000.
> >
> > "Mike Walsh" wrote:
> >
> > > Sorry that I didn't spot this before
> > >
> > > > db: WMSDE (installed with Sharepoint Microsoft SQL Server 2000 -
> > > > 8.00.884)
> > >
> > > Does this mean that you already had SQL Server 2K installed on this server
> > > and that when you installed WSS you selected the default install (which
> > > installs WMSDE) ?
> > >
> > > I.e. that your WSS installation is using WMSDE as its database instance?
> > >
> > > Mike Walsh, Helsinki, Finland
> > > WSS FAQ at http://wss.collutions.com
> > > Please reply to the newsgroup
> > >
> > > "Cambio Del Arte" <parisit@nospam.nospam> wrote in message
> > > news:FA6FA10C-F23C-475C-8CE5-FBE79BC6605E@microsoft.com...
> > > > Problem:
> > > >
> > > > When connecting to Sharepoint website via web browser, following message
> > > > is
> > > > displayed: "Cannot connect to the configuration database."
> > > >
> > > > After a few weeks of running fine, all of a sudden the Sharepoint app is
> > > > unable to connect to the WMSDE database, and there are no obvious
> > > > indiciations as to the problem. The MSSQL$SHAREPOINT service starts up
> > > > fine
> > > > and no errors are logged in ERROLOG or NT event log, however it is
> > > > impossible
> > > > to connect to the database using the Sharepoint user or admin website,
> > > > OSQL,
> > > > or the sharepoint STSadmn tool.
> > > >
> > > > The only way that I have been able to temporarily resolve the problem is
> > > > to:
> > > > - uninstall Sharepoint
> > > > - uninstall WMSDE
> > > > - reinstall Sharepoint and WMSDE
> > > > - restore the Sharepoint db using the command STSADM.EXE -o restore
> > > >
> > > > Everything then works fine again for a weeks util the same problem
> > > > resurfaces. This is the 4th time that it has occurred
> > > >
> > > > The following Microsft KB articles did not resolve or were not relevant to
> > > > the problem
> > > >
> > > > http://support.microsoft.com/?id=823287
> > > > http://support.microsoft.com/default.aspx?kbid=833183
> > > >
> > > >
> > > > Server Configuration:
> > > >
> > > > Cleanly installed server dedicated to running Sharepoint
> > > >
> > > > OS: Windows 2003 Server
> > > > SP ver: Windows SharePoint Services with Service Pack 1 (SP1)
> > > > db: WMSDE (installed with Sharepoint Microsoft SQL Server 2000 -
> > > > 8.00.884)
> > > > other installed software: Symantic A/V 10, NetVault backup agent
> > > >
> > > >
> > >
> > >
> > >

parisit
Mon Aug 01 03:58:06 CDT 2005

This article was not relevant to the problem. The server was cleanly
installed with Windows server 2003. There version of the Oledb32.dll file is
2.82.1830.0

Thanks for your feedback.

"Wei-Dong XU [MSFT]" wrote:

> Hi,
>
> There is one kb article introducing one possible cause for this.
> 883547 You receive an "Unable to connect to database" error message when you
> http://support.microsoft.com/?id=883547
>
> I'd suggset please troubleshoot this issue based on this article. If it
> remains, please feel free to let me know.
>
> My pleasure to be of any assistance!
>
> Best Regards,
> Wei-Dong XU
> Microsoft Product Support Services
> This posting is provided "AS IS" with no warranties, and confers no rights

v-wdxu
Mon Aug 01 22:19:06 CDT 2005

------=_NextPart_0001_2F0AE60E
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi,

Since many causes may result in this odd behaivor, now it is very hard for
us on the troubleshooting. I have one suggestoin that you could install the
SQL serfver clienet tools in your WSS box. Then we could use this to manage
MSDE. Then when the error occurs, it will be easy for us to troubleshoot
the database. For WSS is running very well now, we could research this when
the next issue occured with the assistance of SQL server client tools.

Please feel free to let me know if any question. It is my pleasure to be of
any assistance.

Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.

------=_NextPart_0001_2F0AE60E
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\froman\fprq2\fcharset0 Georgia;}}
\viewkind4\uc1\pard\lang2052\f0\fs23 Hi,
\par
\par Since many causes may result in this odd behaivor, now it is very hard for us on the troubleshooting. I have one suggestoin that you could install the SQL serfver clienet tools in your WSS box. Then we could use this to manage MSDE. Then when the error occurs, it will be easy for us to troubleshoot the database. For WSS is running very well now, we could research this when the next issue occured with the assistance of SQL server client tools.
\par
\par Please feel free to let me know if any question. It is my pleasure to be of any assistance.
\par
\par Best Regards,
\par Wei-Dong XU
\par Microsoft Product Support Services
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par }
------=_NextPart_0001_2F0AE60E--

parisit
Tue Aug 02 03:10:02 CDT 2005

I have already tried this option with negative results.

With the SQL client tools installed I am still unable to connect to the
server "MSSQL$SHAREPOINT" using either the Enterprise Manager or the query
analyzer.

The current state of the system is that WMSDE is running but I am unable to
connect.

"Wei-Dong XU [MSFT]" wrote:

> Hi,
>
> Since many causes may result in this odd behaivor, now it is very hard for
> us on the troubleshooting. I have one suggestoin that you could install the
> SQL serfver clienet tools in your WSS box. Then we could use this to manage
> MSDE. Then when the error occurs, it will be easy for us to troubleshoot
> the database. For WSS is running very well now, we could research this when
> the next issue occured with the assistance of SQL server client tools.
>
> Please feel free to let me know if any question. It is my pleasure to be of
> any assistance.
>
> Best Regards,
> Wei-Dong XU
> Microsoft Product Support Services
> This posting is provided "AS IS" with no warranties, and confers no rights

v-wdxu
Tue Aug 02 21:53:44 CDT 2005

------=_NextPart_0001_341A1011
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi,

This appears to be one SQL issue. If we uses the SQL client tools at the
WSS server, it should work very well with the WMSDE as the same to MS SQL
Server. So I'd suggest you could post this issue at SQL newsgroup. After
the resolution on this problem, let's focus on the sharepoint side if it
remains. The SQL clients newsgroup is at:
http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.publi
c.sqlserver.clients&lang=en&cr=US

It is my pleasure to be of any assistance.

Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.

------=_NextPart_0001_341A1011
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\froman\fprq2\fcharset0 Georgia;}}
\viewkind4\uc1\pard\lang2052\f0\fs23 Hi,
\par
\par This appears to be one SQL issue. If we uses the SQL client tools at the WSS server, it should work very well with the WMSDE as the same to MS SQL Server. So I'd suggest you could post this issue at SQL newsgroup. After the resolution on this problem, let's focus on the sharepoint side if it remains. The SQL clients newsgroup is at:
\par http://msdn.microsoft.com/newsgroups/managed/default.aspx?dg=microsoft.public.sqlserver.clients&lang=en&cr=US
\par
\par It is my pleasure to be of any assistance.
\par
\par Best Regards,
\par Wei-Dong XU
\par Microsoft Product Support Services
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par }
------=_NextPart_0001_341A1011--

parisit
Wed Aug 10 07:58:43 CDT 2005

Problem Solved:

"Enable Shared Memory Protocol" in SQL Server Client Network Utility must be
checked.

Normally, this should be enabled by default

"Cambio Del Arte" wrote:

> Problem:
>
> When connecting to Sharepoint website via web browser, following message is
> displayed: "Cannot connect to the configuration database."
>
> After a few weeks of running fine, all of a sudden the Sharepoint app is
> unable to connect to the WMSDE database, and there are no obvious
> indiciations as to the problem. The MSSQL$SHAREPOINT service starts up fine
> and no errors are logged in ERROLOG or NT event log, however it is impossible
> to connect to the database using the Sharepoint user or admin website, OSQL,
> or the sharepoint STSadmn tool.
>
> The only way that I have been able to temporarily resolve the problem is to:
> - uninstall Sharepoint
> - uninstall WMSDE
> - reinstall Sharepoint and WMSDE
> - restore the Sharepoint db using the command STSADM.EXE -o restore
>
> Everything then works fine again for a weeks util the same problem
> resurfaces. This is the 4th time that it has occurred
>
> The following Microsft KB articles did not resolve or were not relevant to
> the problem
>
> http://support.microsoft.com/?id=823287
> http://support.microsoft.com/default.aspx?kbid=833183
>
>
> Server Configuration:
>
> Cleanly installed server dedicated to running Sharepoint
>
> OS: Windows 2003 Server
> SP ver: Windows SharePoint Services with Service Pack 1 (SP1)
> db: WMSDE (installed with Sharepoint Microsoft SQL Server 2000 - 8.00.884)
> other installed software: Symantic A/V 10, NetVault backup agent
>
>

v-wdxu
Wed Aug 10 21:14:43 CDT 2005

------=_NextPart_0001_03EFB8CE
Content-Type: text/plain
Content-Transfer-Encoding: 7bit


Splendid! Very great news! Thanks for sharing this to the community! :-)

Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.
It is my pleasure to be of assistance.
------=_NextPart_0001_03EFB8CE
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\froman\fprq2\fcharset0 Georgia;}}
\viewkind4\uc1\pard\lang2052\f0\fs23
\par Splendid! Very great news! Thanks for sharing this to the community! :-)
\par
\par Best Regards,
\par Wei-Dong XU
\par Microsoft Product Support Services
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par It is my pleasure to be of assistance.
\par }
------=_NextPart_0001_03EFB8CE--