in

SharePoint Blogs

The Best Place for SharePoint-related Blogs

This Blog

Syndication

ChadClarkesMOSSBlog

Unable to connect to database. -- *Solved

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 pfc-penndb-tst. Check the database connection information and make sure that the database server is running..

 I keep getting this error in my error logs for our Test/Staging Portal.  I'm unsure where its coming from.  Any ideas?

--------------------------------------------------------------

This issue was a component service.  So go into Component Services and drill down to DCOM, then there was a OSearch service there that needed our service account SPSWorker added with launch and activate priviledges. 

 Another fun Debug!

 Someone else's fix for this issue:

I don't know exactly what fixed it, but somewhere along the way:
* reset farm credentials (just the stsadm -o updatefarmcredentials; not the rest) as described in http://support.microsoft.com/kb/934838 - this involved IISReset's on every server in  the farm
* bumped timer job
* bumped administrative service job on the index server (probably should bump those jobs on the other servers as well)"

 

Comments

 

Russell said:

Did you install SP1 and/or have you checked your log file sizes recently?

January 15, 2008 11:46 AM
 

wwwpalyer said:

Can you explain what spsworker account is. I can' find it

January 21, 2008 10:29 AM
 

ChadClarke said:

SPSWorker was an account we created for least priviledges.  In this case it is the account selected for all site app pool.  Except Central admin, which uses spsadmin.

January 28, 2008 1:38 PM
 

Todd said:

I'm running into the same problem.  I added our service account to the OSearch services and granted it Local Launch, Local Activation, and  Local Access permissions, but I'm still getting the same error.  Any ideas about what else I should be looking at?

April 15, 2008 8:57 AM
 

ChadClarke said:

Make sure the app pool account for your site collection has the proper access to your databases.

April 15, 2008 1:14 PM

Leave a Comment

(required )  
(optional )
(required )  
Add

Need SharePoint Training? Attend a SharePoint Bootcamp!

Posts (c) their respective authors. Everything else (c) 2007 SharePoint Experts