This issue showed up in my production environment immediately following a restart of the Cold Fusion services to recover from a JVM OutOfMemoryError. We have identified what caused the OutOf Memory error and have implemented code changes to prevent this in the future however now the scheduler isn't accessable via CF Admin. I'm thinking a file may have gotten corrupted in the scheduler during the OutOfMemory event. I have redundant application servers so I simply moved all my scheduled tasks to the other server until I can sort this out. Otherwise the server works fine. I made a archive of the server settings back a month or so ago, I'm wondering if I import that archive in through packaging and deployment if it might fix the corrupt file. I've also read some post about replacing the \cfusioninstance\lib\neo-cron.xml to resolve the issue. I wonder if anyone else has experienced anything like this?