tracker issue : CF-4203714

select a category, or use search below
(searches all categories and all time range)

Failure of importing Schedule Task

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Shigeyoshi Muraoka / ()

Created: 12/12/2018

Components: Installation/Config, Config

Versions: 2016,2018

Failure Type: Non Functioning

Found In Build/Fixed In Build: 2016.0.03.301771 / 314612

Priority/Frequency: Normal / Most users will encounter

Locale/System: ALL / Win 2012 Server x64

Vote Count: 0

Problem Description:
When running the migration wizard from ColdFusion 11 Std to 2016 Std, the following error occurs:
coldfusion.server.ServiceException: Advance Scheduling support is not available in this edition of ColdFusion server.

Steps to Reproduce:
1?Install ColdFusion 2016 Std on environment where ColdFusion 11 Std is already installed 
Input a license key of the Standard while installation process

2?After Setup, complete migration wizard (Follow the steps).

Actual Result:
After import of CF 11 settings, an error message indicating failure of Schedule Task and Runtime import is displayed.
Also, the error message above is logged on migrationException.log.

Expected Result:
Scheduled Task is imported properly without any error.

Any Workarounds: Using Enterprise or Trial Edition for installation.

This issue is same as the following forum.

Could you provide a hotfix that Schedule Task can be imported without causing the error even on Standard Edition?



Can you please provide information on below points: 1) Debugging port in CF11 & CF2016 is not the same? 2) If you see any permission issue in the log, was the local account an administrator account?  3) Detailed log (migration.log & migrationException.log) is needed.     
Comment by Nitin K.
30086 | January 03, 2019 04:33:30 AM GMT
Hi Shigeyoshi, Please help us with the information requested Thanks, Nitin
Comment by Nitin K.
30090 | January 07, 2019 06:52:02 AM GMT
  Did you get a chance to look at this ?
Comment by Nitin K.
30100 | January 09, 2019 03:15:40 AM GMT
When I inquired the issue through Adobe Platinum maintenance and support, Sandip Halder asked me to log this bug, and I did. I have reproduced this bug in his published test environment and he has confirmed the issue. I have already provided him with details and logs needed. Could you contact him and get information and logs?
Comment by Shigeyoshi M.
30101 | January 10, 2019 01:09:50 AM GMT
Thanks for the info. I will get in touch with him to get further information. 
Comment by Nitin K.
30102 | January 10, 2019 05:21:29 AM GMT