Skip to main content
Inspiring
June 22, 2017
Answered

ColdFusion 2016 install migration error "Could not import Runtime settings"

  • June 22, 2017
  • 2 replies
  • 2319 views

Hello,

We are trying to upgrade from ColdFusion 11 to ColdFusion 2016.  During the migration, we had two errors:

"Error","Could not import your ColdFusion Runtime settings. - The current user is not authorized to invoke this method."

"Error","Could not import your ColdFusion Scheduled Tasks. - Advance Scheduling support is not available in this edition of ColdFusion server

I'm not too concerned about the Scheduled Tasks because we only have one that was a 'one time' task and now it's in the past. 

However, I'm not sure what is included in 'Runtime settings' so I am hesitant to just try and start using the new ColdFusion without knowing what did not get migrated correctly.

We tried running as administrator and that did not solve the problem.  How can we resolve the 'Runtime settings' error?

Thanks in advance for any help.

This topic has been closed for replies.
Correct answer aliciam29605858

Sorry about the delay. Could you please send an email at cf.install@adobe.com  and mentioned this forum post link.

Thanks,

Priyank


Thank you for your help!  For anyone else with this problem, we figured out that the debugging port in CF11 was the same as the port used by the Administration webpage in CF2016.

2 replies

Known Participant
September 15, 2021

Hi, was trying to upgrade CF11 to CF2021 and facing the same problem. Everything migrates properly, except runtime. Stopped all CF11 services before starting the installation too. Migration log error reads:

 

"Error","http-nio-8500-exec-1","09/15/21","01:13:54","CFADMIN","Could not import your ColdFusion Runtime settings. - String index out of range: -1"

 

If needed, can post migrationException log too.

 

Thanks in advance!

Charlie Arehart
Braniac
September 15, 2021

You can share the migration logs, sure. That may help. But I will note that I won't be surprised if it's simply not supported to migrate CF11 settings into CF2021. That's jumping over CF2016 and 2018. I'm pretty sure CF has only tended to support migration of two versions back, not three.

 

Have you tried instead to use the CAR migration feature, to export your settings (some or all) out of your CF11 (to a .car file), and then import that into CF2021? I can't say for sure that it will work, but I think it might. It's worth a try.

 

That said, you may want to copy off first all the neo*.xml files in your CF2021 instance's lib folder (such as [cf]/cfusion/lib, or [cf]/[insancename[]/lib), since the import would try to modify those. If anything went amiss, you could stop CF, copy them back in, and restart to be back where you were before trying the CAR import (unless you or anyone may make changes in the CF Admin UI between then and when you took the backup).

 

One other thought: rather than resurrect a 4 year old thread, sometimes it would be better to open a new one (and point to this old one for context). At this point, it's probably moot. But I'll assume that comment marked as the "answer" for this thread did not work for you, is that right?

/Charlie (troubleshooter, carehart. org)
Priyank Shrivastava.
Community Manager
Community Manager
June 22, 2017

Hi,

Can you please share the car log which was created under \ColdFusion2016\cfusion\logs folder.

Thanks,

Priyank

Thanks,Priyank Shrivastava
Inspiring
June 27, 2017

priyanks97293812​ Do you need more information than what is provided above?

If we cannot work around the 'Runtime' error, is it safe to just manually set up the connection to our Apache web server?  Is there anything outside of the 'cfusion\runtime' directory that is included in the definition of failure of 'Runtime' during migration that we would need to copy over?

WolfShade
Braniac
June 28, 2017

Hi, aliciam29605858​,

I'm going to totally guess:  Was the local account an administrator account?  I ask because the first error indicates a permission issue.

If the account is an admin account, I'm not sure what to say.  But if the account was NOT the admin account, then roll-back the upgrade and log on as admin to perform the install and see if that helps.

HTH,

^ _ ^