I have a number of different sheduled tasks that are set to run some executable files written in VB.Net. When they go to run they almost always get an error saying that the task failed to start and references this error value:
Additional Data: Error Value: 2147942402
How can I fix this?
asked Aug 8, 2012 at 13:15
2
I was getting the same error message. As pointed out in this other answer, it turns out that the error code 2147942402 actually means File Not Found.
I was creating my Scheduled Task programmatically, and it turned out that I had a typo in the path of the executable that I was specifying to run, and it didn’t actually exist. Once I corrected the file path of the exe that the Scheduled Task was set to run then everything worked as expected.
answered Feb 9, 2018 at 22:41
deadlydogdeadlydog
22.7k14 gold badges112 silver badges118 bronze badges
2
I had the same issue when I tried running web pages with IE using windows scheduler.
Follow these steps:
-Right click your task -> properties.
-Click the Settings tab, look for «If the task is already running, then the following rule applies», should be at the bottom of the dialog, and set the DropDownList value to «Stop the existing instance».
-Click the Actions Tab, edit your task, under Program/script choose the FULL PATH of the application running your task (In my case I replaced iexplore.exe with C:\Windows\winsxs…\iexplore.exe)
Hope this helps you 
answered Apr 26, 2017 at 15:51
I got the same Additional Data: Error Value: 2147942402.
For me the solution that worked was to delete the task and create the new one, the same that was deleted. You can also try to validate the password for user on with the task is running.
answered Feb 4, 2015 at 7:54
Janusz NowakJanusz Nowak
2,6051 gold badge17 silver badges36 bronze badges
1
Changing permissions, different files or locations didn’t work for me.
I had to create a brand new task and disable the old one, and it worked for me. Something must’ve been corrupted with the original task.
answered Aug 20, 2018 at 16:16
EricEric
312 bronze badges
1
I fixed this error by changing «Run whether user is logged on or not» to «Run Only when user is logged on» on the General tab of the task.
You must a valid user on the General tab-> security options-> «When running the task, use the following user account:»
answered Sep 10, 2021 at 16:48
I was getting this error when running a batch file as my scheduled task. My task action pointed to a batch file and executed successfully but reported operational code 2 and the following details.
Task Scheduler successfully completed task...., action "C:\Windows\SYSTEM32\cmd.exe" with return code 2147942402
I fixed this by changing the final exit code to:
exit 0
Make sure to trap and handle errors in the batch file. If the batch runs successfully then change «exit» to «exit 0». Now the task scheduler result is «The operation completed successfully (0x0)».
answered Aug 2, 2022 at 20:08
I encountered the same issue while executing the command on the remote server. I fixed the issue by including cmd /c in front of the command.
The command for which I was getting error:
<filepath> <command to run>
The fix that solved the issue.
cmd /c <filepath> <command to run>
answered Feb 12 at 3:57
kgangadharkgangadhar
4,8865 gold badges36 silver badges54 bronze badges
- Remove From My Forums
-
Общие обсуждения
-
При входе в пользователя в систему получаю сообщение об ошибке «Планировщику заданий не удается запустить задачу «\Microsoft\Windows\CertificateServicesClient\UserTask» для пользователя «TESTDOMAIN\test_user». Дополнительные сведения: значение ошибки: 2147942402.». Прогуглился ничего толкового не нашел. Кто-нибудь сталкивался с таким?
-
Перемещено
8 марта 2010 г. 10:01
Несоответствие тематике раздела (От:Scripting Languages) -
Перемещено
Mike Wang (MSCS)
22 апреля 2012 г. 17:19
(От:Windows Server 2008) -
Изменен тип
Petko KrushevMicrosoft contingent staff
28 марта 2013 г. 9:08
Нет действий
-
Перемещено
In this post we’ll talk about three popular windows task scheduler error codes, task Scheduler 2147942401, 2147942402, and 2147942403. Those error prevent users from running their scheduled tasks successfully. If you’re using windows task scheduler often, chances are you’ve come across one or two of these codes. We’ll take a look at all the three error codes separately so that you can fully understand them. Let’s take a look at them right away.
How To Fix Task Scheduler 2147942401, 2147942402 and 2147942403
Task Scheduler 2147942401
When converted to hex code, task scheduler 2147942401 is the same as 0x80070001. This error code is confusing also because the task will be marked as ‘successfully completed’ but with the code 0x80070001. The error code indicate ‘illegal function’
Possible causes
The main cause is when the ‘start in’ for the configured action isn’t filled out.
How to fix it
In order to fill this you should open your schedule task and then right-click to open properties window. Navigate to actions tab and then click edit. When you open it you’ll realize it’s not filled and you need to fill in the path to your batch file. Once you filled that the problem will definitely be solved. This is the best way to fix task scheduler error code 2147942401 which is also the same as 0x80070001.
Task Scheduler 2147942402
2147942402 is the same as 0x80070002 when you convert to hex, it means file not found.
Possible cause
It might be possible there is an error when typing the path to the file, so try checking the file path before applying any fix. Some users have reported making a typo in the file path and fixing it has solved the problem.
Another reason that causes this problem is that you’ve set the task to be deleted if it’s not going to be scheduled again. And hence when you try to run the task again the path will not be found since the task has been deleted. In order to avoid this you need to set expiration time of the trigger at least 1 min ahead of the starting time of the trigger.
How to fix the problem
The fix is almost similar to 2147942403 as mentioned below.
- Right click on the task and click on properties.
- Hit the settings tab and check the last option that says ‘if the task is already running
- Then the following rule applies’ and from the drop down menu you should set as ‘stop the existing instance’.
Second fix
Another way to fix this is to just recreate the schedule task again. Since this error is generated due “folder not found”, recreating the task will create a new folder if the previous one is missing. Even if the folder for the failed task exists, delete it and create a new one.
These are the two effective ways to get rid of this error code.
Task Scheduler 2147942403
You should understand that 2147942403 is the same 0x80070003 in hex value and it means that system is unable to find the specified path. The path that’s saved in task scheduler folder couldn’t be found and hence you receive the message ‘ERROR-PATH NOT FOUND’ which means the system couldn’t locate the path to the given task.
Possible fixes
- Open windows task scheduler; control panel > administrative tools > Task scheduler,
- You should Delete SmartFTP task folder that’s located in task scheduler
- Restart the SmartFTP.
Most of the time the problem will be solved by applying this fix.
Second fix
Another fix is by changing task scheduler settings;
Open task scheduler > click on scheduled job properties > click on settings, There are options listed and you need to take a look at the one that says, ‘if the task is already running, the following rule applies’, in the drop-down options you should select ‘stop the existing instance’, Click save and then exit the window. Go back now and check to see whether your task is running or not. Following the two methods will help you fix task scheduler error 2147942403. Let’s now move to the next error code.
Conclusions:
We’ve now reached the end of the article and if you have any other suggestions that have worked for you regarding these three error codes namely: 2147942403, 2147942402, and 2147942401. Please drop a comment for our readers to learn how to fix the problem. Let us know if the fixes shared here have worked for you or not.
Windows Server 2008 R2 (fully patched)
I’m trying to run a scheduled task to move a specific type of files from C:\Windows\Temp to E:\Foo_blah_blah_blah_blah\Foo2 and for some reason am getting the following error:
Task Scheduler failed to start instance «{fe0f148a-cece-44a0-a4d1-914aaf21daa8}» of «\Move Temp Files» task for user «FOOBOX\Administrator». Additional Data: Error Value: 2147942402
Any idea why this is happening?
Additional details:
- The task is configured to run as an account that has authority to move the file.
- The task is configured to run whether user is logged on or not. It fails for both scenarios — same errors.
- The task is configured to run for the local OS (Windows Server 2008)
- The command is broken up into two parts. Program/script:
moveAdd Arguments:C:\Windows\Temp\*.foo E:\Foo_blah_blah_blah_blah\Foo2\
If I run this same command move C:\Windows\Temp\*.foo E:\Foo_blah_blah_blah_blah\Foo2\ from the windows command prompt, it works fine.
What am I missing?
SamErde
3,4193 gold badges24 silver badges44 bronze badges
asked Dec 4, 2013 at 21:17
1
As Ryan Ries pointed out, 2147942402 translates to «File not Found» — which is a very appropriate response. Try and press Win+R, put in «move» and press enter — that’s the interactive equivalent of what your task is failing to do.
The reason is that MOVE is not a program, but a native command in cmd.
It should be:
Program: "cmd.exe"
Arguments: "/c move C:\Windows\Temp\*.foo E:\Foo_blah_blah_blah_blah\Foo2\"
answered Dec 4, 2013 at 23:05
The reason is: the Task is configured to be deleted when it is not scheduled to run again. This is configured in the Settings Tab.
The deletion of the Task is done at the expiration time of the Trigger that fires the Task. If the expiration time of the trigger is exactly the same as the start time of the trigger it may (incidentally) happen that the Task is deleted a few seconds before its trigger fires. This causes the event 101 with reason code 2147942402.
The solution is to set the expiration time of the trigger 1min later than the start time of the trigger.
answered Oct 21, 2014 at 12:07
with Powershell, specify full path in command, thus C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
answered Oct 9, 2020 at 14:39
FranKFranK
211 bronze badge
1
The answer that Matthias posted helped me figure out my problem.
I had put the whole command line into the «Program» field, path and args all together; I hadn’t noticed that there was a separate «Args» input field. When I split the arguments off and entered them separately, my scheduled task ran like a champ.
Diagnosis: The OS was looking for a program called "C:\bin\someprog.BAT connect keep" rather than looking for "C:\bin\someprog.BAT" and invoking that with arguments connect keep.
My mistake, now fixed.
answered Mar 16, 2020 at 18:38
rich prich p
1013 bronze badges
After going down several rabbit holes I found the issue was that Windows couldn’t find powershell.exe (???). Putting the full path to powershell into the programme field solved it.
answered Sep 28, 2021 at 6:23
Maybe it’s the problem of the blanks in the line of order
example:
C:\Program Files\Wireshark\Wireshark.exe -i1 -k FAILS
«C:\Program Files\Wireshark\Wireshark.exe» -i1 -k OK
answered Aug 29, 2016 at 18:32
You must log in to answer this question.
Not the answer you’re looking for? Browse other questions tagged
.
Not the answer you’re looking for? Browse other questions tagged
.
Server 2008 R2 (полностью исправлен)
Я пытаюсь запустить запланированное задание для перемещения файлов указанного типа из C: \ Windows \ Temp в E: \ Foo_blah_blah_blah_blah \ Foo2 и по какой-то причине получаю следующую ошибку:
Планировщику не удалось запустить экземпляр задачи «{fe0f148a-cece-44a0-a4d1-914aaf21daa8}» задачи «\ Move Temp Files» для пользователя «FOOBOX \ Administrator». Дополнительные данные: Значение ошибки: 2147942402
Есть идеи, почему это происходит?
Дополнительные детали:
- Задача настроена для запуска от имени учетной записи, обладающей полномочиями для перемещения файла.
- Задача настроена на выполнение независимо от того, вошел ли пользователь в систему или нет. Это терпит неудачу для обоих сценариев — те же самые ошибки.
- Задача настроена на запуск для локальной ОС (Windows Server 2008)
- Команда разбита на две части. Программа / скрипт:
moveДобавить аргументы:C:\Windows\Temp\*.foo E:\Foo_blah_blah_blah_blah\Foo2\
Если я запускаю эту же команду move C:\Windows\Temp\*.foo E:\Foo_blah_blah_blah_blah\Foo2\из командной строки Windows, она работает нормально.
Чего мне не хватает?
Ответы:
Как отметил Райан Райс, 2147942402 переводится как «Файл не найден», что является очень подходящим ответом. Попробуйте нажать Win + R, введите «move» и нажмите enter — это интерактивный эквивалент того, что ваша задача не справляется.
Причина в том, что MOVEэто не программа, а встроенная команда в cmd.
Должен быть:
Программа: "cmd.exe"
Аргументы:"/c move C:\Windows\Temp\*.foo E:\Foo_blah_blah_blah_blah\Foo2\"
Причина в том, что задание настроено на удаление, если не запланировано повторное выполнение. Это настраивается на вкладке «Настройки». Удаление Задачи выполняется во время истечения Триггера, который запускает Задачу. Если время истечения триггера точно совпадает со временем запуска триггера, может (случайно) произойти, если Задание будет удалено за несколько секунд до срабатывания триггера. Это вызывает событие 101 с кодом причины 2147942402. Решение состоит в том, чтобы установить время истечения триггера на 1 мин позже времени начала триггера.
Может быть, это проблема пробелов в строке порядка заказа:
C: \ Program Files \ Wireshark \ Wireshark.exe -i1 -k FAILS
«C: \ Program Files \ Wireshark \ Wireshark.exe» -i1 -k ОК