none
'cannot connect to configuration database' after microsoft update

    Question

  • Stole this from a post on a different message board, but we're having the same problems and cannot figure it out!  Any help would be greatly appreciated.  This has nothing to do with similar issues people have had with this patch and zone alarm...we have internet connectivity and all that good stuff.  It just seemed to mess up the permissions with WMSDE or something like that.
    Thanks,
    Robert

    ___________________________________________________________________________________________________

    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?
    Friday, July 11, 2008 2:00 PM

Answers

  • Hi Gavilan,

    The steps are exactly what nayrbrey said. Restoring the system to the state before the problem happened is a good resolution.

     

    For supgraffix’s issue, based on the post, the errors are thrown repeatedly and there is an authorization problem in the configuration database.

    I diagnosed that the issue happens in the Central Administration application pool account and the SharePoint Timer Service is not working properly.

    There are both WSS 2.0 and WSS 3.0 error logs in your post. I suppose WSS 2.0 is the cause of your issue based on the database name.

    To resolve the problem, you can do the following steps:

    1. Browse to the SharePoint Central Administration page.

    2. Under Server Configuration, click Configure Virtual Server for Central Administration.

    3. Select Use an Existing Application Pool.

    4. Select the application pool that the central administration virtual server is running under.

    5. Click OK.

    6. Run an IISReset.

    7. Restart the SharePoint Timer Service.

     

    Hope the information can be helpful and let me know the result if possible.

    -lambert

    Tuesday, July 15, 2008 9:47 AM
  • Have you tried to re-run the configuration wizard?  It will create a new content DB but you will be able to add the previous one via Centeral Administration --> under Operations.

     

    I would back the WSS_Conent DBs first.

     

    If you did a basic or stand alone install then you are using the Windows Internal DB or SSEE (Sql Server Express Embedded).  You can make a copy of these files by going to there location on the drive ...

     

    C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data

     

    You will have to turn off the SSEE service first.

    Wednesday, July 16, 2008 11:01 PM

All replies

  • We had the same issue at one of our clients, we basically had them remove the update (reboot) restore the DB back to before the patch was applied.  They were using the WMSDE but not at the SP4 level, so the cause is on the DB side, but after trolling the boards like yourself, no word if there is a MS fix yet.

     

    Friday, July 11, 2008 5:31 PM
  •  

    I'm having this exact issue.  I just need to confirm your solution:

     

    1. Rollback update KB951748

    2. Restore DB from a backup from before the patch.

    3. Reboot.

     

    Is this correct?

    Monday, July 14, 2008 6:01 PM
  • Hi Gavilan,

    The steps are exactly what nayrbrey said. Restoring the system to the state before the problem happened is a good resolution.

     

    For supgraffix’s issue, based on the post, the errors are thrown repeatedly and there is an authorization problem in the configuration database.

    I diagnosed that the issue happens in the Central Administration application pool account and the SharePoint Timer Service is not working properly.

    There are both WSS 2.0 and WSS 3.0 error logs in your post. I suppose WSS 2.0 is the cause of your issue based on the database name.

    To resolve the problem, you can do the following steps:

    1. Browse to the SharePoint Central Administration page.

    2. Under Server Configuration, click Configure Virtual Server for Central Administration.

    3. Select Use an Existing Application Pool.

    4. Select the application pool that the central administration virtual server is running under.

    5. Click OK.

    6. Run an IISReset.

    7. Restart the SharePoint Timer Service.

     

    Hope the information can be helpful and let me know the result if possible.

    -lambert

    Tuesday, July 15, 2008 9:47 AM
  • I am encountering the exact same issue, a virtual server has this problem after upgrading with the same Windows Update. When returning to a previous state it is fine. Is there any information from Microsoft about a solution to fix this? It cannot be the case I have to disable the updating on that server for WSS to work?
    Wednesday, July 16, 2008 6:15 AM
  •  

    Do you have any suggestions if the Central Administration site is returning the same "cannot content to contenct database" error? This is running on virtual server as well.

     

    Wednesday, July 16, 2008 6:47 PM
  • Have you tried to re-run the configuration wizard?  It will create a new content DB but you will be able to add the previous one via Centeral Administration --> under Operations.

     

    I would back the WSS_Conent DBs first.

     

    If you did a basic or stand alone install then you are using the Windows Internal DB or SSEE (Sql Server Express Embedded).  You can make a copy of these files by going to there location on the drive ...

     

    C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data

     

    You will have to turn off the SSEE service first.

    Wednesday, July 16, 2008 11:01 PM
  • After a while I found a better solution for this problem.

    This errormessage seems to appear when you have your Sharepoint Configuration and Content Databases in a different directory then the default installation.

    After installing the infamous Windows Update the directory containing the mdf and ldf files has different security properties. All priviliges are removed except for Administrators. Add SQLServer2005MSSQLUser$[ServerName]$SSEE user with full access and it will work again.

    Finally I am able to update the server...

    Rody van Sambeek

    www.weasy.nl
    Wednesday, August 06, 2008 2:00 PM
  • The solution posted by Rody is what did the trick for me.  I had noticed that the NTFS permissions were altered to only be the Administrators group, yet SharePoint was using the Network Service account to access the databases.  I verified the configuration on a server that had not been patched, and simply granted the Network Service full permission to the Data folder (making sure that the permissions were replaced on the mdf and ldf files in the folder).

    Thanks for the post!
    Friday, August 15, 2008 6:27 PM
  • Yes, changing the permissions on both the directory and the files to include Network Service with full rights did the trick.  You have to do both, though.  Just changing permissions on the directory does not work.
    Friday, February 27, 2009 4:18 AM
  • Finally I resolved this problem.
    I tried several solutions like restarting
    sql services, resetting IIS, changing service accounts, checking account
    permissions…etc before, but faild.

    For most of cases, the problem was Account Permissions.
    I’m not sure it
    would work for your casees… but If you get “Cannot connect to the configuration
    database” after windows update or hotfix, try these:

    1. Navigate to IIS management -> Select SharePoint sites -> Right click
    and Edit Permissions -> Add WSS_ADMIN_WPG group with full control, add
    WSS_WPG group for each sites.

    2. Navigate to ADSI management -> Select Action -> Connect -> Select
    Domain name -> Select CN=System -> Right click and make new “Container”
    -> Fill the value with “Microsoft SharePoint Products”

    3. Select the container you just made(CN=Microsoft SharePoint Products) ->
    Right click and open the property, Security tab -> Add Sharepoint System
    account(The account you set as farm admin account) -> Advanced settings ->
    Select Sharepoint System account you just added and make sure you allowed on
    “serviceConnectionPoint object creation” (or you just add the Sharepoint System
    account to the Built-in Administrator Account Group to skip step 3)

    4. Run SharePoint Configuration Wizard to restore your SP server.

    hope this helps.

    • Proposed as answer by MechaniCat Tuesday, November 06, 2012 7:08 AM
    • Unproposed as answer by MechaniCat Tuesday, November 06, 2012 7:09 AM
    • Proposed as answer by MechaniCat Tuesday, November 06, 2012 7:09 AM
    Wednesday, August 29, 2012 11:30 AM