FIM Portal (WSS) Log File Growth Issue

Published on Sunday, June 20, 2010 in

When I was installing the FIM Portal & Service binaries on the second node of my NLB setup the setup failed. I went looking in the log file and it told me the disk was full. After starting up TreeSize (in UAC mode, or else the statistics are completely wrong ;) ) I quickly found the Sharepoint logs being the culprit.


The log files can be found at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS. Mine were about 30 GB and it took them about 1 hour to get that big… On a fresh WSS install, no activity whatsoever on the site…

The log file looks like this:


And the error:

06/14/2010 15:59:49.06 OWSTIMER.EXE (0x04F8) 0x0508 Windows SharePoint Services Timer 5uuf Monitorable The previous instance of the timer job 'Config Refresh', id '{EA314111-18D2-4E59-B709-56608E8D5BD4}' for service '{392FB345-12E6-4F93-8528-29136C9B2602}' is still running, so the current instance will be skipped. Consider increasing the interval between jobs.

There is no real solution, just a workaround… It’s explained in KB941789: You receive error messages after you install security update 931212 (MS07-040) on a Windows SharePoint Services 3.0 Web front-end server or on a SharePoint Server 2007 Web front-end server

Related Posts

No Response to "FIM Portal (WSS) Log File Growth Issue"

Add Your Comment