There is a scheduled task that executes a script. It was running fine until one day it started to fail with ‘Task Scheduler failed to start «Task» task for user «domain account». Additional Data: Error Value: 2147944309.’ It failed on a Friday, ran on a Saturday, then began failing daily after that. My research on this found that 2147944309 means the account is either disabled or locked out. I double checked the account and it was neither. Server is Windows 2012. It’s an RDS server so it reboots every morning. After it reboots a warning message shows in history for the task «Task Scheduler did not launch task «Task» as it missed its schedule. Consider using the configuration option to start the task when available, if schedule is missed.»
What I was able to determine:
-
account is not locked or disabled
-
account is in the administrator group on the server
-
permissions are correct on the script
-
set it to run with highest privileges
-
able to manually kick off the task
-
the task is in a folder under Task Scheduler Library
-
created a test task to run notepad under the same account in the folder. It did not run
-
created a test task in a test folder under Task Scheduler Library to run notepad under the same account. It did not run
-
created a test task directly Task Scheduler Library to run notepad under the same account. It ran
-
moved the task under directly under Task Scheduler Library.
The scheduled task kicked off for four days in a row and then began failing with the same error. Yesterday, I set the option to restart every minute three times if it fails. It didn’t execute a second or third time after failing. Any ideas what the heck is going with this?
There is a scheduled task that executes a script. It was running fine until one day it started to fail with ‘Task Scheduler failed to start «Task» task for user «domain account». Additional Data: Error Value: 2147944309.’ It failed on a Friday, ran on a Saturday, then began failing daily after that. My research on this found that 2147944309 means the account is either disabled or locked out. I double checked the account and it was neither. Server is Windows 2012. It’s an RDS server so it reboots every morning. After it reboots a warning message shows in history for the task «Task Scheduler did not launch task «Task» as it missed its schedule. Consider using the configuration option to start the task when available, if schedule is missed.»
What I was able to determine:
-
account is not locked or disabled
-
account is in the administrator group on the server
-
permissions are correct on the script
-
set it to run with highest privileges
-
able to manually kick off the task
-
the task is in a folder under Task Scheduler Library
-
created a test task to run notepad under the same account in the folder. It did not run
-
created a test task in a test folder under Task Scheduler Library to run notepad under the same account. It did not run
-
created a test task directly Task Scheduler Library to run notepad under the same account. It ran
-
moved the task under directly under Task Scheduler Library.
The scheduled task kicked off for four days in a row and then began failing with the same error. Yesterday, I set the option to restart every minute three times if it fails. It didn’t execute a second or third time after failing. Any ideas what the heck is going with this?
Как прочитать код ошибки?
Во время настройки одного из заданий для планировщика, в момент сохранения, появилась ошибка. Ошибка имела следующий код 2147944309. Абсолютно не информативно.
Предлагаю хинт — после трех манипуляций без всякого гугла ошибка станет чуть более понятной. Потребуется два инструмента: калькулятор в режиме «Программист» и утилита командной строки. Скармливаем калькулятору номер ошибки и переводим его в шестнадцатеричную систему (настоящие гуру могут не запускать калькулятор, а проделать операцию в уме 🙂 ). Получили 80070775. Первый четыре цифры указывают на тип ошибки. Вторые четыре на номер ошибки. Нас интересует номер 0775. Не забываем, что это шестнадцатеричная система. При помощи калькулятора переводим в десятичную:
0775(HEX)=1909(DEC)
Теперь нам понадобится командная строка.
Ввожу:
Получаю ответ:
Учётная запись пользователя заблокирована и не может быть использована для входа в сеть
Безликий код стал более читаемой ошибкой.
(с) ds0m
Запись опубликована в рубрике IT с метками Microsoft, windows 2008. Добавьте в закладки постоянную ссылку.
- Remove From My Forums
-
Question
-
I created a basic task in Windows 2008 R2 Standard.
I set d:workprogram1mywork.bat to run each day, and I set the working dir to d:workprogram1
Then I set the user account to run the task as MYDOMAINServerScheduler
When I inserted the password I got an error, since the password was incorrect.After this, whatever I do I am not asked for a new password prompt. Each time I try press OK in the Properties I get the following error:
An error has occurred for task MyTask. Error message: The following error was reported: 2147944309.
Answers
-
In order to change the credentials you will have to «switch users»
This will allow you to use the same user but enter the correct password.
David Bliss
-
Marked as answer by
Monday, March 1, 2010 9:17 AM
-
Marked as answer by