Skip to main content
A
ACS LLC
Inspiring
January 14, 2008
Question

Scheduler not running

  • January 14, 2008
  • 1 reply
  • 436 views
I have used the scheduler for many years with no problem. All of a suddent after removing all the sceduled tasks and adding just one new one that runs indefinately it won't run the task

I know it is set up correctly because if I run it from the administrator by hitting the go button, it works.

It did for for a short time, just a few hours then stopped, so I removed it, added it again, and same problem.

I also notice that it's not even writing any entries to the scheduler log file, which I deleted until I manually run it.

I'm running Windows Server 2003 with Cold Fusion 5.0

Appreciate any advise

Thanks

Mark
    This topic has been closed for replies.

    1 reply

    D
    DCwebGuy
    Inspiring
    January 15, 2008
    Try rebooting the whole machine if you haven't already. Then I would definitely check the permissions on the task file. Is it behind a firewall? When you say it runs for a few hours then stops it sounds like the session or login is timing out at the point which it fails. That leads me to believe it has to do with security or firewall. You might also consider upgrading from CF 5 to the latest version. Post back once you find the answer.
    A
    ACS LLCAuthor
    Inspiring
    January 15, 2008
    Already tried a reboot. I actually tried it on another server that I put a trial of CF8 on. and also tried it on my dev machine running CF5 and it had the same problem.

    So I tweaked the CFM page which it hits to see if that made a difference by adding some HTML into it, but that did not work.

    Next thing I tried changing the time, I wanted it running every 15 minutes around the clock so I had something like start at 1:00 and finish at 23:45 I changed it to 20:00 to 22:00 and it worked fine, I then started to expand that time gap and so far so good, I have it set at every 15 minutes 1:00 to 23:30 and it ran all night

    It looks as though if you try to put the start and end to close to each other that it trips.. or, I've just had a lucky run, it's going to take more experimentation to see if I can replicate the problem and also figure out what's causing it. If it runs for another 24 hours I'll delete it and add a new one with start 1:00 and end 12:55 to see what happens, hopefully it wil trip and I'll have my answer, although I'm not optomisitc!

    After typing this I realize that 1:00 and 12:55 might technically cause a problem? If you start at 2:00am then it won't have an end time because the end of the day is 23:59. Maybe that is what is causing the problem
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices