SharePoint User Group UK

Share the knowledge!

Welcome to SharePoint User Group UK Sign in | Join | Help
in
Home Blogs Forums Photos Files Roller

#50070: Unable to connect to the database SPS01_Config_db

Last post 04-07-2008, 8:50 AM by GrahamBennett. 2 replies.
Sort Posts: Previous Next
  •  04-04-2008, 10:58 AM 9549

    #50070: Unable to connect to the database SPS01_Config_db

    Hi,

    New to this forum and not 100% with Sharepoint but learning and enjoying it!!!!

    Just wondered if anyone has an idea on what this problem is:

    Event ID is 1000 and the source is Windows SharePoint Services 2.0.

    Descr:
    #50070: Unable to connect to the database SPS01_Config_db on <ServerName>. Check the database connection information and make sure that the database server is running.

    Users can connect and perform browsing etc ok but the event log is littered with this entry every 20seconds.

    Am really confused as the SQL database is up and running, permissions appear to be ok and there are no other issues, I have tried the MS fixes 1. Adding a reg key into the SPTimer. 2. Setting the application pool settings to an exitsting pool.

    Thanks for any advice.

  •  04-04-2008, 12:54 PM 9556 in reply to 9549

    Re: #50070: Unable to connect to the database SPS01_Config_db

    Take a look at this article and see if it applies :) http://support.microsoft.com/?kbid=900498&FR=1

    You may also see this if the
    Sharepoint Timer Service is not running under the same account as the WSS Admin App Pool and also check the version of Oledb32.dll file on the computer is 2.8 or a later, installing MDAC 2.8 does not alway fix this, so you may have to manually update the dll.

    Hope these help


    Andrew Carter
    .Net & SharePoint
  •  04-07-2008, 8:50 AM 9585 in reply to 9556

    Re: #50070: Unable to connect to the database SPS01_Config_db

    Thanks Andrew,

    I have checked your suggestions, the Oledb32.dll is at 2.82. and if I understand your point about the Application pool/timer service it has an identity using a different account. I have checked the timer service on the indexing server as well as the web server and they are both setup the same.

    I did test the KB article in our pre production environment but not on all servers so will revisit this.

     

    Thanks for your help.

View as RSS news feed in XML
Powered by Community Server, by Telligent Systems