neo-cron.xml corruption issue

ColdFusion , Gotchas , Misc , Server and Hosting Add comments

After New Years - we returned to a sickly server, and something I never came across before - so I thought I'd share this with you all!


Our servers are deployed as Multiple J2EE Instances runnng the latest version of ColdFusion 9.0.1.

When we tried accessing one particular application, we got the following error:

The Cron service is not available.  
This exception is usually caused by service startup failure. Please check your server configuration.

Don't be fooled by the error message, the real issue lies in a corrupted server file.

Turns out the neo-cron.xml file was corrupted.


About neo-cron.xml

The neo-cron.xml file is used by the ColdFusion administrator to store the details of any Scheduled Tasks configured. 

The content of the file is stored in WDDX format and is located in "cf_root\lib".



This file normally resides in C:\coldFusion9\lib (stand-alone installation) or C:\JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib (for multiple instances) 

NOTE: The server name "cfusion" is the default, if your installation has been modified \ customized it will reside in a slightly different path similar to the one above but the file will always reside in the "lib" folder.

Thankfully we had backups for the server so it was simply a case of retriving the last backup "neo-cron.xml" file and restoring it to the "lib" directory.

If, however you're not in that position, then the following content should get you back up and running without re-installing:

<wddxPacket version='1.0'><header/><data><array length='2'><struct type='coldfusion.server.ConfigMap'></struct><boolean value='false'/></array></data></wddxPacket>

WARNING: This content is a blank instance of the file and obviously does not contain any configuration for previous scheduled tasks.  Ideally you will want to retrieve your original neo-cron.xml file if possible.



Purpose and location of XML configuration files used in ColdFusion MX

Bookmark and Share

8 responses to “neo-cron.xml corruption issue”

  1. Pritesh Says:
    Thanks a lot,You save my time.
  2. Ross Says:
    Thanks :) Having a blank version of it is a real life saver to get back up and going.
  3. Steve Says:
  4. Steve Says:
    Thanks for posting. Saved me a lot of time.
  5. Martin Parry Says:
    Can you believe this sis STILL happening in version 10 all these years on!
  6. Martin Parry Says:
    FYI - For version 10 (I'm at update 11 so don't know if it's applicable to earlier versions) the wddx is slightly different:-

    <wddxPacket version='1.0'><header/><data><array length='4'><struct type='coldfusion.server.ConfigMap'></struct><boolean value='false'/><string></string><string>log,txt</string></array></data></wddxPacket>
  7. Oli H Says:
    Niall! Looks like you saved my arse here (and yes amazingly we're still running a 901 server :) Happy birthday for a month today!
  8. Martin Parry Says:
    Please vote this up...

Leave a Reply

Leave this field empty:

Powered by Mango Blog. Design and Icons by N.Design Studio