In the past 2 weeks I have seen the error below pop up on multiple client farms. Everything from 5 server farms to single server installs. In all of them, they have been running fine for a long time. All of them are MOSS SP1 w/o the infrastructure update (it is not an option to put that update on at this time for most of them). At this point we have not noticed any functionality that is not working on the farms. That does not mean there isn't anything broken, it just means we have not seen anything. In multi-server farms it happens at regular intervals (usually 5 minutes) but at different times on each box on the farm. It would suggest there was a scheduled job that was having issues. I have double checked all the service accounts and permissions, all are where they should be. I have restarted most MOSS services without issue or any impact on the box. I have restarted the boxes. I have not managed to get past this issue on any farms aflicted. I have searched on multiple folks seeing this type of issue. Of those with fixes, none seemed to apply to this. Also, to date I have only seen it on 32 bit systems. Error description: Event Type: ErrorEvent Source: Windows SharePoint Services 3Event Category: General Event ID: 27745Date: 9/9/2008Time: 7:42:29 AMUser: N/AComputer: A7XXXXXHPT001Description: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 XXXXXX_Config on A7XXXXXHPT001. Check the database connection information and make sure that the database server is running..

Hi, This may be a service account issue, please try to this workaround: Reset the farm credentials by using the KB934838: http://support.microsoft.com/kb/934838 Hope it helps.Xue-Mei Chang

That did not fix it. I did go through a set of steps running Netstop netstart on just about every MOSS Service on the box. For the time being this has solved it. However, having to restart services and reset service accounts on a regular basis is not doing much for keeping my clients convinces MOSS or Microsoft is the solution they want for their enterprise. There are enough posts here and across the web that MS needs to be addressing this with a patch and not a "reboot/reset and wait for it to happen again" approach. I do not mean to sound harsh but MOSS can easily lose the market share it has established from issues like these and MS management needs to recognize this and spend the money to have their people research and fix these.

I've just been troubleshooting this on a farm.It appears to be related to the SharePoint Timer service; restarting that has cleared it for me.http://mossytips.blogspot.com/2008/09/event-id-64827076639827745.htmlmay provide some useful background.

Kindly Check the database SharePoint_Config log file for size, Try to truncate this and then ran a Windows Sharepoint Timer Service restart for it.Regards,Sandeep Lad

yeah the sptimer restart does help but it will reoccur. I really do not mean to be a P*ick on it but for my clients sake, when they have spent a quarter million dollars on licensing and such for an enterprise product, having it be so high maintenance and fill up event logs and ULS logs with errors listed as critical, is really unacceptable. This is a long running issue with MOSS. Having this clutter in the logs complicates their ability to effectively maintain the farm and determine overall farm health. It would be realy good if the MOSS product team would find a fix for this and throw it in a CU.

Thanks Peter. Resetting the timer service did the trick.Phil Shisbey