Task Scheduler IGNORES duration

  • Thread starter Thread starter createwindow@gmail.com
  • Start date Start date
C

createwindow@gmail.com

Guest
OK, I have a sched. task in Windows Server 2008 64 Bit RTM Enterprise,
that fires (sorry, I mean sexy new term "Triggers") on second Thursday
of every month, then repeats every hour. However, although I ask it to
stop after 6 hours,it keeps going & going up to 8 hours now and
counting!!!!!!

I am seeing posts on this in Vista groups also (no surprises there -
same kernel). So, can MS admit this is a bug and advise when this will
be dealt with please?

Oh the pain, the pain. (Dr. Smith)

Thanks.
 
Re: Task Scheduler IGNORES duration


<createwindow@gmail.com> wrote in message
news:c73e2125-378f-4846-aa4b-608c30989056@8g2000hse.googlegroups.com...
> OK, I have a sched. task in Windows Server 2008 64 Bit RTM Enterprise,
> that fires (sorry, I mean sexy new term "Triggers") on second Thursday
> of every month, then repeats every hour. However, although I ask it to
> stop after 6 hours,it keeps going & going up to 8 hours now and
> counting!!!!!!
>
> I am seeing posts on this in Vista groups also (no surprises there -
> same kernel). So, can MS admit this is a bug and advise when this will
> be dealt with please?
>
> Oh the pain, the pain. (Dr. Smith)
>
> Thanks.

In view of the very large number of Windows installations it is a risky
step to declare this behaviour a "bug" and demand from Microsoft to
admit it and fix it. It is far more likely that the issue is due to a lack
of
understanding. To keep the egg away from one's face it would be more
prudent to ask "why" the Task Scheduler behaves like this.

The simple explanation is: The "Duration" parameter does NOT
control the time a scheduled task is allowed to run. It defines the
number of hours during which repetitive tasks are launched. If you
specify a task to run once every hour, starting at 6 am with a duration
of 5 hours, then the task will be launched at 6, 7, 8, 9 and 10 am,
and perhaps at 11am (I'm not sure). This is exactly as designed,
hence no bug and no fixing required.

You need to launch a separate task to kill a scheduled process
that takes more time to finish than expected.
 
Re: Task Scheduler IGNORES duration

Dear Pegasus.

This *is* a bug. Try it yourself. No egg (yet anyway) on my face. :-)

My vbs task checks for a USB drive online with the correct drive
(volume) letter and takes milliseconds to run - then emails me if I
have the wrong drive online for my monthly backup. (Or praises me that
I have powered up the correct drive :-).

I have rebuilt this task twice and, know what I am doing (I think). I
have set the darn thing as per the skimpy help instructions. I also
selected to elevate the UAC privileges ett-set-er-ahhhhhh. Ad
nauseum....

The darn thing won't stop!

The technology of the new task sched. service is way cool. I can see
that. Much better than downlevel Win 2003 etc. task manager services.

I would be interested if you could verify it happens to you too. Make
a simple vbs that - say - writes the time Now() to a file and exits.
Get it to start on the 2nd Thursday of this month, start it a 10 AM or
whatever and repeat every hour for 2 hours.

I'll bet it will ignore the "for a duration of:" 2 Hours

Gosh, I just had an idea! Boing! I'll run up one of my Vista
business VM's on a Hyper-V machine (that I use for deveopment) and do
a controled test. :-)

Btw I would *love* to have that egg on my face as that would mean this
darn problem would be solved. So, if I'm missing something - please
advise.

Time for bed in my TZ.

Thanks for you reply.
Looking fwd to your results/reply.

Cheers,
CreateWindow
 
Re: Task Scheduler IGNORES duration

See below.

<createwindow@gmail.com> wrote in message
news:955142b6-cc27-4abe-a55f-a67c3ba49463@79g2000hsk.googlegroups.com...
> Dear Pegasus.
>
> This *is* a bug. Try it yourself. No egg (yet anyway) on my face. :-)
>
> My vbs task checks for a USB drive online with the correct drive
> (volume) letter and takes milliseconds to run - then emails me if I
> have the wrong drive online for my monthly backup. (Or praises me that
> I have powered up the correct drive :-).
>
> I have rebuilt this task twice and, know what I am doing (I think). I
> have set the darn thing as per the skimpy help instructions. I also
> selected to elevate the UAC privileges ett-set-er-ahhhhhh. Ad
> nauseum....
>
> The darn thing won't stop!

> The technology of the new task sched. service is way cool. I can see
> that. Much better than downlevel Win 2003 etc. task manager services.
>
> I would be interested if you could verify it happens to you too. Make
> a simple vbs that - say - writes the time Now() to a file and exits.
> Get it to start on the 2nd Thursday of this month, start it a 10 AM or
> whatever and repeat every hour for 2 hours.
>
> I'll bet it will ignore the "for a duration of:" 2 Hours

*** I scheduled a task to run once every 2 minutes with a duration
*** of 5 minutes. I also ticked the box "If the task is still running,
*** stop it at this time". Here is what happened:
***
*** On its first invocation the job kept running. The second instance
*** got launched (as shown by the Task Scheduler) and generated the
*** following log entry: ' The task was forced to close since its execution
*** time exceeded the configured maximum. You may want to go
*** to the Settings page and increase the "Stop the scheduled task
*** after" time.' When "duration" time was up (5 minutes), the first
instance
*** got killed.
***
*** How did I test it? Very simple - with this primitive batch
*** file that I scheduled to run under my foreground account:
*** @echo off
*** echo Instance #1
*** pause
*** In the waiting time between the first and the second run
*** I manually changed #1 to #2 etc.
***
*** In my initial reply I was partly wrong and partly right. The
*** "duration" parameter permits repetitive tasks to start during
*** the span defined by "duration". The "Stop" box causes tasks
*** to stop after "duration" time is up, as measured from the
*** very first start time.
*** I suggest you test your setup with a batch file like the one
*** above, then watch the job output and examine the Task Scheduler
*** log file and the event viewer. After this is clear, test it with
*** your real job.

> Gosh, I just had an idea! Boing! I'll run up one of my Vista
> business VM's on a Hyper-V machine (that I use for deveopment) and do
> a controled test. :-)
>
> Btw I would *love* to have that egg on my face as that would mean this
> darn problem would be solved. So, if I'm missing something - please
> advise.
>
> Time for bed in my TZ.
>
> Thanks for you reply.
> Looking fwd to your results/reply.
>
> Cheers,
> CreateWindow
 
Re: Task Scheduler IGNORES duration


<createwindow@gmail.com> wrote in message
news:955142b6-cc27-4abe-a55f-a67c3ba49463@79g2000hsk.googlegroups.com...
> Dear Pegasus.
>
> This *is* a bug. Try it yourself. No egg (yet anyway) on my face. :-)
>
> My vbs task checks for a USB drive online with the correct drive
> (volume) letter and takes milliseconds to run - then emails me if I
> have the wrong drive online for my monthly backup. (Or praises me that
> I have powered up the correct drive :-).
>
> I have rebuilt this task twice and, know what I am doing (I think). I
> have set the darn thing as per the skimpy help instructions. I also
> selected to elevate the UAC privileges ett-set-er-ahhhhhh. Ad
> nauseum....
>
> The darn thing won't stop!
>
> The technology of the new task sched. service is way cool. I can see
> that. Much better than downlevel Win 2003 etc. task manager services.
>
> I would be interested if you could verify it happens to you too. Make
> a simple vbs that - say - writes the time Now() to a file and exits.
> Get it to start on the 2nd Thursday of this month, start it a 10 AM or
> whatever and repeat every hour for 2 hours.
>
> I'll bet it will ignore the "for a duration of:" 2 Hours
>
> Gosh, I just had an idea! Boing! I'll run up one of my Vista
> business VM's on a Hyper-V machine (that I use for deveopment) and do
> a controled test. :-)
>
> Btw I would *love* to have that egg on my face as that would mean this
> darn problem would be solved. So, if I'm missing something - please
> advise.
>
> Time for bed in my TZ.
>
> Thanks for you reply.
> Looking fwd to your results/reply.
>
> Cheers,
> CreateWindow

Here is a better version of this batch file. It does not require
modification in between jobs.
@echo off
echo Time = %time%
pause
Further tests show that the Task Scheduler will not launch a subsequent
job if the previous job is still running.
 
Re: Task Scheduler IGNORES duration

Dear Pegasus,

I did a test on Vista Business and Server 2008 x64 and sure enough the
task stopped triggering based on "start every minute" for a "duration
of 3 minutes". However the Next Run Time is _every_ 'next' minute.
Just that when the 4th minute, 5th minute etc. comes around 'nothing
happens' or is logged which is good. But the Next Run Time increments
to the next minute. I would have thought the "Next Run Time" would be
next month as I am triggering on 2nd Friday of every month.

My original backup script is still running at 2 mins past the hour -
sending me emails - every hour totally ignoring the 6 hour limit I
placed in the duration. Driving me nuts! :-(

So, it could be a 64 bit problem only? I'll need to do some more
testing. Could be a 6 hour problem?? I'll post results - could take
awhile....

Btw my original backup check script (because its been running so long)
is now complaining that its not the correct day for backups! :-) Cute
'eh I forgot I wrote that part into the vbs. :-)

The echo stuff is nice and simple - but the 'pause' needs to be hit-
any-key'd to get the task to exit. Double starting has never been a
problem as 500 Ms is all the time my script takes to run.

**Stopping the task triggering and running is the only problem.**

This is my test code: Called test.vbs

'---- Start Code ------

Option Explicit

Dim fso, ts, Filename
Const ForReading = 1, ForWriting = 2, ForAppending = 8

Filename = "c:\util\Tardis.txt"

Set fso = CreateObject("Scripting.FileSystemObject")
Set ts = fso.OpenTextFile(Filename, ForAppending, True)
ts.Writeline(Now())
ts.Close
Set ts = Nothing
Set fso = Nothing

'---- End Code ------

As I said it worked in the time scale of minutes (but has a stupid
"next run time" - should be NEXT MONTH).

So, will it work in the 6 hour timeframe??

Lets see,

Cheers
CreateWindow

http://mymessagetaker.com
 
Re: Task Scheduler IGNORES duration


<createwindow@gmail.com> wrote in message
news:78331fdf-965c-46bb-a5cf-dea2750f4f52@b1g2000hsg.googlegroups.com...
> Dear Pegasus,
>
> I did a test on Vista Business and Server 2008 x64 and sure enough the
> task stopped triggering based on "start every minute" for a "duration
> of 3 minutes". However the Next Run Time is _every_ 'next' minute.
> Just that when the 4th minute, 5th minute etc. comes around 'nothing
> happens' or is logged which is good. But the Next Run Time increments
> to the next minute. I would have thought the "Next Run Time" would be
> next month as I am triggering on 2nd Friday of every month.
>
> My original backup script is still running at 2 mins past the hour -
> sending me emails - every hour totally ignoring the 6 hour limit I
> placed in the duration. Driving me nuts! :-(
>
> So, it could be a 64 bit problem only? I'll need to do some more
> testing. Could be a 6 hour problem?? I'll post results - could take
> awhile....
>
> Btw my original backup check script (because its been running so long)
> is now complaining that its not the correct day for backups! :-) Cute
> 'eh I forgot I wrote that part into the vbs. :-)
>
> The echo stuff is nice and simple - but the 'pause' needs to be hit-
> any-key'd to get the task to exit. Double starting has never been a
> problem as 500 Ms is all the time my script takes to run.
>
> **Stopping the task triggering and running is the only problem.**
>
> This is my test code: Called test.vbs
>
> '---- Start Code ------
>
> Option Explicit
>
> Dim fso, ts, Filename
> Const ForReading = 1, ForWriting = 2, ForAppending = 8
>
> Filename = "c:\util\Tardis.txt"
>
> Set fso = CreateObject("Scripting.FileSystemObject")
> Set ts = fso.OpenTextFile(Filename, ForAppending, True)
> ts.Writeline(Now())
> ts.Close
> Set ts = Nothing
> Set fso = Nothing
>
> '---- End Code ------
>
> As I said it worked in the time scale of minutes (but has a stupid
> "next run time" - should be NEXT MONTH).
>
> So, will it work in the 6 hour timeframe??
>
> Lets see,
>
> Cheers
> CreateWindow
>
> http://mymessagetaker.com

You appear to miss the purpose of the "Pause" command. It is
there to cause the task not to end by itself. You should therefore
NOT respond to it but just leave it there on the screen. When
expiry time comes along, it is supposed to disappear - it certainly
does on my machines.

I cannot comment on your own task that you claim keeps on
sending you EMails, because I have not seen it. The way to
debug such issues is to start nice and simple - e.g. by using the
batch file I suggested - then build up to the real thing. In other
words, try to walk before you run. If the Task Scheduler ends
the test batch file after the expiry of "duration" but does not end
your own job then you obviously need to examine your own
job in more detail.
 
Re: Task Scheduler IGNORES duration

Dear Pego,

I *know* what pause does. My scripts do work and exit after 100
milliseconds or much less.

They are not running a big backup job or somthing like that. See
script above - simple right....

I did more tests and so far the above SIMPLE vbs runs perfectly. (This
is the walking part before I run).

It runs for every minute for 5 minutes (duration) then stops. Now
thats excellent.

BUT if I set it to run every hour for a duration of 6 hours - it DOES
NOT STOP "triggering" every hour after 8 hours now it still
triggers!!!!!!!!!!!!
It just wont clock off and give up & go home to its wife.

This may still be an x64 Server 2008 bug - I'll try Vista 32 bit
tomorrow.

On the pain, the pain.

CW
PS: Can you run the script above to run every hour & set a 2 hour
duration and see if it NEVER stops "triggering". Then you will finally
understand.
Thanks.
 
Re: Task Scheduler IGNORES duration

There is no script "above".


<createwindow@gmail.com> wrote in message
news:b178f87d-6638-4c5a-8e99-115831a718e8@z66g2000hsc.googlegroups.com...
> Dear Pego,
>
> I *know* what pause does. My scripts do work and exit after 100
> milliseconds or much less.
>
> They are not running a big backup job or somthing like that. See
> script above - simple right....
>
> I did more tests and so far the above SIMPLE vbs runs perfectly. (This
> is the walking part before I run).
>
> It runs for every minute for 5 minutes (duration) then stops. Now
> thats excellent.
>
> BUT if I set it to run every hour for a duration of 6 hours - it DOES
> NOT STOP "triggering" every hour after 8 hours now it still
> triggers!!!!!!!!!!!!
> It just wont clock off and give up & go home to its wife.
>
> This may still be an x64 Server 2008 bug - I'll try Vista 32 bit
> tomorrow.
>
> On the pain, the pain.
>
> CW
> PS: Can you run the script above to run every hour & set a 2 hour
> duration and see if it NEVER stops "triggering". Then you will finally
> understand.
> Thanks.
>
>
 
Re: Task Scheduler IGNORES duration

On Jul 11, 11:24 pm, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:
> There is no script "above".
>
Here it is again...

This is my test code: Called test.vbs


'---- Start Code ------


Option Explicit


Dim fso, ts, Filename
Const ForReading = 1, ForWriting = 2, ForAppending = 8


Filename = "c:\util\Tardis.txt"


Set fso = CreateObject("Scripting.FileSystemObject")
Set ts = fso.OpenTextFile(Filename, ForAppending, True)
ts.Writeline(Now())
ts.Close
Set ts = Nothing
Set fso = Nothing


'---- End Code ------

Sigh...

CW
 
Re: Task Scheduler IGNORES duration


<createwindow@gmail.com> wrote in message
news:f0a0d692-7966-4e2c-9afa-e04afcc1d731@k37g2000hsf.googlegroups.com...
On Jul 11, 11:24 pm, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:
> There is no script "above".
>
Here it is again...

This is my test code: Called test.vbs


'---- Start Code ------


Option Explicit


Dim fso, ts, Filename
Const ForReading = 1, ForWriting = 2, ForAppending = 8


Filename = "c:\util\Tardis.txt"


Set fso = CreateObject("Scripting.FileSystemObject")
Set ts = fso.OpenTextFile(Filename, ForAppending, True)
ts.Writeline(Now())
ts.Close
Set ts = Nothing
Set fso = Nothing


'---- End Code ------

Sigh...
=======================
I pasted your code into c:\test.vbs, then scheduled the following task:
Target cscript.exe //nologo c:\test.vbs
Time 19:45
Repetition 55 minutes
Duration 2 hours
Account My own

Here is the contents of c:\Tardis.txt as at 23:00 -
Fri 11/07/2008 19:45:02
Fri 11/07/2008 20:40:02
Fri 11/07/2008 21:35:02

Note that there is no log entry at 22:30, which is what I would
have expected.
 
Re: Task Scheduler IGNORES duration

Dear pegasus,

Thats it exactly. Now I'm sure you see what a pain it is because I'm
getting these correct results on Vista 32 and 2008 x64 using small
durations of 15 minutes or so. However, when I schedule the VBS test
to run every hour for 6 hours on server 2008 x64 it keeps going for
the 7th 8th 9th (and forever) hours!

Today I'm trying Vista Business x32 with the *identical* VBS test in a
VM for the same 6 hours as the darn "task that won't quit" on my new
Quad core 8 GB RAM, 4 Terabyte server.

Lets see what happens.

Thanks for your 2 hour test btw much appreciated.
CW
 
Re: Task Scheduler IGNORES duration

Dear Pegasus and MS Windows 6.0.6001 team,

There is a BUG in the task scheduler.

It fails to obey the setting of 6 hours duration. (At least).

I just confirmed this on Windows Vista Business RTM Service Pack 1.
Previously confirmed on Windows Server 2008 Enterprise SP1 x64 RTM
with Hyper-V

Pegasus, here is my tardis.txt

12/07/2008 12:04:00 PM Initial
12/07/2008 1:04:00 PM Repeat 1
12/07/2008 2:04:00 PM 2
12/07/2008 3:04:00 PM 3
12/07/2008 4:04:00 PM 4
12/07/2008 5:04:00 PM 5
12/07/2008 6:04:00 PM 6
12/07/2008 7:04:00 PM 7 !!
12/07/2008 8:04:00 PM 8 !!!
12/07/2008 9:04:00 PM 9 !!!!
12/07/2008 10:04:00 PM 10 !!!!! etc. !!!!!!!

I will try 3, 4, 5, hours now and see if there is a "stuff up point".

To reproduce:

Set a task as per VBS in this thread.
Set it to trigger "On a Schedule" on the Xth (day e.g. 2nd Sunday) of
every month, at a time in the future by a few minutes.
Set it to repeat the task for 1 hour "for a duration of" 6 hours - (6
hours is not in the drop down list - just type it in - it gets shown
as 06:00:00).
Tick the Run with highest privlidges.

Unless I'm doing something wrong. GKWhat tho ???

This revelation may get as ignored as when I found outlook 2007
sending AUTH commands to POP3 servers in Jan 2007. I notice with a
network trace silly Outlook 2007 is *STILL* sending AUTH (and a
space) as the first command to POP3 servers. Most of them return "-
ERR" as in error. GKWhy this has never been fixed?

Pego, do you have Network Monitor 3.1 and Outlook 2007 - take a look
at the traffice as Outlook strikes up a conversation with POP3
server(s). Its ROFL stuff.

Maybe the NSA need it foer some kind. o..... (Sorry I digress). :-)


Regards,
CreateWindow
 
Re: Task Scheduler IGNORES duration


<createwindow@gmail.com> wrote in message
news:52022d82-c4e8-41a1-b2c1-60fecb31fcf0@a1g2000hsb.googlegroups.com...
> Dear Pegasus and MS Windows 6.0.6001 team,
>
> There is a BUG in the task scheduler.
>
> It fails to obey the setting of 6 hours duration. (At least).
>
> I just confirmed this on Windows Vista Business RTM Service Pack 1.
> Previously confirmed on Windows Server 2008 Enterprise SP1 x64 RTM
> with Hyper-V
>
> Pegasus, here is my tardis.txt
>
> 12/07/2008 12:04:00 PM Initial
> 12/07/2008 1:04:00 PM Repeat 1
> 12/07/2008 2:04:00 PM 2
> 12/07/2008 3:04:00 PM 3
> 12/07/2008 4:04:00 PM 4
> 12/07/2008 5:04:00 PM 5
> 12/07/2008 6:04:00 PM 6
> 12/07/2008 7:04:00 PM 7 !!
> 12/07/2008 8:04:00 PM 8 !!!
> 12/07/2008 9:04:00 PM 9 !!!!
> 12/07/2008 10:04:00 PM 10 !!!!! etc. !!!!!!!
>
> I will try 3, 4, 5, hours now and see if there is a "stuff up point".
>
> To reproduce:
>
> Set a task as per VBS in this thread.
*** Done.

> Set it to trigger "On a Schedule" on the Xth (day e.g. 2nd Sunday) of
> every month, at a time in the future by a few minutes.
*** Set to trigger at 15:45 every 2nd Saturday of the month

> Set it to repeat the task for 1 hour "for a duration of" 6 hours - (6
> hours is not in the drop down list - just type it in - it gets shown
> as 06:00:00).

*** Done.

> Tick the Run with highest privlidges.
*** Done.

> Unless I'm doing something wrong. GKWhat tho ???
>
> This revelation may get as ignored as when I found outlook 2007
> sending AUTH commands to POP3 servers in Jan 2007. I notice with a
> network trace silly Outlook 2007 is *STILL* sending AUTH (and a
> space) as the first command to POP3 servers. Most of them return "-
> ERR" as in error. GKWhy this has never been fixed?

*** Here is the contens of c:\Tardis.txt, copied at 22:54:
Sat 12/07/2008 15:45:03
Sat 12/07/2008 16:45:02
Sat 12/07/2008 17:45:02
Sat 12/07/2008 18:45:03
Sat 12/07/2008 19:45:02
Sat 12/07/2008 20:45:04
*** No surprise for me here even if it is not what you expected.
 
Re: Task Scheduler IGNORES duration

OK, That's not what I'm getting.

So this is a bug "just for me" -
amazing.................................

Must be my Time Zone & Language settings??? or the fact that I am
launching the task under an account called Robot who is a member of
the Administrators group. (On the machine).

I'll do more tests.

Meanwhile I'll just have to modify my main backup check script to work
when run on the hour - every hour - forever!
At least I can write code that will obey me :-)


Thanks again,
CW aka Ring0
 
Re: Task Scheduler IGNORES duration

OK, that's interesting, I set one of my Vista VM's to English US and
US timezone (PDT) and I think its working!

More tests needed; and if proven, how to pass this on to MS???

Maybe via the connect WS where I already beta test things for them - I
wonder how an off topic post woud get through.. Hmmm...??

CW
 
Re: Task Scheduler IGNORES duration

No, thats not it. Time (pun intended) to terninate this thread and get
back to sometning productive.

Just for fun here is the exported task. Wonder if anyone can spot a
sillyness?? Apart from the fact I'm letting WScript.exe do the work
based on this is a VBS with no UI. I didn't bother with all that
cscript stuff //batch //nologo //pleasework..... etc.

<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/
2004/02/mit/task">
<RegistrationInfo>
<Date>2008-07-11T10:26:22.3663424</Date>
<Author>VISTADEV\Administrator</Author>
</RegistrationInfo>
<Triggers>
<CalendarTrigger>
<Repetition>
<Interval>PT1H</Interval>
<Duration>PT2H</Duration>
<StopAtDurationEnd>false</StopAtDurationEnd>
</Repetition>
<StartBoundary>2008-07-12T22:00:00</StartBoundary>
<Enabled>true</Enabled>
<ScheduleByMonthDayOfWeek>
<Weeks>
<Week>2</Week>
</Weeks>
<DaysOfWeek>
<Saturday />
</DaysOfWeek>
<Months>
<January />
<February />
<March />
<April />
<May />
<June />
<July />
<August />
<September />
<October />
<November />
<December />
</Months>
</ScheduleByMonthDayOfWeek>
</CalendarTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>VISTADEV\Administrator</UserId>
<LogonType>Password</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>true</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>false</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT1H</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>C:\Util\test.vbs</Command>
</Exec>
</Actions>
</Task>

Over and out...
CW
 
Re: Task Scheduler IGNORES duration


<createwindow@gmail.com> wrote in message
news:af8eb460-c69e-4924-8e2f-998fb99d17f9@34g2000hsh.googlegroups.com...
> OK, that's interesting, I set one of my Vista VM's to English US and
> US timezone (PDT) and I think its working!
>
> More tests needed; and if proven, how to pass this on to MS???
>
> Maybe via the connect WS where I already beta test things for them - I
> wonder how an off topic post woud get through.. Hmmm...??
>
> CW

Your beta testing activity would be a good starting
point, if only to enquire about an effective channel
to discuss this issue.
 
Re: Task Scheduler IGNORES duration

I have just set up a new Server 2008 STD x64 and have run into the same bug
as you. This functionality worked fine on the old server (SVR 2003 x32) and
some small tests with short duration (like send a mail every 1 minute for 5
minutes) works.
The problem occurs on my small scheduled jobs that are set up to run
repeatedly for some hours.

--
Sigurd


"createwindow@gmail.com" wrote:

> Well, at least I'm not alone...
>
> http://www.eggheadcafe.com/software/aspnet/31368449/task-scheduler.aspx
>
> WHY!!! I'ts enuf to drive one mad. :-~
>
> Time for a tequila.
>
> CW
>
>
>
 
Back
Top