...swimming in OWSTIMER.EXE error messages....

I am getting the below message that is being logged many times every 10 seconds. I have tried to find a solution for it but cannot find any. I noticed that the log files are consuming 2gb every 4 days. And I need to delete them because I have only 2gb of space on C: drive. I am getting the same message in the path called "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS". All other things seems to be working fine, except the issue with log files eating all the free space. I am using a SBS 2003 with all SP patches and WSUS 3 and Sharepoint 3. Below is the message:

OWSTIMER.EXE (0x0DE8) 0x0E30
Windows SharePoint Services Timer 5uuf
Monitorable The previous instance of the timer job 'Config Refresh', id '{975F79C9-1B0D-4D14-BD60-C531FF142500}' for service '{6C881CF7-F11F-457B-A757-68862E0059E6}' is still running, so the current instance will be skipped. Consider increasing the interval between jobs.

Have you tried to install Sharepoint 3 side by side with WSS 2 per the document on the SBS website?

Yes, you are right, Sharepoint is installed side by side as per the documentation, I forgot to state that out. Also, I have stopped the original WSS2 site from within IIS, just to stop users from using it by mistake. There doesnt seem to appear to be any related errors in the Event log.

What is the event id number that you are getting?

The EventID from the logfile is "5uuf". Check the below in details:

Timestamp
08/13/2007 20:20:44.98

Process
OWSTIMER.EXE (0x0DE8)

TID
0x0E30

Area
Windows SharePoint Services

Category
Timer

EventID
5uuf

Level
Monitorable

Message
The previous instance of the timer job 'Config Refresh', id '{975F79C9-1B0D-4D14-BD60-C531FF142500}' for service '{6C881CF7-F11F-457B-A757-68862E0059E6}' is still running, so the current instance will be skipped. Consider increasing the interval between jobs.

I am facing the same issue.

Making the settings for the timer entntries not been logged in the log files is fine.

But is the event which is causing this entry affecting the server performance?

Can we dig to the reason of these entries and whether they mean something is wrong with the timer/server and whether we need to fix that issue so that no such entries created at all.

If anyone really knows the cause, please explain the same here.