question

rainmakers-3202 avatar image
0 Votes"
rainmakers-3202 asked Jemshut-2667 published

Scheduled task EventID 153 followed by many 322

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

windows-server-2016
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

rainmakers-3202 avatar image
0 Votes"
rainmakers-3202 answered

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.



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ElevenYu-MSFT avatar image
0 Votes"
ElevenYu-MSFT answered rainmakers-3202 commented

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.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Server 2016 OS Version 1607 Build: 14393.3930

The start date is in the past. However after manually running the schedule is working once again.
For the security updates I am at Sept 2020.

Unfortunately, I do not have a way to replicate the issue on demand.

Most of all I'm trying to understand why the task thought there was an instance already running, and even if it thought the job was running why it didn't self resolve after the run longer than time had passed.

0 Votes 0 ·
ElevenYu-MSFT avatar image
0 Votes"
ElevenYu-MSFT answered rainmakers-3202 commented

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://docs.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.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for the info.
The Trigger we currently have for the job is a one time with a past historical date. It has the option "Repeat task every:" 15 minutes in our case and set to run indefinitely. The job starts as expected even across server reboots.
So what setting can be set to recover from the problem on the next scheduled run without human intervention?

0 Votes 0 ·
ElevenYu-MSFT avatar image
0 Votes"
ElevenYu-MSFT answered ElevenYu-MSFT commented

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.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I should be able to recreate the job. But, are you suggesting the problem is related to the start date being in the past? This job is intended to run for years without needing to be modified.

I'm trying to understand the logic behind recreating the job, and how it would solve a problem created by VMware snapshots.

0 Votes 0 ·

Hi,

Recreating the task is just a possible method that you can test to resolve event 153. And if your issue is caused by VMware snapshots, you might need to seek help from VMware side.

0 Votes 0 ·
Jemshut-2667 avatar image
0 Votes"
Jemshut-2667 answered Jemshut-2667 published

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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.