Anybody have an idea what this is?

[srsust]

I must have set-up a logging file without setting limits, but for the life of me I can't remember where. This one has reached 4.5 gigs.

WINDOWS\system32\LogFiles\WMI\trace.log

I'd really like to get rid of this monster, or at least set some limits, but not knowing what's controlling it, I'm afraid to just delete it. Anybody have a suggestion on how I should proceed?

Thanks.
SRS:confused:

[Fatal_Exception]

looks like you have set up Windows Management Instrumention to trace net activity.

have you reviewed the log?

nobody needs a log that grows to that kind of size--if you haven't been examining it, you probably don't have any real use for the log function

as big as that log is, i'd delete it, then if the controlling app can't create it again, it should error for you.

[$1500-P4 gamer]

My sysmon log grows quit large.Is that what you are logging.If so deleteing it wont hurt anything.If it is sysmon you can set the log limit by the prog. itself.Start>prog>acc>system tools>sysmon.Hope that helped.

[bassman]

Deleting the log won't hurt because probably it will be created again. However, you can set the log's size limit to any desired. On the other hand, you could just...let it be...I don't think it'll grow to 1Gb :p

[Kiierun]

log file output is never mission critical stuff. it's telling you what it already knows. to be sure. you could rename it and reboot. if it causes wacky stuff to happen rename it back.

[jmatt]

Type these words one at a time into your Windows Help .

Task Sheduler
Troubleshooting
Log .

What I think is happening is that Troubleshooting or Task Sheduler has been set to log problems .

Something along those lines might find a setting that can be stopped .
Might even be able to do it from > Start > Run , type in msconfig & press Enter .

[Bellbus]

If your ever afraid to delete a file, the best idea is to rename it first and run your system for a little while. If nothing happens then delete it.

as stated, Log files are not usually system vital

[srsust]

Thank you all for troubling to help me.

1. WMI Control under Services and Applications has logging active, but with a 64Kb limit on the file.

2. Performance Logs and Alerts under Services and Applications is set to manual, but has not been started.

3. The system will not permit me to rename or delete the file.

4. Task Scheduling is set to automatic, and has been started, but I can find no indication of any logging.

5. Windows Management Instrumentation and Event Logging are set to start automatically and show as started but, again, I can't find where either is set to unlimited logging.

6. I believe SYSMON in XP is Performance Monitor, a sample of which is automatically set up when XP is installed (I have no "Start>prog>acc>system tools>sysmon"). I haven't done anything with this, but in any event the log file is set to "C:\PerfLogs\System_Overview.blg" and my problem is with "\WINDOWS\system32\LogFiles\WMI\trace.log" (at this moment 2.5 gigs).

7. I was finally able to get a look at the very beginning of the trace.log file, and have attached what I found there. Perhaps this will give you a clue to identify where I might go from here.

Thanks again,
SRS

[Fatal_Exception]

Looks pretty much like your standard NT event log.

[srsust]

Hup -- I agree. But, what snap-in is controlling it? Identifying the control seems the only way to deal with it. Any ideas?

SRS

[srsust]

Reporting my latest efforts:

1. I downloaded the Exctrlst tool and disabled reporting. I then rebooted and found that the TRACE.LOG file was still being created and grew rapidly.

2. I found the following in the TRACE.LOG file:

N T K e r n e l L o g g e r C : \ W I N D O W S \ S y s t e m 3 2 \ L o g F i l e s \ W M I \ t r a c e . l o g

\ D e v i c e \ H a r d d i s k V o l u m e 1 \ W I N D O W S \ S y s t e m 3 2 \ L o g F i l e s \ W M I \ t r a c e . l o g

\ D e v i c e \ N e t B T _ T c p i p _ { 8 1 1 E 9 E 3 9 - 9 9 1 2 - 4 A 0 2 - 9 C 8 0 - A 8 6 4 8 F E 1 3 C F 6 } ]?

3. Assuming that the "NT Kernel Logger" was creating the file, I unsuccessfully attempted to find a relevant entry in "Administrative Tools."

If I'm correct and the TRACE.LOG file is being created by the NT Kernel Logger, I assume I can limit the file's size if I can find the control for that logger. Any ideas?

Thanks,
SRS