Skip to main content
altascene
Inspiring
December 12, 2021
Answered

CF2018 Incorrect Update Level After Update

  • December 12, 2021
  • 2 replies
  • 528 views

I have updated an installation of CF2018 from U4 to U8, and then to U12.  I did upgrade the web connectors after upgrading to U8, and then upgraded to U12.  All of these steps completed with no errors, and my site is now up, and I am able to use CFAdmin.  I also confirmed that the secret introduced in U8 matchs in server.xml and workers.properties.

 

In CFAdmin, when I check the Information page, to verify the current version, I see that CF is at U8 (2018.0.08.328566), and not U12.  If I go Server Updates, no updates are available.  If I check the CF Updates folder, I see that there is information for the U12 update.  As part of this update, I also updated to Java 11.0.12 (I will update to 11.0.13 at a later date).

 

At this point, I need some guidance.  Do I manually uninstall U12, even though CFAdmin thinks that I am at U8?  Or, do I manually re-install U12 without uninstalling it first?  Or, is there a different way to on how to address this issue?

 

Thanks,

Scott

This topic has been closed for replies.
Correct answer Charlie Arehart

It would not make sense to me for the cf admin info page to report 2018.0.8 if the latest update installed was 12.

 

Atr you confirming that the install log in the update 12 folder (under hf-updates) shows 0 fatalerrors? and the date/time if that install log is later than any install log in the update 8 folder?

 

If you find that the u12 install log DID have errors, you can just try installing it again, yes. And doing it manually is often the most reliable approach, for various reasons. 

2 replies

Charlie Arehart
Community Expert
Charlie ArehartCommunity ExpertCorrect answer
Community Expert
December 12, 2021

It would not make sense to me for the cf admin info page to report 2018.0.8 if the latest update installed was 12.

 

Atr you confirming that the install log in the update 12 folder (under hf-updates) shows 0 fatalerrors? and the date/time if that install log is later than any install log in the update 8 folder?

 

If you find that the u12 install log DID have errors, you can just try installing it again, yes. And doing it manually is often the most reliable approach, for various reasons. 

/Charlie (troubleshooter, carehart. org)
altascene
altasceneAuthor
Inspiring
December 12, 2021

Charlie,

 

Thanks for getting back to me.  In checking the install log, I did find one error;

 

"Failed to copy hotfix files:C:\Windows\system32\config\systemprofile\377770.tmp\dist\cfusion\bin\coldfusion.exe: Failed to copy the hotfix files to the target location. Retry installation after ensuring that the server is not running or files are not locked by the server."

 

Based on your insights, I will attempt a manual reinstall.

 

Thanks, again,

Scott

altascene
altasceneAuthor
Inspiring
December 12, 2021

Charlie,

 

Another, related question.  In the instructions for a manual Update install, it is stated that the original JRE included with CF should be used;

Installing the update manually

  1. Click the link to download the JAR.
  2. Execute the following command on the downloaded JAR. You must have privileges to start or stop ColdFusion service and full access to the ColdFusion root directory.

    Windows: <cf_root>/jre/bin/java.exe -jar <jar-file-dir>/hotfix-012-328566.jar

    Linux-based platforms: <cf_root>/jre/bin/java -jar <jar-file-dir>/hotfix-012-328566.jar

Ensure that the JRE bundled with ColdFusion is used for executing the downloaded JAR. For standalone ColdFusion, this must be at, <cf_root>/jre/bin.

 

Does this imply that, when using the Update Installer process in CF Admin, the original JRE should also be used?  I had previously upgraded Java on the server from the original, bundled JRE (11.01) to 11.05.

altascene
altasceneAuthor
Inspiring
December 12, 2021

Another tibit of information.  Tomcat is now at version 9.0.50.0, which was part of the U12 update.