I am having an odd andvery frustratingproblem that just startedshowing uptwo days ago.I am starting to receive log files in my MOSS 2007 server:10/23/2008 14:33:08.99 OWSTIMER.EXE (0x1E60) 0x1570Windows SharePoint Services Timer 5uufMonitorableThe previous instance of the timer job 'Application Server Timer Job', id '{C455141D-FE86-49BB-88CC-9691AC63AF39}' for service '{5C4ADEDE-0FC5-47ED-8DA7-8BF3DD989A5D}' is still running, so the current instance will be skipped. Consider increasing the interval between jobs. these errors repeat themselves over and over in the log file and as a result the log file is balloning to hundreds of megs.and in my event viewer i'm getting errors that look like this:Source: MSSQLSERVER Event ID 17310 A user request from the session with SPID 71 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.however the SPID seems to change every couple of seconds.my log files went from about 28 megs to a couple hundred meg. and out of the blue there appears a log file that balloons to over 4 gig in a matter of minutes. it is so large that it tries to take up the remainder of the disk space on the disk that houses the log files. I cannot see what is in the log file since it is so large and it is cratering my server. what is odd is that there doesn't seem to be an increase in CPU usage.has anyone run across an issue like this before? any help or input is appreciated!

A quick fix is given on this page:http://sharepoint.microsoft.com/pedia/pages/ContentDetails.aspx?ContentID=810This is not a fix infact, it will just reduce the log file size so that your disk doesnt get out of space.The following article suggests a solution:http://blogs.msdn.com/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspxThere can be several reasons for this error to occur. Did you change something on the server recently? SSA

thats the frustrating thing... i've made no changes on my server at all. i'm hesitant to start truncating the log files until i find out what really is the problem... i have a TON ofSQLDump000X.log andSQLDump000X.mdmp files showing up, i just cleared out like 16,000 of them. the issue seems to be with SQL but i cannot find a solution thus far. i thought i had it fixed when i cleard my crawled content in my search. that seemed to temporarily solve the problem but its back for some reason...

I resolved the SQL issues by installing SP2, the OWSTIMER log issue is still there however. i'm having a 2-4GB log file generated hourly it seems that won't go away. how do you troubleshoot these issues? 10/24/2008 11:25:51.99 OWSTIMER.EXE (0x15FC) 0x14FCWindows SharePoint Services Timer 5uufMonitorableThe previous instance of the timer job 'Workflow', id '{B534BEC9-8542-409C-B0BA-7396E34C11AB}' for service '{29428BB5-81ED-4638-ABCC-801E4E2B6A3F}' is still running, so the current instance will be skipped. Consider increasing the interval between jobs.

I suffered from the exact same problem and the proposed solution (clearing the sharepoint configuration cache) in the posthttp://blogs.msdn.com/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspxas stated by 'SS Ahmed' solved the issue for me.SvenSven De Bont - MCAD

I am seeing the same problem on a MOSS2007 server (enterprise) with SP1. I tried the fix suggested by Joe Rodgers' blog post (i.e. clearing the cached XML files ) and when that didn't work I tried some variations (e.g. turning off IIS - i.e. IISRESET STOP - while the timer services was off and I was deleting the XML files) which also didn't change the log entries and the subsequqent log growth rate. At that point I was forced to treat the "symptom" (the log growth rate) instead of the rrot "disease" (i.e. whatever is causing the OWSTimer.exe log entries about previous instances) by following the MSDN entry about logging level (i.e. see http://support.microsoft.com/kb/941789/ ). I can't believe MS considers this (KB941789) a true fix but it's the best I could come up with. I'd sure appreciate from anyone who can explain the log growth, the reason the Joe Rodgers blog post didn't work for my server, and/or a true fix for the root problem causing OWTimer.exe to log so much.

I am also experiencing this problem and we've not made any changes to our sharepoint or SQL environment.

I am also experiencing this problem and we've not made any changes to our sharepoint or SQL environment.

Did as suggested. Cleared Cache. Re-started timer services. Within 1 minute log file has swelled to over 30 megs with "timer job is still running ..." errors. So no Mike. This is not the answer.ERJ MCSD MCDBA

First of all you need to know if the logs are verbose or information & If your environment has a lot of errors or not, many logs that I have seen that is too big like yours are mostly logigng errors about OWSTimer, so you need to know this first, to do so follow the below steps: Go to C:\Program Files\Common files\Microsoft Shared\Web Server Extensions\12\logs\YourServerName -Date .log Check the log content nature, If you find a lot of Information logs not error logs then run this STSADM command:STSADM -o setlogginglevel -default If it was OWSTimer errors or any other errors that is causing your log to expand this much, please let us know. Thanks, I. Elshafie.I. Elshafie

1. The logs were NOT set to verbose. 2. Logging level is already set to default. 3. A whole slew of OWSTimer for the most part. Used to be a whole lot of "List not found" for list that are quite clearly present. However it's been a while since these were seen.Edward R. Joell MCSD MCDBA

I am also facing these issues, and i have done all the steps of jeo but still problem is there... Can anybody tell me about this?Ali Murtaza Sharepoint Developer Xelleration LLC