Strange Tomcat error after installing Update 5
Question… since upgrading to Update 5 on CF 2018, I’m randomly getting this screenshot when loading CF pages.
Refreshing the page makes it load properly. I’ve re-run the wsconfig.exe. It’s on a Windows Server 2019 AWS EC2 instance running IIS 10 and CF 2018. Has anyone else run into this problem? Any suggestions on where I should troubleshoot?
David, did either of the above solve your problem? I and dwaltermys each replied with different ways to get to the same solution (but because of this blog’s moderation of comments).
If it did not help, then you ought to add a comment to the tracker ticket and the blog post, so that Adobe can help you (and others who are asserting these are “not fixing their problem”).
First thing, David: you refer to re-running the wsconfig, but that won’t get you the latest available connector DLL. The one released with update 5 had a bug (a couple, it seems). You need to get an updated dll, from Adobe. And despite the blog post title not seeming to relate to your need, see this post:
https://coldfusion.adobe.com/2019/10/error-accessing-coldfusion-administrator-using-connector-port/
Let us know if that helps.
Beware also that if you DO re-run the wsconfig tool, that will cause an OVERWRITE of this updated DLL, and will put back in place the original one from update 5.
If that updated DLL does NOT help, then the next question is to wonder if you are merely in need of connector tuning. Since CF2016, the default connector settings are suited only to 2 sites sharing a connector (and there being only one connector). If you have either more than one connector, or more than two sites sharing a connector, you should consider the tuning that Adobe discusses in this 2014 post, still as valid today as when it was written for CF11:
https://coldfusion.adobe.com/2014/05/coldfusion-11-iis-connector-tuning/
If you struggle still, I can help via consulting, of course (if somehow I can’t answer questions here).
Sounds like this bug – https://tracker.adobe.com/#/view/CF-4205361
We had the same issue, there is a fix available listed in the comments
You must be logged in to post a comment.