Task Scheduler did not start monthly task after daylight saving change

Question

Hello,

we have a problem with the task schedule in Windows Server 2019 and the summer/winter time change. Our monthly scheduled tasks did not start anymore, but the daily or weekly tasks start as scheduled without any problems. A manual start from the task scheduler does not work either.
The code 0x800710E0 is displayed as Last Run Result and the following error message is displayed in the event log

Log Name: Microsoft-Windows-TaskScheduler/Operational
Source: Microsoft-Windows-TaskScheduler
Date: 01.04.2021 08:00:03
Event ID: 153
Task Category: Missed task start rejected
Level: Warning
Keywords:
User: SYSTEM
Computer: xxx.xxx.xxx
Description:
Task Scheduler did not launch task "\xxx" as it missed its schedule. Consider using the configuration option to start the task when available, if schedule is missed.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TaskScheduler" Guid="{DE7B24EA-73C8-4A09-985D-5BDADCFA9017}" />
<EventID>153</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>153</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2021-04-01T06:00:03.509187200Z" />
<EventRecordID>2615724</EventRecordID>
<Correlation />
<Execution ProcessID="860" ThreadID="18872" />
<Channel>Microsoft-Windows-TaskScheduler/Operational</Channel>
<Computer>xxx.xxx.xxx</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData Name="MissedTaskRejected">
<Data Name="TaskName">\xxx</Data>
</EventData>
</Event>

Has anyone experienced this problem and solved it? I would be very happy for any tips.

Many thanks
Robert

Answer 1

HI @Robert

This seems a bug that has been know and confirmed by Microsoft for over a year, One way would be delete the job and recreate it.

For error code 0x800710E0, please see : https://appuals.com/fix-operator-administrator-refused-request-error-0x800710e0/

Other reference article:
When system time springs forward (DST change in spring), the first scheduled task after the time change does not run.

Best Regards
Karlie

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hello Karlie,

thank you for the solutions. I have already seen these articles, but they do not solve my problem. I have made or tested all the settings.

• General, When running the task, use the following user account
  --> different users
• General, Run whether the user is logged on or not
  --> selected
• General, Run with highest privileges
  --> activated
• Power, Start the task only if the computer is on AV power
  --> deactivated
• Settings, Run task as soon as possible after a scheduled start is missed
  --> activated
• Settings, Stop the task if it runs longer than
  --> activated
• Permissions
  --> User ist local admin and has full control on needed all files

The problem still exists. However, as soon as I have used another user with the same rights, I can use the intended user again and it works again until the next time change.

Tasks that run daily, weekly or every x minutes work without any problems, with still the same user. It only affects the tasks that run once on day X (1st, 2nd, etc) in the month.

Best Regards
Robert

Answer 3

Hi,

I have tested all the settings/configurations mentioned in the links, because we have had the problem for a few time changes. None of them changed/improved the behaviour. Currently, the monthly tasks are working "error-free" again.

The weird thing about the whole thing is that it only affects the monthly tasks. However, after changing the user, without the task having been started once, it works again with the original user without errors until the next changeover from winter to summer time or summer to winter time. All other tasks (every few minutes, daily, weekly) that are executed with the same user work without errors before and after the time changes.

All in all, I now have to wait for the next time changeover to check whether the phenomenon occurs again then.

Perhaps someone else has a new/different approach to the problem described. I am open to any ideas/tips.

Thank you for your support

Answer 4

Hi,

checking the "Synchronize across time zones" checkbox solved the same problem for us.

Best Regards
Tomas

Answer 5

Hi,

yes, we tested it with and without. But the same phenomenon. The problem concerns only the monthly jobs. All others (hourly, daily, etc.) work without errors.