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
21.8k14 gold badges106 silver badges117 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:Windowswinsxs…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,4511 gold badge17 silver badges34 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:WindowsSYSTEM32cmd.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
- Remove From My Forums
-
Question
-
We’re using a physical installation of Windows Server 2019 Standard at a French location. The server is working normally. Task Scheduler is used for a small number of tasks. One of the tasks runs a CMD-file daily. The CMD-file launches ROBOCOPY which creates
log files. The task runs successfully, since the log files are created. However, the «Action completed» event in the Task History always shows a return code of 2147942402.From Google searches of this return code, it translates to «file not found». But that’s not the case here, since the task runs and Robocopy creates its log files.
If I launch the CMD-file inside a VBS wrapper, Robocopy runs, the log files are created, and the return code is 0.
What does the 2147942402 return code really mean? How can it be avoided without resorting to a VBS wrapper?
regards, AndyA
Windows Server 2008 R2 (fully patched)
I’m trying to run a scheduled task to move a specific type of files from C:WindowsTemp to E:Foo_blah_blah_blah_blahFoo2 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 «FOOBOXAdministrator». 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:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2
If I run this same command move C:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2 from the windows command prompt, it works fine.
What am I missing?
SamErde
3,3443 gold badges23 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:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2"
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:WindowsSystem32WindowsPowerShellv1.0powershell.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:binsomeprog.BAT connect keep" rather than looking for "C:binsomeprog.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 FilesWiresharkWireshark.exe -i1 -k FAILS
«C:Program FilesWiresharkWireshark.exe» -i1 -k OK
answered Aug 29, 2016 at 18:32
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.
Содержание
- question
- Windows 10 20H2 Install Update Fails with Error 2147942402
- 4 Answers
- Ошибка 2147942402 windows 10
- Вопрос
- Все ответы
- Windows Update issue: Error 2147942402
- 4 Replies
- Ошибка 2147942402 windows 10
- Не устанавливаются KB4519976 и KB4520003 — решение проблемы
- Статьи по теме:
- Комментарии: 8 к “Не устанавливаются KB4519976 и KB4520003 — решение проблемы”
question
Windows 10 20H2 Install Update Fails with Error 2147942402
This install has been failing for some time now, and I find that I’m currently at 1909, which is now out of service.
Looking at the Event Viewer, I see this:
ErrorCode 2147942402
ErrorString The system cannot find the file specified.
CommandLine «C:WINDOWSsystem32wusa.exe» Windows8-RT-KB2937636-x86 /quiet
I downloaded KB2937636, but the install failed as it’s for Windows 8.
The question I have is: Why is Win 10 20H2 trying to install a Win 8 KB update?
4 Answers
Most end users do not understand the update error messages or codes.
And many helpers must continue to learn about new messages and codes.
Some update or upgrade messages are easy and others are complex.
If you choose to clean install then backup files to another disk drive or the cloud.
This is information on clean install:
Reset save files, Custom install (saves files similar to a reset save files) and Windows refresh tutorials can also be provided.
Again some troubleshooting can be easy and others can be complex.
Files are collected then trial and error steps are performed.
.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.
On the bottom of each post there is:
Propose as answer = answered the question
On the left side of each post: Vote = a helpful post
.
.
.
.
.
It is very strange. Indeed the KB2937636 it is a cumulative update for 2012/8 that has nothing to do with 20H2. Could it be a pending update that is superseded, but since it failed back in the day it still appears pending before the 20H2?
I would try to rebuild the update repository this way:
If after this still gives you error I would try with a health image restore using DISM: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/repair-a-windows-image
—If the reply is helpful, please Upvote and Accept as answer—
Thank you for the reply, LimitlessTechnology-2700.
I issued the commands in Powershell, and they all completed successfully.
I then launched the Windows Upgrader program, which then started installing 21H1 instead of 20H2 as before.
As before, it hits 99% and then hangs.
The only action I can take is to end the program with Task Manager.
Event Viewer shows:
The program Windows10UpgraderApp.exe version 1.4.9200.23367 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 1730
Start Time: 01d7bac7c399b30c
Termination Time: 4294967295
Application Path: C:Windows10UpgradeWindows10UpgraderApp.exe
Report Id: 571653e4-0ce4-48b0-8660-854ce0e9b2ac
Faulting package full name:
Faulting package-relative application ID:
Hang type: Top level window is idle
I might have to do a Win 10 install from scratch.
Please indicate whether you want to troubleshoot or clean install.
Troubleshooting will require running log collectors and trial and error steps.
Clean install will require the creation of a windows 10 iso flash drive, saving important files to another disk drive or the cloud, installation of the new operating system, installation of new drivers, installation of applications.
.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.
On the bottom of each post there is:
Propose as answer = answered the question
On the left side of each post: Vote = a helpful post
.
.
.
.
.
Источник
Ошибка 2147942402 windows 10
Вопрос
Event Details: Task Scheduler failed to start «MicrosoftWindowsCertificateServicesClientUserTask» task for user «Domainuserxx». Additional Data: Error Value: 2147942402.
Все ответы
If those errors are appearing in the Server Event Logs, please post up the Event Id and the Source, and identify which is which. Or, you can go to www.eventid.net and research them yourself. If you have, and there is no info, then tell us that.
-Please post the resolution to your issue so others may benefit.
-Get Your SBS Health Check at www.sbsbpa.com
Event Details: Task Scheduler failed to start
«MicrosoftWindowsCertificateServicesClientUserTask» task for user
«Domainuserxx». Additional Data: Error Value: 2147942402.
-Kevin Weilbacher (SBS MVP) «The days pass by so quickly now, the nights are seldom long»
http://msmvps.com/blogs/kwsupport/default.aspx
I was desperately trying to solve this issue and tried procedure from the link below, but with no luck. Would somebody try it to make sure it is 100% not working for this particular issue?
the link: http://davidcmoisan.wordpress.com/2010/11/14/resolving-%E2%80%9Cpautoenr-dll-raised-an-exception%E2%80%9D/
Well that one looks pretty frightening to do? These are the only two errors I got today.
What is the consequence of ignoring them? Or maybe I should just restart the server on a regular basis?
Many thanks for your time.
Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk
Well I also had the error when trying to reschedule a Job (trigger One time) Windows 2008 R2
Initial Error Message comming from the task scheduler was :
The following error was reported: The referenced account is currently locked out and may not be logged on to..
In the event view for TaskScheduler I had 2 errors:
Task Scheduler failed to start “MicrosoftWindowsCertificateServicesClientUserTask” task for user “username”. Additional Data: Error Value: 2147942402.
The user in question was disconnected for many days, no schedule task created or running under this user and account was not locked, I logged off the user, still had the issue.
What I did to solve it:
First when to my task, I changed the User or Groups under the General tab
Selected Run only When user is logged on then click on OK
After that I was able to reschedule my job.
Put back Run whether user is logged on or not.
everything is now back to normal.
Источник
Windows Update issue: Error 2147942402
Windows update «Security Update for Windows (KB4015549)» could not be installed because of error 2147942402 «The system cannot find the file specified.» (Command line: «»C:Windowssystem32wusa.exe» «C:AMD64-all-windows6.1-kb4015549-x64.msu» «)
I’ve tried removing cache.. restarting services.. turning off unnecessary services..
any help appreciated
The help desk software for IT. Free.
Track users’ IT needs, easily, and with only the features you need.
Ugh. 4015549 broke software by Open Text and gave me some heartache from it.
I’m assuming the update is actually stored in that location at the root of C:?
If so, I’ve used these instructions for single odd cases just to get them shoved into the system so I can move about my day: https://blogs.technet.microsoft.com/askcore/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-with.
yes it was on C:.. i tried a couple different logins and locations.. i’ll try the DISM tool in your link..thanks
Ugh. 4015549 broke software by Open Text and gave me some heartache from it.
I’m assuming the update is actually stored in that location at the root of C:?
If so, I’ve used these instructions for single odd cases just to get them shoved into the system so I can move about my day: https://blogs.technet.microsoft.com/askcore/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-with.
I’m not the elegant problem solver that generally mills around here. My solutions tend to be like the big nasty hammer you keep around in case you need to perform some percussive maintenance on a contraption from the 1950s.
I’ve generally had good luck unpacking the update and manually installing the cab files, it bypasses whatever is causing wusa to flip out.
Ugh. 4015549 broke software by Open Text and gave me some heartache from it.
I’m assuming the update is actually stored in that location at the root of C:?
If so, I’ve used these instructions for single odd cases just to get them shoved into the system so I can move about my day: https://blogs.technet.microsoft.com/askcore/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-with.
PS C:kb1> Dism.exe /online /add-package /packagepath:c:kb1Windows6.1-KB4015549-x64.cab
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7601.18489
Источник
Ошибка 2147942402 windows 10
Сообщения: 1
Благодарности:
Один из вариантов
Невозможно подключиться к принтеру Kyocera FS-1020MFP »
——-
Скоро станет на одного Линуксоида больше!
» width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″>
Сообщения: 1
Благодарности:
Приветствую, присоединяюсь к проблеме.
комп, на котором рашарен принтер, видится, принтер видится, но не подключается
-дрова переустанавливал
-службы в порядке
-принтер видится по сети
-в АД видится
-по локальному порту не подключается
ошибка как у ТС, на обоих машинах win 10 pro
Сообщения: 2
Благодарности: 2
» width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″> » width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″>
Сообщения: 25794
Благодарности: 4315
Сообщение оказалось полезным? Поблагодарите автора, нажав ссылку 
Полезное сообщение чуть ниже.
Источник
Не устанавливаются KB4519976 и KB4520003 — решение проблемы
По недоброй традиции последних месяцев пользователи Windows 7 и Windows Server 2008 R2 столкнулись с ошибками при установке обновлений KB4519976 и KB4520003 (ежемесячные пакеты обновлений). Впрочем, исправить данные ошибки совсем не сложно.
Как известно, с недавних пор корпорация Microsoft подписывает новые обновления для Windows 7 и Windows Server 2008 R2 только при помощи алгоритма SHA-2. Отсюда следует, что, если своевременно не подготовить операционную систему к таким переменам, новые патчи на неё устанавливаться не будут. Хорошая новость заключается в том, что эти подготовительные мероприятия просты. Достаточно установить несколько обновлений.
Рекомендации с сайта Microsoft.
Перед установкой KB4519976 и/или KB4520003 Microsoft рекомендует установить KB4490628 и KB4474419. Также проверьте, что у вас установлены KB4516655 и (по собственному опыту) KB3133977.
При соблюдении этих условий установка KB4519976 и/или KB4520003 должна пройти в штатном режиме.
Этот «вторник обновлений» оказался не слишком богатым на устранённые уязвимости. Из потенциально опасных следует выделить уязвимости CVE-2019-1238 и CVE-2019-1239, связанные с тем, как VBScript обрабатывает объекты в памяти. Эксплуатируя данные уязвимости, злоумышленник может выполнить произвольный код в контексте текущего пользователя.
Очередная уязвимость (CVE-2019-1333) была найдена и в RDP. Проблема проявляется на стороне клиента и позволяет атакующему добиться удалённого выполнения кода. Однако для этого нужно убедить жертву подключиться к вредоносному серверу.
Несмотря на то, что в этом месяце не зафиксировано уязвимостей нулевого дня, девять багов получили статус критических. Поэтому с установкой обновлений всё таки лучше не тянуть.
Статьи по теме:
Комментарии: 8 к “Не устанавливаются KB4519976 и KB4520003 — решение проблемы”
KB4519976 не устанавливается, хотя все условия перед установкой выполнено. При чем это не на одном ПК. Так что не хватает еще чего-то.
Какой код ошибки? Запускается ли средство восстановления системы?
Код ошибки 800700B7. Начиная с августа, когда Майкрософт ввела подпись SHA-2, перестали устанавливаться ежемесячные пакеты обновлений. Пришлось их начинать скрывать.
Для корректной работы с SHA-2 нужны патчи, которые перечислены в статье. Я правильно понял, что на всех этих компьютерах они корректно установились? Других патчей Microsoft не предлагает. Способ лично успешно опробован в локальной сети с WSUS и десятками ПК.
Если вы распространяете обновления на ПК с WSUS, попробуйте для интереса скачать ежемесячный пакет и установить его на одной из машин вручную. Естественно, предварительно должны быть установлены все KB из этой статьи.
В целом, код 0x800700b7 является обобщённым. Как правило, он говорит о повреждённых системных файлах или о некорректных записях в реестре. Если вручную ежемесячный пакет установится успешно, очистите папку %WINDIR%SoftwareDistributionDownload, чтобы обновления с WSUS на компьютеры загрузились вновь.
Также можно использовать команду sfc /scannow, чтобы провести проверку и восстановление отсутствующих или повреждённых системных файлов.
Да требуемые патчи установились. Вручную пакеты KB4512506, KB4516065, KB 4524157, KB4519976 не устанавливаются при условии установленных патчей. Результат команды sfc /scannow: Защита ресурсов Windows не обнаружила нарушений целостности. Очистку папки SoftwareDistribution делал. Началось все с запуска средства восстановления системы после не установившихся KB4512506 и KB4512486.
Что самое интересное KB4520003 установилось, прилетев от WSUS. И ряд других обновлений тоже установилось. Не устанавливаются только Monthly Rollup.
Выполнил все указанные инструкции дважды с интервалом в месяц.
Чистил папку %WINDIR%SoftwareDistributionDownload, запускал sfc /scannow, устанавливал через центр обновления и скачивал из каталогов. Все тщетно. Указанные обновления уже установлены, а Monthly Rollup по-прежнему устанавливается до 100%, а затем откатывается с сообщением «Не удалось установить обновление.»
Думаю статьи в этом не виноват — просто Microsoft пытается принудить нас к установке W10.
Источник
Adblock
detector
After adding a Python path to my environment variable I ran into an [error 2147942402 (0x80070002) when launching ubuntu.exe that’s preventing me from launching Ubuntu in Windows terminal.
I don’t know what happened. Is my environment variable messed up?
I’m using Ubuntu 18.04 on Windows 10 via WSL2.
NotTheDr01ds
11.8k2 gold badges42 silver badges68 bronze badges
asked Aug 3, 2022 at 15:58
9
Finally I managed to fix this error just by adding a path related to Windows Apps [ C:UsersOSAppDataLocalMicrosoftWindowsApps ] to my user environment variables instead of a Python path added mistakenly.
Hope this will help someone else in the future because I searched a lot and didn’t find any fix to this error.
answered Aug 4, 2022 at 20:55
2
error 2147942402 is a «File not Found» in Windows.
So I would assume ubuntu.exe is not found.
Are you sure of the exe name? IIRC it should be wsl.exe -d Ubuntu-18.04
answered Aug 3, 2022 at 18:07
RinzwindRinzwind
288k39 gold badges561 silver badges701 bronze badges
2
У меня есть ряд различных запланированных задач, которые настроены на запуск некоторых исполняемых файлов, написанных на VB.Net. Когда они начинают работать, они почти всегда получают сообщение об ошибке, говорящее о том, что задача не запустилась, и ссылаются на это значение ошибки:
Дополнительные данные: Значение ошибки: 2147942402
Как я могу это исправить?
5 ответы
Я получал такое же сообщение об ошибке. Как указано в этот другой ответ, оказывается код ошибки 2147942402 на самом деле означает File Not Found.
Я программно создавал свое запланированное задание, и оказалось, что у меня была опечатка в пути к исполняемому файлу, который я указывал для запуска, и на самом деле его не существовало. Как только я исправил путь к файлу исполняемого файла, для запуска которого было настроено запланированное задание, все заработало, как и ожидалось.
Создан 09 фев.
У меня была такая же проблема, когда я пытался запускать веб-страницы в IE с помощью планировщика Windows.
Следуй этим шагам:
-Щелкните правой кнопкой мыши по задаче -> свойства.
-Перейдите на вкладку «Настройки», найдите «Если задача уже запущена, применяется следующее правило» в нижней части диалогового окна и установите для параметра DropDownList значение «Остановить существующий экземпляр».
— Перейдите на вкладку «Действия», отредактируйте задачу, в разделе «Программа/скрипт» выберите ПОЛНЫЙ ПУТЬ приложения, выполняющего вашу задачу (в моем случае я заменил iexplore.exe на C:Windowswinsxs…iexplore.exe)
Надеюсь, это поможет вам
ответ дан 26 апр.
Изменение разрешений, разных файлов или местоположений у меня не сработало. Мне пришлось создать новую задачу и отключить старую, и у меня это сработало. Должно быть, что-то было повреждено исходной задачей.
ответ дан 20 авг.
Я получил те же дополнительные данные: Значение ошибки: 2147942402. Для меня сработало решение: удалить задачу и создать новую, ту же самую, что была удалена. Вы также можете попробовать проверить пароль для пользователя во время выполнения задачи.
Создан 04 фев.
Я исправил эту ошибку, изменив «Выполнять независимо от того, вошел пользователь в систему или нет» на «Выполнять, только когда пользователь вошел в систему» на вкладке «Общие» задачи.
Вы должны быть действительным пользователем на вкладке «Общие» -> «Параметры безопасности» -> «При запуске задачи используйте следующую учетную запись пользователя:»
Создан 10 сен.
Не тот ответ, который вы ищете? Просмотрите другие вопросы с метками
windows
scheduled-tasks
or задайте свой вопрос.
I can’t believe this issue is here since 2009, but the error Background Intelligent Transfer Service service terminated with service-specific error 2147942402 is still a very common phenomenon. I used to have this error in conjunction with Automatic Updates on a Windows 2003 server and Windows XP client. And yet you may face it on Windows 10, 2016 or even 2019.
So here’s the original story.
I was running WSUS in my domain, but the updates didn’t arrive. A quick investigation resulted in A LOT OF ERRORS in the event viewer. For a couple of days, the following error had returned every one or two minutes or so!
The Background Intelligent Transfer Service service terminated with service-specific error 2147942402 (0x80070002).
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 3/31/2009
Time: 3:48:14 PM
User: N/A
Computer: computer name
Description:
The Background Intelligent Transfer Service service terminated with service-specific error 2147942402 (0x80070002).
In my case, I couldn’t get the Background Intelligent Transfer Service started again. The following error messages showed up every time:
Windows could not start the Background Intelligent Transfer Service on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -2147024893.
If you see the same error in your event log (event 7024), you should know that there are a lot of possible solutions. Now, I do not feel embarrassed to tell you that I checked almost every solution available on the internet and spent quite some time on this issue. So, because of all the effort I have put into this problem, I decided to sum up all the solutions for you I’ve tried. Hopefully, it will help you solving this BITS error.
After each step, try to start the BITS service. If it doesn’t start successfully, just continue with the next step
Step 1:
Open services.msc and check that the following services are set to start Manual or Automatic:
Terminal Services
Remote Procedure Call (RPC)
System Event Notification
Windows Management Instrumentation Driver Extensions
COM+ Event System
DCOM Server Process Launcher
Also make sure that service Workstation is Running. And next try to start the BITS service.
Fixed it? Leave a comment
Problem not fixed yet? Continue to step 2!
Step 2:
Delete the Downloader folder. You can find the downloader folder in the following location:
“C:Documents and SettingsAll UsersApplication DataMicrosoftNetworkDownloader”
The Application Data folder is hidden by default, so if you don’t see the Application Data folder, go to folder options and check the option Show Hidden Files and Folders
Next try to start the BITS service.
Fixed it? Leave a comment
Problem not fixed yet? Continue to step 3!
Step 3:
Delete all content of the SoftwareDistribution folder (do NOT delete the folder itself, only the content!). You can find the downloader folder in the following location:
“C:WindowsSoftwareDistribution”
Next try to start the BITS service.
Fixed it? Leave a comment
Problem not fixed yet? Continue to step 4!
Step 4:
Register 8 dll files that are directly connected to BITS. Some applications remove or corrupt the dll files which cause the BITS service to fail. To register the dll files easily, do the following:
- Open Notepad
- Copy and paste the following entries into the text document.
regsvr32 oleaut32.dll
regsvr32 jscript.dll
regsvr32 vbscript.dll
regsvr32 msxml.dll
regsvr32 softpub.dll
regsvr32 wintrust.dll
regsvr32 initpki.dll
regsvr32 cryptdlg.dll - Save this file as a batch file
– click on save as
– open the drop down box at the bottom to read save as file type: all files
– name of file: BITS_fix.bat (the .bat is creating a batch file)
– run the BITS_fix.bat (double-click)
Next try to start the BITS service.
Fixed it? Leave a comment
Problem not fixed yet? Continue to step 5!
Step 5:
Deregister and reregister the qmgr.dll and qmgrprxy.dll. To register these files, open a command prompt and type the following:
regsvr32 qmgr.dll [ENTER]
regsvr32 qmgrprxy.dll [ENTER]
I hope you had success. If not, feel free to post a comment. You’re not the only one who’s struggling with BITS
Oh, by the way, if you DID have success, feel free to post a comment too. I love “thank you”-messages
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:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2
Если я запускаю эту же команду move C:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2из командной строки Windows, она работает нормально.
Чего мне не хватает?
Ответы:
Как отметил Райан Райс, 2147942402 переводится как «Файл не найден», что является очень подходящим ответом. Попробуйте нажать Win + R, введите «move» и нажмите enter — это интерактивный эквивалент того, что ваша задача не справляется.
Причина в том, что MOVEэто не программа, а встроенная команда в cmd.
Должен быть:
Программа: "cmd.exe"
Аргументы:"/c move C:WindowsTemp*.foo E:Foo_blah_blah_blah_blahFoo2"
Причина в том, что задание настроено на удаление, если не запланировано повторное выполнение. Это настраивается на вкладке «Настройки». Удаление Задачи выполняется во время истечения Триггера, который запускает Задачу. Если время истечения триггера точно совпадает со временем запуска триггера, может (случайно) произойти, если Задание будет удалено за несколько секунд до срабатывания триггера. Это вызывает событие 101 с кодом причины 2147942402. Решение состоит в том, чтобы установить время истечения триггера на 1 мин позже времени начала триггера.
Может быть, это проблема пробелов в строке порядка заказа:
C: Program Files Wireshark Wireshark.exe -i1 -k FAILS
«C: Program Files Wireshark Wireshark.exe» -i1 -k ОК