Scheduled task EventID 153 followed by many 322

Question

I have a Windows 2016 server That has a scheduled task that runs every 15 minutes that had an EventID 153 "Task Scheduler did not launch task"........" as it missed its schedule. Consider using the configuration option to start the task when available, if schedule is missed." Then on subsequent runs had EventID 322 "Task Scheduler did not launch task".... " of the same task is already running."

At this time I suspect the original event 153 is due to an issue with VMWare snapshot . However the subsequent EventID 322 is the event I don't understand why it occurred until the task was run manually via right click. I checked and it did not appear the task was still running in the scheduled task window, nor any process running in task manager for that user. Even if the scheduled job was still running we had the job set to stop if it ran longer than 1 day in the scheduled task's config, in yet the errors persisted over 24 hours. If in the early hours of the morning if one job fails I'm not very concerned, but would expect the next scheduled run to start on schedule.

It doesn't seem that "Run task as soon as possible after a scheduled start is missed" would fix the issue of the job not running the next scheduled time. But, what am I missing?
Thanks in advance

Answer 1

Thanks for the suggestion about VMWare, but my group is not responsible for the VMWare infrastructure. Basically we've been told to work around the issue from management.
With that in mind we did some more searching and found a system event of fixing the clock on the system. So we believe that something in the snapshotting process caused the clock to need adjustment. Thus this caused the issue with the task failing to start. Still thought it was interesting the symptom of the task thinking it is still running when it is not. But, with the idea of needing to adjust the system clock to duplicate we tried a few tweaks with the scheduled task the options “Stop the existing instance” and “Run task as soon as possible after a scheduled start is missed”.  Initial tests have been successful but time will tell.

Last remaining trick is to see if the vendor will support our change.

Answer 2

Hi,

What's the OS version of your server? Please run "winver" in CMD to show the version imformation. Have you installed all latest security updates?

Please check if you set a past time as the start date of the task. If so, try to recreate the task with a future date as the start date.
Also, you can try to check "Synchronize across time zones" and see if the issue cound be resolved or not.

Thanks,

Eleven

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

Answer 3

Hi,

The event 153 should because you set a past time as the start date.

And for Event 322, I think it might be a by-design behavior as below article mentioned event 322 will occur when the previous task instance was running longer than expected.

https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc727011(v=ws.10)?redirectedfrom=MSDN

Thanks,
Eleven

----------

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

Answer 4

Hi,

If possible, we suggest that you might need to recreate this scheduled task with a future date, such as several minutes later than you create it, and keep all other settings the same.

Thanks,

Eleven

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

Answer 5

The IO operation at logical block address 0x6a1be8 for Disk 1 (PDO name: \Device\MPIODisk0) was retried.

• System
  • Provider
  [ Name] Disk
  • EventID 153
  [ Qualifiers] 32772 Level 3 Task 0 Keywords 0x80000000000000
  • TimeCreated
  [ SystemTime] 2021-06-27T06:51:28.120799300Z EventRecordID 17902 Channel System Computer src06f8511f6.sec.local Security

• EventData \Device\Harddisk1\DR1
  0x6a1be8
  1
  \Device\MPIODisk0
  0F01040004002C0000000000990004800000000000000000000000000000000000000000000000000000048A

---

Binary data:

In Words

0000: 0004010F 002C0004 00000000 80040099
0010: 00000000 00000000 00000000 00000000
0020: 00000000 00000000 8A040000

In Bytes

0000: 0F 01 04 00 04 00 2C 00 ......,.
0008: 00 00 00 00 99 00 04 80 .... ..
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 04 8A