Task scheduler- task completed "successfully" with exit code 0x8007001

Hi,
I am running a daily task which is supposed to
- wake the computer from hibernation
- copy a file to a network drive, and create a log file
- shutdown the computer

When starting the task manually from within the task scheduler, everything is executed as intended.

When leaving the computer in hibernation mode, the task scheduler wakes the computer at the specified time, but apparently the command file (.cmd) ist not executed at all. No log file ist created, no file is copied, and the computer is not shut down. The task is marked as "successfully completed with the return code 0x80070001" displayed in decimal (2147942401).
This error code seems to indicate an "illegal function", but I have no clue what that might be, especially since the task runs fine when started manually, as said.

Any hint highly appreciated, questions welcome.

As a matter of fact I have another task running weekly and reliably at night with the same task settings (different actions and trigger), and accessing the same NAS. Which is why I'm puzzled. No changes to the network at any time.
I'm not sure how to use the event viewer, a hint woud be great.
Thx and cheers, Steinspecht

I appreciate the notion of taking a problem apart. However, as said, the two tasks differ only in the actions (i.e., different commad scripts) and triggers (different execution times). Both start at the specified times which I can see in the scheduler protocol. One executes the command script, the other one does not. I can tell because both command scripts redirect their output to a log file. One does what it's supposed to (i.e. a weekly backup), the other does not (I.e. copyying a file each night). It still records the task as successfully completed with the return code mentioned in my initial post. If I only knew what exactly it means. Web research only mentions it in the connection with Windows backup and restore, something my command script doesn't invoke.

I shall now look at the links you provided - thanks a lot!

Back after a while in frustration.
I couldn't find anything suspicious in the event viewer at or around the times the task was started. There are some informational things recorded about "Music.UI (9036) {7FAAB28B-5CC2-407F-BD83-28FE53F0BA3C}:" and a protocol file C:\Users\Andrei\AppData\Local\Packages\Microsoft.ZuneMusic_8wekyb3d8bbwe\LocalState\Database\anonymo us\edb.log", apparently about a database module doing something about a logfile (I don't use MicrosoftZuneMusic and have no idea what this is!).

The error message in my first posting header should read "0x80070001", one zero was missing there.

Still no clue what to look for.

Yes this all works. But not when re-activating the computer shortly after midnight via the task scheduler. It looks like cmd.exe ist never started, therefore the comand script is not run. Then I get this weird return code.

Do you know anything about it? That is the only question I have.

the script has a delay of 3 minutes, but what use if it never runs. how do i delay starting a job in the scheduler which is set to start at time x??