Use neo-cron.xml to migrate the ColdFusion program task

We currently have two ColdFusion 10 dedicated servers and we are migrating to a VPS server. We each have many scheduled tasks. I have obtained each neo-cron.xml File and copied the var XML element from the struct type=’coldfusion.server.ConfigMap’ XML element and pasted them into that element in the neo-cron.xml file. New server. After that I restarted the ColdFusion service, Log in to cf admin, all tasks are displayed as expected.

My problem is that when I try to update any task, I get the following error when saving:

An error occured scheduling the task. Unable to store Job :
‘SERVERSCHEDULETASK#$%^DEFAULT.job_MAKE CATALOGS (SITE CONTROL)’,
because one already exists with this identification

In addition, when I try to delete a task, it tells me that the task with that name does not exist. So in my opinion, the task information must also be stored elsewhere. Therefore, when I When trying to update the task, the record in the secondary location does not exist, so it will try to add it to the neo-cron.xml file, which will cause an error because it already exists. When trying to delete, it does not exist in the secondary location , So it means that there is no task with that name. This is just a guess.

Is there any idea how to make it work without manually recreating dozens of tasks? According to my reading, this should work, but I need to be able to edit the task.

Thank you.

After a lot of scratching, I was able to find out the problem. It all boiled down to the brackets in the scheduled task name. This resulted in “Unable to store job:’SERVERSCHEDULETASK#$%^ DEFAULT.job_MAKE directory (site control) ‘, because this identifier already exists” error and also caused me to be unable to delete the job. I think it is related to encoding brackets, because the actual neo-cron.xml name attribute of the var element encodes the following name:

serverscheduletask#$%^default#$%^ MAKE CATALOGS( SITE CONTROL)

Please note that this exception does not exist on ColdFusion 10, Update 10, but on Update 13 It does exist. I’m not sure which update broke it, but you went.

We currently have two ColdFusion 10 dedicated servers and we are migrating to a VPS server . We each have many scheduled tasks. I have obtained each neo-cron.xml file and copied the var XML elements from the struct type=’coldfusion.server.ConfigMap’ XML element and pasted them into neo- This element in the cron.xml file. New server. After that I restarted the ColdFusion service, logged in to cf admin, and all tasks were displayed as expected.

My problem is that when I try When updating any task, I encountered the following error when saving:

An error occured scheduling the task. Unable to store Job :
‘SERVERSCHEDULETASK#$ %^DEFAULT.job_MAKE CATALOGS (SITE CONTROL)’,
because one already exists with this identification

Also, when I try to delete the task, it tells me the task with that name Doesn’t exist. So in my opinion, the task information must also be stored elsewhere Therefore, when I try to update the task, the record in the secondary location does not exist, so it tries to add it to the neo-cron.xml file, which causes an error because it already exists. When trying to delete it, it Does not exist in the auxiliary location, so it means that there is no task with that name. This is just a guess.

Any idea how to make it work without manually recreating dozens of tasks? According to my reading, this should work, but I need to be able to edit the task.

Thank you.

After a lot of napping, I was able to Find out the problem. It all boils down to the brackets in the scheduled task name. This resulted in “Unable to store job:’SERVERSCHEDULETASK#$%^ DEFAULT.job_MAKE directory (site control)’ because this logo already exists” error and also caused I cannot delete the job. I think it has something to do with the encoding brackets, because the actual neo-cron.xml name attribute of the var element encodes the following names:

serverscheduletask#$%^default#$% ^ MAKE CATALOGS( SITE CONTROL)

Please note that this exception does not exist on ColdFusion 10, Update 10, but it does exist on Update 13. I am not sure which update broke it, But you went.

Leave a Comment

Your email address will not be published.