Coldfusion 2018 New Install – Cannot Open Up Coldfusion Admin After Reboot

March 26, 2019
Newbie 1 posts
Followers: 0 people
2

Coldfusion 2018 New Install – Cannot Open Up Coldfusion Admin After Reboot

Newbie 1 posts
Followers: 0 people
March 26, 2019

Hello, 4-5 months ago I installed Coldfusion 2018 on my new Dell Precision Laptop Workstation. It is high performance and running Windows 10. At that time I was able to access Coldfusion 2018 Admin and had 2 dynamic applications working fine. Three weeks ago I saw there were Coldfusion 2018 Updates available (I think 4 of them) and I did the latest update. Initially everything worked great but after my first reboot I get the error below and cannot access Coldfusion Admin (http://127.0.0.1:8500/CFIDE/administrator/index.cfm). I have since uninstalled and reinstalled Coldfusion 2018 at least 8 times now and still the same exact problem, I can access Admin after a fresh install but once I reboot I have the exact same problem. Really frustrated , any help would be greatly appreciated.

Thanks in advance,

Kirk

This site can’t be reached
127.0.0.1 refused to connect.
Try:
ERR_CONNECTION_REFUSED
Comments (2)
2019-04-01 02:42:49
2019-04-01 02:42:49

We discovered that the CF updates have been proactively updating the version of the jre installed on our local machines.  The problem we encountered was that some of our team was storing the Java folder in their program files directory.  Suprise, the CF installer was hitting some sort of install permission issue (that’s our best guess at least since the issue did not affect others).  We were able to track down the CF admin file that contained the server java settings and manually update the JRE to point to the new JRE folder and after that we were able to start up the service normally.

That having been said, each Hotfix issue seems to be its own unique challenge – This blog post by Charlie is worth a permanent bookmark: https://coldfusion.adobe.com/2019/03/problems-applying-cf-update-check-first/

Like
(1)
>
insuractive
's comment
2019-04-01 03:56:11
2019-04-01 03:56:11
>
insuractive
's comment

Thanks, insuractive. I was just about to post a comment to Kirk to consider what I shared in that post. It nearly always explains the scenario he describes.

If he confirms that perhaps it’s not that, then we can consider other possibilities.

Like
(1)
Add your comment