• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Sharepoint 3.0 creating huge log files

Zucarita9000

Golden Member
I've recently re-installed IIS on our server, and also installed Sharepoint Services 3.0.
Everything works quite well, except that after a few days I noticed that something was eating up space on the C: drive. After a few minutes of file-hunting, I found that this directory:

C:\Program Files\Microsoft Shared\web server extensions\12\LOGS

was filled with huge log (.txt) files. Within just 2 or 3 days, there were 6GB of log files (some txt files were over 600MB).

What the hell is up with that?? I also noticed that from time to time the server starts to lag horribly, and I suspect it's because this issue.

Any ideas?
 
This is an excerpt of one of the log files:

Timestamp Process TID Area Category EventID Level Message Correlation
06/19/2007 10:20:51.10 mssearch.exe (0x1704) 0x0C94 Search Server Common GatherStatus 0 Monitorable Insert crawl 461 to inprogress queue hr 0x00000000 - File😀:\office\source\search\search\gather\server\gatherobj.cxx Line:6421
06/19/2007 10:20:51.14 mssearch.exe (0x1704) 0x0C94 Search Server Common GatherStatus 0 Monitorable Request Start Crawl 0, project Search, crawl 461 - File😀:\office\source\search\search\gather\server\gatherobj.cxx Line:2775
06/19/2007 10:20:51.14 mssearch.exe (0x1704) 0x0C94 Search Server Common GatherStatus 0 Monitorable Advise status change 0, project Search, crawl 461 - File😀:\office\source\search\search\gather\server\gatherobj.cxx Line:4688
06/19/2007 10:20:51.14 OWSTIMER.EXE (0x0DD4) 0x0E98 Search Server Common MS Search Administration 7hkp High Processing content source 'Default'.
06/19/2007 10:20:53.48 mssdmn.exe (0x13C0) 0x0B74 Search Server Common MS Search Indexing 8z15 Medium GetChanges(before ws call) URL http://serverhp:12953, Content Database Id='{02e657db-6adf-4dac-8d40-1626d394290a}', LastChange 1;0;02e657db-6adf-4dac-8d40-1626d394290a;633177922675600000;1969, CurrentChange
06/19/2007 10:20:53.78 mssdmn.exe (0x13C0) 0x0B74 Search Server Common MS Search Indexing 8z16 Medium GetChanges(after ws call ) URL http://serverhp:12953, LastChange
 
You may have figured this out, but I think this would be the navigation path:

Central Administration -> Operations -> Diagnostic Logging

From there you can play with the Event Throttling (what you log) and Trace Log (how much you log) settings.
 
Back
Top