------
<Task version="1.3" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Author>Alex</Author>
<URI>\stop_task</URI>
</RegistrationInfo>
<Triggers>
<CalendarTrigger>
<StartBoundary>2022-04-08T01:35:00</StartBoundary>
<Enabled>true</Enabled>
<ScheduleByDay>
<DaysInterval>1</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>S-1-5-18</UserId>
<RunLevel>LeastPrivilege</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>StopExisting</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>false</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>
<UseUnifiedSchedulingEngine>true</UseUnifiedSchedulingEngine>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT72H</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>SC</Command>
<Arguments>stop myservice</Arguments>
</Exec>
<Exec>
<Command>powershell</Command>
<Arguments>.\main.ps1 -app myservice -archDest 'E:\Archive'</Arguments>
<WorkingDirectory>D:\Scripts\</WorkingDirectory>
</Exec>
</Actions>
</Task>
Launch request ignored, instance already running with code 0x800710E0
Hi,
We have the issue with task scheduller that returned a warning with id 322 (Launch request ignored, instance already running) and it missed the task.
We use Windows Server 2019 Standard (64 bit) on physical server. And before the issue, we carried out technical work with the server in a time covering task running time. So, the task was not started because the server was in service mode. The screenshot below shows that the task starts every day at 1:35. On the 11th there were works from 1:10 until 2:35 and at 2:47 the scheduler returned that the start (1:35) was skipped (event 153) - This is OK. But the next day we get the event 322. Why did this happen?
As you can see, there are no other events between the missed launch on the 11th and the problem on the 12th. Moreover, the return code for problematic tasks was 0x800710E0. And it affects only to those tasks that intersect with the time of work.
When we start it manually - all OK, the issue resolving.
Additionaly i attached xml of the task below.
Many thanks Alex
Windows for business Windows Server User experience Other
1 answer
Sort by: Most helpful
-
Alexander 0 Reputation points
2023-07-12T23:23:12.3566667+00:00