Author |
Message |
barefootguru
Joined: 10 Aug 2007 Posts: 195
|
|
Days of month schedule not working |
|
Hi, I have a job I want to run on the 9th, 10th, 11th, 12th, 13th, 14th, and 15th of the month.
I've set the schedule type to Monthly.
Start date=1/10/2010, Start Time=06:00 PM
Run on Days 9, 10, 11, 12, 13, 14, 15
'Shift' is off and calendar is [default]
It's currently the 13th @ 16:06 yet 24x7 is saying the next run isn't until the 14th.
This happened in 4.3.293 and I've just installed 4.4.319 with the same result. Windows XP.
Thoughts?
|
|
Tue Oct 12, 2010 11:08 pm |
|
|
mbenton
Joined: 08 Feb 2010 Posts: 38 Country: United Kingdom |
|
|
|
I also am having the same problem.
Currently 24x7 MP 4.4b319, but was on 4.4b314.
Scheduled job to run Monthly;
Start date=6/09/2010 at 10:00 AM
Run on Days 6
Calendar=[default]
The job ran on the 6th September 2010 at 10:00, but there was no trace of the job being queued or run on the 6th October 2010 :-(
|
|
Wed Oct 13, 2010 4:48 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7903
|
|
|
|
Hi, I'm unable to offer an immediate solution for this issue. I've logged new case for the support #24x7-11835, and waiting for more details.
|
|
Wed Oct 13, 2010 9:17 am |
|
|
barefootguru
Joined: 10 Aug 2007 Posts: 195
|
|
|
|
Thanks SysOp. Now it's the 14th 24x7 is saying the next run is tomorrow--it should be later today.
Our myriad of hourly, daily, and weekly jobs are all fine.
|
|
Wed Oct 13, 2010 3:40 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7903
|
|
|
|
If you are running 24x7 on a Windows system as a service... please check regional settings and time-zone selected for the service account and also the default regional settings for the system. If they differ from your interactive accounts, perhaps that may help to explain the anomaly.
|
|
Wed Oct 13, 2010 4:23 pm |
|
|
barefootguru
Joined: 10 Aug 2007 Posts: 195
|
|
|
|
Hi, we alternate between running the 24x7 service and running the GUI. Both are under my account. When looking at the next run time I've been using the GUI, so there's an issue there; and the scheduled run has also been missed when running as a service.
I don't know how to change the default regional settings for XP and the intraweb is saying it can't be done.
|
|
Wed Oct 13, 2010 4:36 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7903
|
|
|
|
They can be modified here HKEY_USERS\.DEFAULT\Control Panel\International and here HKEY_USERS\.DEFAULT\Control Panel\International\Geo
Computer manufactures often leave the default USA based settings.
Please let us know if this doesn't help.
|
|
Wed Oct 13, 2010 6:11 pm |
|
|
barefootguru
Joined: 10 Aug 2007 Posts: 195
|
|
|
|
Any particular entry?
For both the default user and myself International\iCountry=64 and International\Geo\Nation=183
We're in New Zealand.
|
|
Wed Oct 13, 2010 6:54 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7903
|
|
|
|
Can you compare all values in that registry key against values in your account and update not matching values?
|
|
Wed Oct 13, 2010 7:13 pm |
|
|
barefootguru
Joined: 10 Aug 2007 Posts: 195
|
|
|
|
I didn't want to muck with the registry on our production machine so I've installed 24x7 on a virtual machine and this is what I've found.
The International and Geo registry entries for the default user and myself are identical.
Here's the results for a Monthly schedule, looking at the Next Run column:
It's currently 2010-10-15 before midday, the job is scheduled for 17:00
Start date=2010-10-01, Days=15, 16, 17. Next run=wrong date of 16th
Start date=2010-10-15, Days=15, 16, 17. Next run=right date of 15th
Start date=2010-10-15, Days=15. Next run=right date of 15th
Start date=2010-10-14, Days=15. Next run=wrong date of 15th Nov
Start date=2010-09-15, Days=15. Next run=wrong date of 15th Nov
Start date=2010-09-14, Days=15. Next run=wrong date of 15th Nov
So it looks like there's a bad interaction between the Start Date and the Days list. It also happens when using the single Day entry.
Are you able to reproduce?
Cheers
|
|
Thu Oct 14, 2010 7:07 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7903
|
|
|
|
Thank you. This example is very helpful. And yes, after moving my system clock forward to 15th and changing to 10 minutes before noon, I can reproduce this issue. I'm trying to figure out at what time the next run clock starts shifting 1 day forward and what can be done to resolve this issue.
|
|
Thu Oct 14, 2010 9:58 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7903
|
|
|
|
It seems to me that as long as the initial start date matches first day in the sequence, everything is ok. The problem manifests when the start date is before the first day.
I'm glad there is a simple workaround available. Still I'm going to log a bug report describing the issue with incorrect first start date calculation.
|
|
Thu Oct 14, 2010 11:19 pm |
|
|
barefootguru
Joined: 10 Aug 2007 Posts: 195
|
|
|
|
Thanks, though not convinced there's a workaround:
Today's the 22nd Oct at 09:15. I create a monthly job which runs on Day 22 at 17:00, Start Date=22nd Sep. Next run is showing as 22nd Nov instead of today.
|
|
Thu Oct 21, 2010 4:18 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7903
|
|
|
|
We are working on a fix for this issue, and expecting it included with next update planned for to the next week
|
|
Fri Oct 22, 2010 8:54 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7903
|
|
|
|
Hi,
This was fixed in version 4.4.322, which was released today. Thank you for your patience and support with resolving this issue.
|
|
Fri Nov 05, 2010 7:18 pm |
|
|
|