SharePoint Trace Log File Huge Every Night

apitech
apitech used Ask the Experts™
on
We installed Windows SharePoint Services 3.0 (WSS), last Friday afternoon, on Windows Server 2008.  All went well, and no errors were received.

Last Friday night at 7:44, however, WSS generated a trace log file that was over 15 GB.  So, in the Diagnostic section of Operations, I reduced the maximum number of log files from 96 to 24 and increased the number of minutes per log from 30 to 60.

Then, last night at 7:58, WSS generated a trace log file of over 41 GB!!!  So, I reduced the maximum number of log files to 10.

Event Viewer is not reporting any issues occurring, at these times of night.  And, this site is brand new.  So, no data is being entered or imported into it.

I am having Diagnostic Logging collect error reports but no throttling.

Any ideas on what can be causing this and what to do to keep the log file size to a minimum?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Justin SmithSr. System Engineer
Top Expert 2012

Commented:
What about your Windows App Event log, is it filling as well?  What errors seem to be filling it?  You can adjust the level of logging through Central Admin.

Author

Commented:
Again, Event Viewer is not showing anything for those dates and time periods.  The only thing, for instance, it said about last night is that disk space is running low.  That's not very helpful.

I know about changing the logging through Diagnostic Logging in the Operations page of SharePoint Central Admin.  But, what specifically else can I do, beyond what I mentioned earlier?
Justin SmithSr. System Engineer
Top Expert 2012

Commented:
read throught the logs, see what they are throwing a fit about, fix it.
CompTIA Network+

Prepare for the CompTIA Network+ exam by learning how to troubleshoot, configure, and manage both wired and wireless networks.

Listlogginglevels: Stsadm operation

In addition to the categories that are visible on the Diagnostic logging  page on the SharePoint Central Administration Web site, the showhidden operation also displays the hidden categories that are not available on the Diagnostic logging page.

Syntax


stsadm.exe -o listlogginglevels [-showhidden]

Open in new window

Also:
The actual registry key that specifies the location of the trace log is called LogDir and is located at the following location:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS]
However, you should never edit this value directly.

See if the value is valid for key entries?

Author

Commented:
It's WSS, not MOSS.  So, the stadm.exe does not work.
Justin SmithSr. System Engineer
Top Expert 2012

Commented:
WSS still has STSADM

Author

Commented:
But, I got an error message when I tried to "Run" the script mentioned earlier in this posting on stsadm.exe.  It said that it could not find the file.  Also, I did a search in Windows Explorer and Windows Explorer could not find it either.  So, I did not know what other conclusion to draw.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial