Invisible Scheduled Task

2012-01-18 Thread Matthew Gersting
Has anyone had any experience with a scheduled task that is mysteriously running but does not appear in the ColdFusion Administrator? I am racking my brain on this one and starting to feel a little insane. ~| Order the Adobe C

Re: Invisible Scheduled Task

2012-01-18 Thread Dan Baughman
Is there another instance of CF somewhere that could be triggering the task to run? does the server log show the http request, and the scheduler activity, or just the http request? On Wed, Jan 18, 2012 at 2:00 PM, Matthew Gersting wrote: > > Has anyone had any experience with a scheduled task th

Re: Invisible Scheduled Task

2012-01-18 Thread Alan Rother
What are the symptoms that lead you believe a scheduled task is running? I assume it's something along this line, "the only way such and such could get updated, is if this file, in this folder is hit. Looking at the logs this file is clearly being hit - but it's not linked to anywhere" If that i

Re: Invisible Scheduled Task

2012-01-18 Thread Russ Michaels
put some code in the scheduled task to log the address of the server that is executing it. You will probably find it is being called from somewhere else. we have had this issue lots of times with clients and it always turns out that the scheduled task is still setup on their old hosts server. --

Re: Invisible Scheduled Task

2012-01-18 Thread Matthew Gersting
Thanks for the tips - I'll try these out and let you know what, if anything, I find. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http:

Re: Invisible Scheduled Task

2012-02-02 Thread Matthew Gersting
Hey, all - thanks for the ideas. I ended up manually going through the neo-cron.xml file for all our many, many instances and finally found it - it was in a very old instance that had been re-purposed a long time ago. ~| Orde

Re: Invisible Scheduled Task

2012-02-06 Thread Dain Anderson
We had this very same problem, and removing it from the neo-cron.xml file was the only way to get rid of it. -Dain On Thu, Feb 2, 2012 at 1:43 PM, Matthew Gersting wrote: > > Hey, all - thanks for the ideas. I ended up manually going through the > neo-cron.xml file for all our many, many insta