WSS 3 - Cannot connect to the configuration database after KB95174 - Sharepoint

Oh, forgot one bit of information. In addition to the errors in the
Application log, there is an error in the System log as well that started at
the same time

====================================================
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 7/9/2008
Time: 6:51:48 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: SRV
Description:
The application-specific permission settings do not grant Local Activation
permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
permission can be modified using the Component Services administrative tool.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
====================================================

"Tom" wrote:

> All of a sudden last night at 3:03AM EST the Application log on my server
> hosting WSS3 starting throwing lots of errors. The three repeating errors
> are:
>
> =====================================================
> Event Type: Error
> Event Source: Windows SharePoint Services 2.0
> Event Category: None
> Event ID: 1000
> Date: 7/9/2008
> Time: 6:40:39 PM
> User: N/A
> Computer: SRV
> Description:
> #50070: Unable to connect to the database STS_Config on RV \MICROSOFT##SSEE.
> Check the database connection information and make sure that the database
> server is running.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> =====================================================
>
> =====================================================
>
> Event Type: Error
> Event Source: Windows SharePoint Services 3
> Event Category: Database
> Event ID: 3760
> Date: 7/9/2008
> Time: 6:40:07 PM
> User: N/A
> Computer: SRV
> Description:
> SQL Database 'STS_Config' on SQL Server instance
> 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error
> information from SQL Server is included below.
>
> Cannot open database "STS_Config" requested by the login. The login failed.
> Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> =====================================================
>
> =====================================================
> Event Type: Failure Audit
> Event Source: MSSQL$MICROSOFT##SSEE
> Event Category: (4)
> Event ID: 18456
> Date: 7/9/2008
> Time: 6:40:07 PM
> User: NT AUTHORITY\NETWORK SERVICE
> Computer: SRV
> Description:
> The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE )
> 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:
> NT AUTHORITY\NETWORK SERVICE, [CLIENT: <named pipe>].
> Data:
> 0000: 18 48 00 00 0e 00 00 00 .H......
> 0008: 17 00 00 00 4e 00 43 00 ....N.C.
> 0010: 44 00 4d 00 56 00 31 00 D.M.V.1.
> 0018: 5c 00 4d 00 49 00 43 00 \.M.I.C.
> 0020: 52 00 4f 00 53 00 4f 00 R.O.S.O.
> 0028: 46 00 54 00 23 00 23 00 F.T.#.#.
> 0030: 53 00 53 00 45 00 45 00 S.S.E.E.
> 0038: 00 00 07 00 00 00 6d 00 ......m.
> 0040: 61 00 73 00 74 00 65 00 a.s.t.e.
> 0048: 72 00 00 00 r...
> =====================================================
>
> The server and WSS3 had been up and operational since I installed several
> weeks ago. No problems reported.
>
> After these errors started to appear out all of a sudden I started to check
> the system for changes. The only change from the prior day was the
> installation of update KB951748.
>
> Searching the web I came across a post that someone using SBS2003 had major
> connectivity issues after installing the update as well as thier WSS site not
> being giving the message "Cannot connect to the configuration database",
> which my in a well.
>
> So... anyone else experiencing this issue, or maybe have some advice?
>

I am having the exact same issue since July 9th. Would appreciate any feedback. This is urgent as our users are unable to access any data for over 4 days now on the WSS3.0 portal.

Dear Tom,

We have the same problem over here.
Also after update KB951748.

Did you resolve the problem?
Could you help us?

Kind regards,

Pieter

"Tom" wrote:

> Oh, forgot one bit of information. In addition to the errors in the
> Application log, there is an error in the System log as well that started at
> the same time
>
> ====================================================
> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10016
> Date: 7/9/2008
> Time: 6:51:48 PM
> User: NT AUTHORITY\NETWORK SERVICE
> Computer: SRV
> Description:
> The application-specific permission settings do not grant Local Activation
> permission for the COM Server application with CLSID
> {61738644-F196-11D0-9953-00C04FD919C1}
> to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
> permission can be modified using the Component Services administrative tool.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ====================================================
>
> "Tom" wrote:
>
> > All of a sudden last night at 3:03AM EST the Application log on my server
> > hosting WSS3 starting throwing lots of errors. The three repeating errors
> > are:
> >
> > =====================================================
> > Event Type: Error
> > Event Source: Windows SharePoint Services 2.0
> > Event Category: None
> > Event ID: 1000
> > Date: 7/9/2008
> > Time: 6:40:39 PM
> > User: N/A
> > Computer: SRV
> > Description:
> > #50070: Unable to connect to the database STS_Config on RV \MICROSOFT##SSEE.
> > Check the database connection information and make sure that the database
> > server is running.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > =====================================================
> >
> > =====================================================
> >
> > Event Type: Error
> > Event Source: Windows SharePoint Services 3
> > Event Category: Database
> > Event ID: 3760
> > Date: 7/9/2008
> > Time: 6:40:07 PM
> > User: N/A
> > Computer: SRV
> > Description:
> > SQL Database 'STS_Config' on SQL Server instance
> > 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error
> > information from SQL Server is included below.
> >
> > Cannot open database "STS_Config" requested by the login. The login failed.
> > Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> > =====================================================
> >
> > =====================================================
> > Event Type: Failure Audit
> > Event Source: MSSQL$MICROSOFT##SSEE
> > Event Category: (4)
> > Event ID: 18456
> > Date: 7/9/2008
> > Time: 6:40:07 PM
> > User: NT AUTHORITY\NETWORK SERVICE
> > Computer: SRV
> > Description:
> > The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE )
> > 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:
> > NT AUTHORITY\NETWORK SERVICE, [CLIENT: <named pipe>].
> > Data:
> > 0000: 18 48 00 00 0e 00 00 00 .H......
> > 0008: 17 00 00 00 4e 00 43 00 ....N.C.
> > 0010: 44 00 4d 00 56 00 31 00 D.M.V.1.
> > 0018: 5c 00 4d 00 49 00 43 00 \.M.I.C.
> > 0020: 52 00 4f 00 53 00 4f 00 R.O.S.O.
> > 0028: 46 00 54 00 23 00 23 00 F.T.#.#.
> > 0030: 53 00 53 00 45 00 45 00 S.S.E.E.
> > 0038: 00 00 07 00 00 00 6d 00 ......m.
> > 0040: 61 00 73 00 74 00 65 00 a.s.t.e.
> > 0048: 72 00 00 00 r...
> > =====================================================
> >
> > The server and WSS3 had been up and operational since I installed several
> > weeks ago. No problems reported.
> >
> > After these errors started to appear out all of a sudden I started to check
> > the system for changes. The only change from the prior day was the
> > installation of update KB951748.
> >
> > Searching the web I came across a post that someone using SBS2003 had major
> > connectivity issues after installing the update as well as thier WSS site not
> > being giving the message "Cannot connect to the configuration database",
> > which my in a well.
> >
> > So... anyone else experiencing this issue, or maybe have some advice?
> >

Hello, we appear to be having the exact same problem. Have either of
you been able to get past this? Please advise if so.

Thanks
Brent

Unfortunately, more often than not, this means having to back-up the content
database, re-installing WSS 3.0, then restoring the content database and
adding it to a new web application.

--
Hope this helps!
Only my 2 cents! Not authoritative and comes with no warranty or guarantee
of useability, correctness or accuracy!
<brent.lowe@gmail.com> wrote in message
news:97f1bd81-7b6a-4b4d-8a77-18e76a1dd5ad@y38g2000hsy.googlegroups.com...
> Hello, we appear to be having the exact same problem. Have either of
> you been able to get past this? Please advise if so.
>
> Thanks
> Brent