Capture the output from a Scheduled Task

Today I had to diagnose a problem with a Windows Scheduled Task that was sporadically failing with a non-zero return code. The exe in question was a .NET console application that was throwing an exception before Main() got called; it was outside our try-catch block.


Anyway, if you ran the .exe from a command line yourself, you would see the error written to stderr. If you ran the Scheduled Task, the error was not logged anywhere.

To capture the output of the scheduled task, I redirected it to a text file with the following command:

before: NightlyBatchJob.exe

after: cmd /C NightlyBatchJob.exe >> NightlyBatchJob.output.txt 2>&1

The > symbol redirects the output to a file; >> makes it append instead of creating a new blank file each time it runs. 2>&1 makes it include the output from stderr with stdout — without it you won’t see any errors in your logs.


The whole command is run in a new cmd.exe instance, because just running an .exe directly from a scheduled task doesn’t seem to produce any console output at all.

16 thoughts on “Capture the output from a Scheduled Task

  1. Thanks!

    Was just trying to solve the issue with “why I do not see a redirected output file at all” and found your post. After adding “cmd /c” – everything worked fine :)

  2. Thanks, was trying to figure out why this wasn’t working for me, and this solved the problem.

  3. Hi Rich,I have four scheuled jobs .I want to run one after another one.After first one success second one should start.Could you pls help on this.

  4. Richard.Can you pls give me some direction on this.I am new on this.Could you pls send similar batch files.So that i will try to modify and use it

  5. hi,

    i cannot see any redirected output file. i am not using a .exe file rather calling a script in scheduled tasks. please help me out

  6. Thank you very much – I have been faffing about for two weeks trying to figure out why my program is failing when called from a scheduled job. I still don’t quite understand why – but I now know *how* – which is a vital first step!

  7. Thank’s a lot, it really helps me !!!!!
    What a strange thing not being able to directly redirect outputs like : myapp.exe >stdout.txt 2>stderr.txt !

  8. Another thank you for posting this information. I needed a solution and fast, and this provided it for me. Thanks again!

Comments are closed.