Skip to main content
B
boopower
Participant
October 5, 2023
Answered

Migrating from CF 2016 to 2023 Issue - The service is unavailable after Migration

  • October 5, 2023
  • 1 reply
  • 1791 views

I am trying to migrate Coldfusion from 2016 to 2023. I have followed the migration guide and stopped the CF 2016 service and installed the 2023 release. After installation and migration from 2016, when I review the IIS websites I have on the server, I am getting the following error:

 

The service is unavailable.

Service Temporarily Unavailable!

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Tomcat/ISAPI/isapi_redirector/1.2.46

 

Then when I look at the coldfusion-error.log file, I can see the following:

INFO: The Apache Tomcat Native library which allows using OpenSSL was not found on the java.library.path: [C:\ColdFusion2023\cfusion\lib;C:\ColdFusion2023\cfusion\jintegra\bin;C:\ColdFusion2023\cfusion\jintegra\bin\international;C:\\ColdFusion2023\\jre\bin]

 

Can anyone tell me what I have wrong that is causing the websites to not start working under CF 2023?

 

Looks like a mapping or config issue with IIS or something on the win server.

 

Thanks in advance for any help I can get.

 

    This topic has been closed for replies.
    Correct answer boopower

    I figured out the issue. You have to go into the WSConfig tool in the old verison of CF and remove the connector for IIS, then go into the C:\ColdFusion2023\cfusion\runtime\bin and run the wsconfig.exe tool and add the connector for the new instance of CF.

     

    Once that's done, the website resolved fine. Hope this helps someone else in the future.

    1 reply

    B
    boopowerAuthorCorrect answer
    Participant
    October 5, 2023

    I figured out the issue. You have to go into the WSConfig tool in the old verison of CF and remove the connector for IIS, then go into the C:\ColdFusion2023\cfusion\runtime\bin and run the wsconfig.exe tool and add the connector for the new instance of CF.

     

    Once that's done, the website resolved fine. Hope this helps someone else in the future.

      Charlie Arehart
      Community Expert
      Charlie ArehartCommunity Expert
      Community Expert
      October 5, 2023

      Yes, that is indeed the solution. And FWIW, it's been since cf2018 that the cf installer itself no longer leads you through implementing the web server config tool.

       

      Then again, it never did lead one through the process of launching the OLD web server config to remove that first. Neither does the documentation on using the web server configuration tool. We could assert that they should. 

       

      Finally, that migration guide also does not lead you through this step. And if anything that's a place it should be discussed. You would help many by opening a tracker ticket reporting that as a bug or feature request, at tracker.adobe.com. If you do, let us know the ticket number and interested readers here can add votes. 

      /Charlie (troubleshooter, carehart. org)
      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices