Asked By Merv Porter [SBS-MVP]
15-Aug-07 08:21 PM
Hi Harry,
I'm only guessing that since your running Sharepoint 3.0, that this applies
to you. Not sure at all what the OWSTIMER error means, but the procedure
below for Sharepoint 3.0 Central Administration may help you get a handle on
your logs (and their size):
http://drunkmasterdev.blogspot.com/
---------------------------------------------
Things you should do after first installing Microsoft Office SharePoint
Server 2007 Beta 2 (MOSS)
Pat yourself on the back for a job well done.
Open up c:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\logs, and watch them files grow!
Start up Task Manager, find wsstracing.exe, and note its' neurotic CPU
utilization and growing memory usage
Make the madness less visible by reducing tracing:
Start SharePoint 3.0 Central Administration (you might have to pause the
Windows SharePoint Timer service before you can actually get there -
especially if you're using a VPC - for whatever reason, OWSTIMER.EXE can
easily soak up whatever CPU cycles you have...)
Go to Operations
Under Logging and Reporting, choose Diagnostic Logging
Under Event Throttling, choose All as the category (this may be
unnecessary, as it could be the default, but judging by the amount of
logging, it probably isn't)
Under Trace Log, set "Number of log files" to something reasonable - say,
5. You can leave "Number of minutes..." to be 30, unless you want those 5
files to be smaller in size. At the default rate, a 30 minute trace file in
my case seems to be about 200MB.
Click on OK.
You can see that if you don't reduce logging amounts, you're likely to
run out of disk space on your system drive...
-------------------------------------------
--
Merv Porter [SBS-MVP]
============================