Why Windows 7 Task Scheduler task crashes with error 2147942667

Question

I got a strange problem. I assigned a task to the batch file. When I run the task with the option Run only when user is logged on , everything works fine. but I want to run this task in the background, and so I start it with the Run whether user is logged on or not option. Now when I run the task, it does not work. I get the following 2 errors. I do not understand this error. Please help me solve this problem.

  Task Scheduler failed to launch action "C:\Windows\SYSTEM32\cmd.exe" in instance "{2a7cc950-fad9-4633-9701-af75a0fd220d}" of task "\stmm\Daemon". Additional Data: Error Value: 2147942667. Task Scheduler failed to start instance "{2a7cc950-fad9-4633-9701-af75a0fd220d}" of "\stmm\Daemon" task for user "GBLADHEDANI\N011940" . Additional Data: Error Value: 2147942667. 

Answer 1

I had the same problem.

The solution for me was found in Microsoft KB article 2452723:

Windows Vista scheduled tasks cannot start if the path in the "Start at (Optional)" box is in quotation marks

Basically, edit the scheduled task and withdraw Quotes from the Start In field:

• Open your scheduled task.
• Click on the "Actions" tab.
• Open your action
• Remove quotes (") from the" Start (optional) "field
• Save and close all open dialogs

Answer 2

For me it was "Start In" - I copied the values ​​from an older server and updated the path to the new exe location, but I forgot to update the "start in" location - if it does not exist, you will also get this error

To quote @ hans-passant's comment above, because it is useful to discard this problem:

Convert error code to hex to get 0x8007010B. 7 makes it a Windows Error. Which makes error code 010B 267. "The directory name is invalid." Of course this is happening.

Answer 3

This can happen for several reasons. In my case, this was due to a permission issue. The user to whom the task was running did not have the right to write to the logs directory, so he could not execute this error.

Answer 4

I had the same problem on Windows7.

I received error 2147942667 and a report about the impossibility of starting c: \ windows \ system32 \ CMD.EXE. I tried without double quotes in Script and Start-in, and that didn't make any difference. Then I tried replacing all the links to the mapped network drives and the UNC links (\ Server1 \ Sharexx \ my_scripts \ run_this.cmd) and this fixed it for me. Pat.

Answer 5

For a more general answer, convert the error value to hex, then find the hexadecimal value in "Windows Task Scheduler Error and Success Constants"