Event 103: Task Scheduler failed to start instance «{…}» of «…» task for user «…». Additional Data: Error Value: 2147942667. Event 203: Task Scheduler failed to launch action «…» in instance «…» of task «…». Additional Data: Error Value: 2147942667.
Error 2147942667 означает ERROR_DIRECTORY
Лечится удалением кавычек в поле Start In в настройках задания.
Запись опубликована в рубрике Client, Server. Добавьте в закладки постоянную ссылку.
I have scheduled a task to lauch a batch file. When I run the task with the option
Run only when user is logged on
everything works fine.
I want to run this task in the background, hence I am running it using the option
Run whether user is logged on or not.
Now when I run the task under that parameter, it is not working. I get the following 2 errors:
- 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.
What is Error Value: 2147942667? How can I resolve this errors?
TylerH
20.8k66 gold badges76 silver badges101 bronze badges
asked Nov 29, 2012 at 4:40
5
To get the relevant error message:
- Convert 2147942667 to hex: 8007010B
- Take last 4 digits (010B) and convert to decimal: 267
- In a Command Prompt, run
net helpmsg 267
- Result: «The directory name is invalid.»
The solution for me was that I had quotes in the «Start In» field. I found this information in Microsoft KB Article 2452723, Windows Vista onward scheduled tasks fail to run if the path in «Start in (Optional)» field has quotes.
Basically, edit your scheduled task and take the quotes out of the «Start In» field:
- Open your Scheduled Task
- Switch to «Actions» tab
- Open your Action
- Remove Quotes («) from the field «Start in (optional)»
- Save and close all open dialogs
You should also check for other causes of the error, like not having permission to access the directory, or using a mapped drive letter which is only available during certain login sessions.
TylerH
20.8k66 gold badges76 silver badges101 bronze badges
answered Jan 14, 2013 at 20:28
3
For me it was the «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 doesn’t exist, you get this error too
Quoting @hans-passant ‘s comment from above, because it is valuable to debugging this issue:
Convert the error code to hex to get 0x8007010B. The 7 makes it a
Windows error. Which makes 010B error code 267. «The directory name is
invalid». Sure, that happens.
answered Apr 27, 2017 at 5:23
user230910user230910
2,3532 gold badges28 silver badges50 bronze badges
This can happen for more than one reason. In my case this happened due to a permissions issue. The user that the task was running as didn’t have permission to write to the logs directory so it failed with this error.
answered Nov 30, 2016 at 10:21
CookalinoCookalino
1,55914 silver badges19 bronze badges
I had the same problem, on Windows7.
I was getting error 2147942667 and a report of being unable to run c:\windows\system32\CMD.EXE. I tried with and without double quotes in the Script and Start-in and it made no difference. Then I tried replacing all path references to mapped network drives and with UNC references (\Server1\Sharexx\my_scripts\run_this.cmd) and that fixed it for me.
Pat.
answered Feb 6, 2017 at 10:22
Pat FahyPat Fahy
1091 silver badge5 bronze badges
2
Автор: , 07 Янв 2014 • 15:17 1 отзыв
Планировщик Windows может завершать задачу с ошибкой 2147942667
Event 103: Task Scheduler failed to start instance "{…}" of "…" task for user "…". Additional Data: Error Value: 2147942667. Event 203: Task Scheduler failed to launch action "…" in instance "…" of task "…". Additional Data: Error Value: 2147942667.
Лечится это диагностикой вкладки Actions.
Заходим, проверяем правильность указания директории для скрипта и параметра «Start in».
Обычно, ошибка заключается в том, что при переносе задачи на Vista / Windows Server 2008 Вы оставляете двойные кавычки, их нужно убрать, сохранить задачу в планировщике.
I have scheduled a task to lauch a batch file. When I run the task with the option
Run only when user is logged on
everything works fine.
I want to run this task in the background, hence I am running it using the option
Run whether user is logged on or not.
Now when I run the task under that parameter, it is not working. I get the following 2 errors:
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.
What is Error Value: 2147942667? How can I resolve this errors?
Solution 1
To get the relevant error message:
- Convert 2147942667 to hex: 8007010B
- Take last 4 digits (010B) and convert to decimal: 267
- In a Command Prompt, run
net helpmsg 267
- Result: “The directory name is invalid.”
The solution for me was that I had quotes in the “Start In” field. I found this information in Microsoft KB Article 2452723, Windows Vista onward scheduled tasks fail to run if the path in “Start in (Optional)” field has quotes.
Basically, edit your scheduled task and take the quotes out of the “Start In” field:
- Open your Scheduled Task
- Switch to “Actions” tab
- Open your Action
- Remove Quotes (“) from the field “Start in (optional)”
- Save and close all open dialogs
You should also check for other causes of the error, like not having permission to access the directory, or using a mapped drive letter which is only available during certain login sessions.
Solution 2
For me it was the “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 doesn’t exist, you get this error too
Quoting @hans-passant ‘s comment from above, because it is valuable to debugging this issue:
Convert the error code to hex to get 0x8007010B. The 7 makes it a
Windows error. Which makes 010B error code 267. “The directory name is
invalid”. Sure, that happens.
Solution 3
This can happen for more than one reason. In my case this happened due to a permissions issue. The user that the task was running as didn’t have permission to write to the logs directory so it failed with this error.
Solution 4
For a more generic answer, convert the error value to hex, then lookup the hex value at Windows Task Scheduler Error and Success Constants
Solution 5
I had the same problem, on Windows7.
I was getting error 2147942667 and a report of being unable to run c:\windows\system32\CMD.EXE. I tried with and without double quotes in the Script and Start-in and it made no difference. Then I tried replacing all path references to mapped network drives and with UNC references (\Server1\Sharexx\my_scripts\run_this.cmd) and that fixed it for me.
Pat.
I have scheduled a task to lauch a batch file. When I run the task with the option
Run only when user is logged on
everything works fine.
I want to run this task in the background, hence I am running it using the option
Run whether user is logged on or not.
Now when I run the task under that parameter, it is not working. I get the following 2 errors:
- 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.
What is Error Value: 2147942667? How can I resolve this errors?
To get the relevant error message:
- Convert 2147942667 to hex: 8007010B
- Take last 4 digits (010B) and convert to decimal: 267
- In a Command Prompt, run
net helpmsg 267
- Result: «The directory name is invalid.»
The solution for me was that I had quotes in the «Start In» field. I found this information in Microsoft KB Article 2452723, Windows Vista onward scheduled tasks fail to run if the path in «Start in (Optional)» field has quotes.
Basically, edit your scheduled task and take the quotes out of the «Start In» field:
- Open your Scheduled Task
- Switch to «Actions» tab
- Open your Action
- Remove Quotes («) from the field «Start in (optional)»
- Save and close all open dialogs
You should also check for other causes of the error, like not having permission to access the directory, or using a mapped drive letter which is only available during certain login sessions.
For me it was the «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 doesn’t exist, you get this error too
Quoting @hans-passant ‘s comment from above, because it is valuable to debugging this issue:
Convert the error code to hex to get 0x8007010B. The 7 makes it a
Windows error. Which makes 010B error code 267. «The directory name is
invalid». Sure, that happens.