SharePoint - Error Event ID 27745

Asked By salim

22-Aug-07 02:54 PM

Since the last couple of days, i have been recieving an error in my
event log at around the same time every day. This is a multi server
farm. The error is as follows

Event Type:	Error
Event Source:	Windows SharePoint Services 3
Event Category:	General
Event ID:	                27745
Date:		8/22/2007
Time:		12:10:32 AM
User:		N/A
Computer:	xxxxxxx
Description:
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 WSS_Content on <our sql server>.
Check the database connection information and make sure that the
database server is running..

Has anyone had experience with this before ? The site seems to be
running ok, but the recurrence of the error every day is bothering
me.

Any help will be appreciated.

Thanks

22-Aug-07 03:09 PM

Hi Salim,

This might not be what you are asking me, but the event description seems to
be missing. This is caused by the event log being archived and then opened
on a machine that does not have WSS installed. If you could cut and paste
the event form the source machine, obfuscating security-sensitive fields,
then we could have a better shot at helping you.

However, it looks like WSS is trying to index your content, but cannot find,
or cannot connect to, the content DB. Have you done any of the following
recently:

1. moved the content DB
2. renamed the content DB
3. changed passwords for WSS services accounts
4. did a backup and restore

--
James R. Morey [MS]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Office SharePoint Server 2007
(http://technet2.microsoft.com/Office/en-us/library/21dcf8aa-8a6e-4325-aa17-0188e491361c1033.mspx)

Windows SharePoint Services 3.0
(http://technet2.microsoft.com/windowsserver/WSS/en/library/8a9690e4-6917-4aab-82ce-cdbe989a20531033.mspx
)

========================

22-Aug-07 04:17 PM

Thanks for your reply James,
The machine I am copying this from has MOSS running on it and this was
all in the event viewer. I believe this

Description:
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 WSS_Content on <our sql server>.
Check the database connection information and make sure that the
database server is running..

.. is the event desciption. If I am mistaken please let me know.
In reply to your other points, I have not changed or renamed the
content database nor has the service account password been changed. I
am backing up the site (this is a publishing site for our client)
every day using the stsadm command in a script that runs on a
schedule.

Thanks Again
Salim

09-Oct-07 07:55 AM

Hey Salim,

hopefully u still watch this topic.

Have u been able to fix this error? If so how did u manage to get rid
of it ?

we get exactly the same errormessage approximately 15 x per minute

Our DB Server is up and running the ServicesUser didn't changed a
password and communication is between Moss2007 server and DB is also
fine.

any help very much appreciated

we need to fix this error asap

thx in advance and br

29-Oct-07 04:06 PM

I am getting a ton of these errors as well, with my own db names of course.

I have been searching and I find this error posted all over the internet
forums, and yet in every case there is not a solution!  Just questions....

Is there any update from Microsoft about this?
Or do we need to open a case?

Thanks!
~Clint

29-Oct-07 04:09 PM

I am getting TONS of these errors in a Medium Farm as well.  Same numbers,
same details, different dbs of course.

I have been searching the internet for updated information and in every case
there is not a solution, only questions.

Is there any update from MS on this error?
Or do we need to open a case with MS support?

Thanks!
~ Clint

13-Nov-07 09:58 AM

Hi,
I have the same problem with SharePoint Services 3.0. I receive 2
error messages every 10-15 days. But SPS ist working fine without any
errors or problems at all!

Have you found any solutions yet?

Thanks
Gunnar

13-Nov-07 10:22 AM

No.  It sure acts like a memory leak.

Rebooting all of the non-sql servers in the farm fixes it for a while, but
then after a week or two, it's back.  So, I guess the fix for now is "Reboot"
Surprised?  I sure hope they do something about it in SP1.

But I'm still amazed at how common this problem is and the lack of
information about it.  I may have to burn a support ticket and I will try to
post what I learn.

~Clint

05-Dec-07 04:46 AM

Have you checked your services?

Try restarting all of the following services:

Distributed Transaction Coordinator (MSDTC)
Windows SharePoint services Administration
Windows SharePoint Services Search
Windows SharePoint Services Timer
Windows SharePoint Services Tracing

If the accounts will not restart, try editing the password for the
account listed in the Log On tab of the service, setting it to the
password for that account.