Copy link to clipboard
Copied
I have upgraded ColdFusion from 2016 to 2021. The installation log file shows only successes without any warnings or errors. CF Admin launched after the installation and I was able to confirm the settings migrated correctly and I created 2 of the 3 datasources with the Oracle driver(I don't have good password for 1 of them). I also manually installed update 4. I disconnected all the IIS sites from version 2016 with its Web Ser Config Tool and then connected all of them to the new version. I've disabled the old CF2016 services to ensure there's no confusion
Unfortunately now, I can't get into the CF Admin. IE reports ERR_CONNECTION_TIMED_OUT. The 1 site the server is hosting responds with a CF error because one of the datasources is broken. So at least I know CF is running and responding to requests. The pathes of 2 of the virtual directories were correctly updated to the new CF version's path. However, CFIDE was still pointing to the old version. Manually updating it to the new version's path had no effect on the browser error.
The port has not changed, so it's not a firewall issue. Event viewer, IIS and CF log files are not catching any errors. Other than a McAfee issue shutting down a call to a dll in the new version's path, I'm stumped.
Any suggestions or insights would be greatly appreciated.
Thanks.
Thanks for all the help. It turns out to be missing windows firewall rules. Explicit allows over both tcp and udp were in for v2016. I'm OOO at the moment and will post the exact rules when I'm back working next week.
Copy link to clipboard
Copied
Jeff, you've done a great job laying out details. I'm sure it's a frustrating situation. That said, it may be something simple, or it may be something more esoteric. Let me offer several ideas, from most likely (yet easy to rule out) to more challenging.
You're sure you're using the same url for that admin when it fails as when it worked right after the install, right?
If it's not something like the above, then it seems something's gone amiss. It's not some inherent result of installing cf, as it was working at first install.
Moving on, when you say the first launch of the cf admin migrated settings from the old one, do beware that at that moment, had you restarted cf, perhaps this error would have happened. Why? Because the import could have brought in changes (especially jvm ones) that may not work well with the new version. But that's just a guess, maybe not the issue. (And I doubt you have the original files from before the migration, as cf does not protect them.)
Some more questions that could help us, in that case:
Let us know how things go. And if you get to needing this fixed without lots of back and forth here (I'm sure others will chime in with more thoughts), note that I could help via a remote consulting session. I doubt it would take 15 mins to sort this out.
That's not a crass sales pitch or bait and switch: it's simply a lot easier to just follow a series of diagnostic steps together live than to elaborate further on each, and the permutations of what they may show, and what next steps would be for each result. If interested, check out the consulting page at carehart.org.
I do hope I may have offered you a solution among all else above, but I'll be following along here either way to hear how it turns out.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Suggestion:
Copy link to clipboard
Copied
Can you please paste the URL that you are using to access the CF Admin?
Copy link to clipboard
Copied
Thanks for all the help. It turns out to be missing windows firewall rules. Explicit allows over both tcp and udp were in for v2016. I'm OOO at the moment and will post the exact rules when I'm back working next week.
Copy link to clipboard
Copied
Glad you solved it. It sounds like someone setup the windows firewall rules (on the cf machine) to be tied to the program (cf2016) rather then its port (8500). You may want them to reconsider just connecting them.now to cf2021--otherwise you or others after you will hit the same issue on the next cf version. 🙂