Quirk with trace.log file

[tabbyplague]

Well this is weird... I use the Task Scheduler to run a daily task of the epg123client.exe to update my WMC guide on one of my WMC client computers. I use the following string: epg123client.exe -i \\192.168.1.3\epg123\epg123.mxf -match. In the "Actions" section of the Task Scheduler task I have set the "epg123client.exe" as the program to run with the " -i \\192.168.1.3\epg123\epg123.mxf -match" in the "Add arguments" box. It runs like a charm and updates my WMC guide with the latest epg123.mxf file that I have centrally stored, but for some reason the trace.log file does not record this action.

Out of curiosity, I created a batch file of the same script (i.e. epg123client.exe -i \\192.168.1.3\epg123\epg123.mxf -match) and used Task Scheduler to run this batch file. This also successfully updates my WMC guide information and the trace.log file captures this action. So why would the trace.log file capture the Task Scheduler batch file execution of this command and not the action with additional arguments command within Task Scheduler?

[glorp]

What is "Start in" in your task's Action tab set to? Search the computer. I think you may have a trace.log file somewhere else you don't expect it, like C:\ (root) or windows\system32.

[garyan2]

^ my thought as well. Here is what my client task looks like...

[tabbyplague]

Both of you guys are correct - found another trace.log file in my windows\system32 directory which appears to be the default for Task Scheduler. Have changed the start in directory to match my current epg123 directory and will see if it appends the current trace.log file when it runs tomorrow.

[tabbyplague]

Both of you guys are correct - found another trace.log file in my windows\system32 directory which appears to be the default for Task Scheduler. Have changed the start in directory to match my current epg123 directory and will see if it appends the current trace.log file when it runs tomorrow.

Yep - that corrected the problem. Thanks for the help!