task scheduler doesn't start delayed task

[Guest]

Hi. I have a simple console-application which I plan to run every day on 6
am. So I added this task to the task planer. Since I don't know if the
computer has already been turned on at 6 o'clock, I checked "run task as soon
as possible after a missed start" (I hope the translation is correct and you
can imagine what I mean), which is exactly what I want.

But this simple doesn't happen. This morning for example, I turned on the
computer on about 7 o'clock and the application was not started:
Last time running: 2007-07-19 06:00:00
Next time running: 2007-07-21 06:00:00

Any idea about that? I got no entry in the task schedulers event-log, so I
got no idea what to do?!

My additional settings are:
- run only if user is logged on
- I didn't check anythingin the conditions-page
- task can be started on demand + run task as soon as possible after a
missed start + end task if it runs longer then 3 days

 

[Guest]

Does the task require elevated permission to run? Try checking "run with
highest privileges".

 

[Jimmy Brush]

Hello,

Can you export the task to a file, open the file, copy the contents and
paste it into a reply?

Also, do you get any errors in the log when you click on the history tab
on the properties screen for the task?

- JB

 

[Guest]

Thanks for your replys!

Does the task require elevated permission to run? Try checking "run with
highest privileges".

I just added this - lets see if it works.

Can you export the task to a file, open the file, copy the contents and
paste it into a reply?

Here it comes:
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2"
xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Date>2007-07-16T10:47:06.1131602</Date>
<Author>MyComputer\MyUser</Author>
<Description>Run every day at 6 o'clock</Description>
</RegistrationInfo>
<Triggers>
<CalendarTrigger id="81ca0caf-34e6-49d7-9d4b-556dd37f9dae">
<StartBoundary>2007-07-16T06:00:00</StartBoundary>
<Enabled>true</Enabled>
<ScheduleByDay>
<DaysInterval>1</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>MyComputer\MyUser</UserId>
<LogonType>InteractiveToken</LogonType>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
<Settings>
<IdleSettings>
<Duration>PT10M</Duration>
<WaitTimeout>PT1H</WaitTimeout>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>true</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>P3D</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>G:\Debug\MyConsoleApp.exe</Command>
<Arguments>-a</Arguments>
</Exec>
</Actions>
</Task>

 

[Guest]

I forgot: There is no entry at all in the log since the last time the task
was started.

 

[Guest]

Does the task require elevated permission to run? Try checking "run with

highest privileges".

Still doesn't start, and still no entries in the log.

 

[Jimmy Brush]

I forgot: There is no entry at all in the log since the last time the task
was started.

Hello,

I can confirm that I get the same experience on my machine - task does
not start, no log entries.

I tried changing some different settings as well and I could not get the
behavior alluded to in the help file where it would start the task after
a delay of 10 minutes if it missed the start time, "for instances, if
the computer was turned off".

Unless I am misunderstanding something (entirely possible), this appears
to be a bug...

I will file a report with Microsoft and see what comes of it.

- JB

 

[Guest]

Unless I am misunderstanding something (entirely possible), this appears

to be a bug...

I will file a report with Microsoft and see what comes of it.

Thanks for your confirmation and the report. Actualy, it worked for me
exactly one time on thuesday, but wednesday and today: not effect, altought I
didn't change anything.

Please place the URL of the report so we could vote for it.