Every 5 seconds an error (connection SharePoint) in Event Viewer

[BE.FDU]

I have something strange in the Event Viewer on my MS Project Server. Every 5
seconds I have an error coming from the source Windows SharePoint Server:

Source: Windows SharePoint Server
Description: #50070 (the error is in Dutch b'cause it's a Dutch installation
of MS Project server): cannot connect database WSSConfigDB on servername.
Check the database connection and check if the database server is active.

I restarted the server, but the error keeps coming every 5 seconds. The
database is running (MS Project runs on the same machine).
How can I get rid of this annoying error. It is also very strange, in the
Project Web Access I see no problems. Everything works.

 

[Assaf]

Hi,
In case you're sure that the server is up and you can successfully connect
to it, I can recomment viewing the sharepoint server log files and see if
there's any trace of problematic process there.
The log is located at ...Program Files\Common Files\Microsoft Shared\Web
Server Extensions\12\LOGS

 

[BE.FDU]

I don't have this directory. In the "web server extensions" folder, only the
subfolders "50", "60" and "wpresources" are available. When I look closer in
these folders, I cannot find a LOGS-dir.

(it's a Windows 2003 server with Project Server 2003)

 

[Assaf]

Back from a weekend vacation, sorry for the delayed answer

I thought you were using server 2007, so indeed the log files is not a
possibility.

Maybe one of these resources could assist:
http://blogs.msdn.com/cgideon/archive/2006/05/24/605454.aspx
http://forums.msrportal.com/archive/index.php?t-625.html

Another option, depends on how much you want to get rid of the messages,
could be creating a new config db, but it can be going to far for this
problem.

 

[BE.FDU]

I've tried the 3 suggestions, but still every 5 seconds an error.

Everything seems working, but I don't have any idea of the impact of this
error every 5 seconds.

 

[Assaf]

Did you check the sharepoint timer service - it might be related to it.
Try stopping him and see if the errors still occur, we will continue from
this point

 

[BE.FDU]

I've redid suggestion 2, and the errors doesn't occur anymore.


Suggestion 2:
==============
Ensure that the SharePoint Configuration Database, the Admin apppool, and
the SharePoint Timer Service are all running under the same context.

a. Browse SharePoint Central Admin
b. Under Server Configuration, Click Configure Virtual Server for Central
Administration
c. Select Use an Existing Application Pool
d. Select the application pool that the admin vserver is running under
e. Click OK
f. Run IISReset
g. Restart the SharePoint Timer Service (use the Services MMC or use Net
Stop/Start on sptimer)

 

[Assaf]

I guess these are good news
Glad we could provide an assistance.