11-09-2017 07:19 AM
When reporting problems, make it a point to always include the complete log of the failed step(s).
In the case of a failed batch run, make sure that all necessary files (source, log, output) are specified with a full path that you have permission to use.
How are you running your batch program? (cmd window, batch file, powershell, VB script, scheduler)
11-09-2017 07:26 AM
11-09-2017 08:57 AM
To quote myself:
"How are you running your batch program? (cmd window, batch file, powershell, VB script, scheduler)"
11-09-2017 09:03 AM
I give up.
02-02-2018 10:39 AM
I just hit a similar error. In my case it was because I did not include the -log option, and it looks like when a scheduled task runs as administrator, it writes the log to c:\WINDOWS\system32. I would double check that your -log option is in the command string.