Skip to main content
ConsoleGenRL
Known Participant
March 14, 2013
Question

Bug in Administrator / Scheduled Tasks

  • March 14, 2013
  • 2 replies
  • 1872 views

I get this error in the CF Administrator when trying to delete a scheduled tasks via the web interface:

The following task could not be found: <task name here - removed for privacy>.

The error occurred in scheduletasks.cfm: line 141

Called from scheduletasks.cfm: line 10
Called from scheduletasks.cfm: line 1

-1 : Unable to display error's location in a CFML template.

System info:

Windows Server 2008 64-bit

ColdFusion 10,0,8,283805

Tomcat 7.0.23.0

JRE 1.7.0_17

Any ideas?

This topic has been closed for replies.

2 replies

Participant
October 5, 2013

I encountered this problem today. I have found the root cause and solution at least as it pertained to my issue.

As we know, Neo-Cron.xml stores the task information including all variables defined by the user. It seems that if a space is entered in the "Group" field it is not properly handled when ColdFusion creates <var name>.

For example, the value <var name='serverscheduletask#$%^groupname #$%^task'> throws an error because there is a space after the value "groupname" and before "#". The "Add/Edit Scheduled Task" dialog and code seem to not handle a space in the "Group" field properly.

As a result, when you attempt to edit the entry from the "Add/Edit Scheduled Task" page the error noted by OP is thrown because the task name cannot be matched - it can't be matched because of the mishandled space.

The solution is to use a text editor to manually manipulate Neo-Cron.xml to remove the offending space(s).

Make sure to stop the ColdFusion server when you make these changes and then restart after the changes have been committed. For good measure, I also deleted Neo-Cron.BAK while ColdFusion was stopped.

itisdesign
Inspiring
March 14, 2013

Updated: Changed DarthGuybrushOz to Peter (name had changed to Peter Tilbrook upon my logging in)

Hi Peter,

This -appears- to have already been logged as #3351451.

Was the task originally created in CF10, or in a previous CF version?  If it was created in a previous CF version, was the task automatically migrated into CF10 via CF10's installer or was it manually imported via .car deploy?  Does the task name have any special characters in it?

Thanks,

-Aaron