When I configure the connector for IIS in 2016 vesion, it prompt error "all the iis sites are already configured by some other version of coldfusion", how can I removed the configured IIS for other version? Thanks
Copy link to clipboard
The simple answer is by running the wsconfig tool for that other version.
If you don't know what "other version" that is, you can go to an example site in iis, to its "isapi filters" feature, and you should see a tomcat filter. What version of CF does that point to?
Then run the wsconfig.exe tool in that cf instance's runtime/bin folder, running it "as admin", to remove the old connector.
Then you should be able to add the new connector with the wsconfig tool of the new cf version.
If you stumble, there are so many things that could be amiss that we might not easily resolve them with back and forth here (though we may). If you just want help to get it working, it shouldn't take even 15 mins to sort out in an online consulting session. If interested, see carehart.org/consulting.
Otherwise, hope what I shared above may get you going.
I saw your reply about "Re: all the iis sites are already configured by some other version of coldfusion ", is that mean if "isapi filters" exist the tomat information(first pic), means the connector is created ok? If so, when I use wsconfig tool, I create one sigle site for this, but it has error, how can I check and solve this error(second pic)? Thanks
There is a solution for you. But first, I will say that you confused matters when you referred to "2016 version" initially. I thought you were referring to CF2016, but the screenshots in your last comment show you using CF2021. Perhaps you were referring to Windows 2016.
Anyway, now that I see the nullpointer errors you are getting from the wsconfig tool, I can report that Adobe HAS in fact recognized and resolved the problem, which will be included in update 1 of CF2021 (whenever that comes out).
Until then, they ARE offering that updated wsconfig.jar file (which is what's used by the wsconfig.exe tool you are running). And you can get that via a link offered by Adobe in the tracker ticket created for this issue, https://tracker.adobe.com/#/view/CF-4210996. See there the steps for how to use it, including how to clean up vestiges of the old connector.
And if you or anyone else may want to see more discussion of the problem, the first forum thread reporting it here in December (with discussion in Jan, Feb, and Mar) is at
Let us know if that solves the problem for you. And as I offered above, if you feel stuck resolving things I can quickly help get everything working, via a shared desktop consulting session. Or you can certainly ask follow-up questions here. (I'm just not as able to keep close track of this or even private messaegs sent in these forums, so use that link I offered in my signature to reach me directly.)
Hi, before I got this answer, I update the applicationHost.config under the Windows\System32\inetsrv\config, delete the ColdFusion related in the configuration file, then uninstalled the ColdFusion I installed. After reinstalled, seems it is OK, is this solution OK for solve above issue? Thanks. By the way, as I post before, verion 2016 means CF2016 version. If there is problem in the future, I will post message again. Is there one Real-time communication if I encounter emergent issue? Seems post message need take one or more day to get the response. Thanks again.
Yes, cleaning out the applicationhost.config is one aspect of removing all the vestiges of the previous connector, as indicated in the Adobe post I linked to.
As for your saying that in the original question, "2016 means CF2016 version", that's only all the more confusing because again your second reply shows a screenshot using CF2021. But anyway, you have solved your problem and that's what matters most for you.
As for getting real-time help, no, this Adobe CF commmunity site does not offer that. You can find that in the CF Slack channel. For more on that and other community/help resources, see a list of them I keep at https://www.cf411.com/cfhelp. (Different people will likley step up to help in the different communities, of course.)