Last post Jul 13, 2006 05:59 AM by gashy
Sep 02, 2004 02:09 PM|hald9000|LINK
Jan 28, 2005 12:55 PM|tward|LINK
Mar 11, 2005 10:29 AM|rodneyjoyce|LINK
Mar 11, 2005 10:56 AM|tward|LINK
Mar 11, 2005 11:17 AM|rodneyjoyce|LINK
Mar 11, 2005 11:34 AM|tward|LINK
Mar 11, 2005 02:17 PM|DBuckner|LINK
Jul 13, 2006 05:59 AM|gashy|LINK
Did you ever get a related answer to your question/issue.
I am using 3.0.12 and have come across a similiar problem which I believe is related to caching. I was to understand that the next scheduled run of a job was derived from teh schedule history but that is not always the case as the cache holds this information
I get the scenario where I get a job run twice because different values of the next run is stored in the histroy and in the cache (which the schedule status relfects).
I don't have the luxury of restarting the IIS server to clear out any existing cached values but I can't see a way to reset the jobs so that they don't keep running twice.
Did you get any other responses other than in this thread?