Recently this error popped up when one of our customers updated their system so we wanted to share how it can be resolved.


The following error may occur under ColdFusion Administrator in the scheduled tasks tab:

The error occurred in scheduletasks.cfm: line 188 -1 : Unable to display error's location in a CFML template.


This problem occurs if neo-cron.xml file becomes corrupt.



Place the following in ColdFusion11\cfusion\lib\neo-cron.xml file and restart the Application Services

<wddxPacket version='1.0'><header/><data><array length='4'><struct type='coldfusion.server.ConfigMap'></struct><boolean value='false'/><string></string><string>txt,log</string></array></data></wddxPacket>

Alternatively, if you have a good backup of the same file you could replace that instead of the above step.


We are unable to reproduce any particular events that cause this issue.  If you have run into the problem, feel free to indicate in the comments any potential steps that may have contributed to it.

8 Comments to “Scheduled Task Error: Unable to display the error's location in a CFML template”

  1. Tom Chiverton
    I'm going to take a wild guess and say this is the same bug as
    so it should be easy to replicate.

    CF has *always* had issue where it would randomly corrupt it's own settings files because it's save logic isn't very robust.
  2. Prachi
    mistake appeared when one of our clients overhauled their framework so we needed to share how it can be determined.

  3. Casey Dougall
    Glad to know you still haven't corrupt neo-cron.xml bug between CF9 to CF11!
  4. Justin Cook
    We keep having this issue. So we have to keep an eye on our scheduled tasks and replace the corrupted neo-cron.xml file with a good backup. Any idea why neo-cron.xml gets corrupt in the first place and what would keep corrupting it?
  5. Aish Kapoor
    I am also affecting such error. Error occurred in my computer but it is unable to display the error's location in CFML i will try solution which is given above....
  6. Robin
    We are suffered a few problems with scheduler too when renaming tasks. Once it ran all tasks at once..!
  7. John
    Thank you so much for sharing.
  8. Tony
    Just had this happen last night. The fix works, but note that when that file gets corrupted, you lose all your scheduled tasks and they will need to be re-input if you don't have a backup of the .xml file.

Leave a Comment

Leave this field empty: