Yep, to what Dave says.
1) And I’d go still further to say first that before removing them all (if you go that route):
a) You may want to backup the /config/wsconfig folder. It’s small, and could help you revert things I’m about to mention.
b) Note (in the wsconfig tool) what sites (if any) have their own connector. You could have it set so that all sites use one connector, or all use one but some others use their own, or all use their own. If you want to put it back that way, you want to take note of that before removing them.
c) Note as well that someone may have tweaked the workers.properties file in each connector folder (numbered folder under /config/wsconfig). You may want to be able to recover those changes, or at least assess whether you should
2) Then, second after removing them all, it would be wise to make sure that all remnants of connections to CF in IIS are gone. That means ensuring (at the server level and each site) that a) there are no more Tomcat “isapi filters”, b) there are no more “handler mappings” for cfm and related extensions, and c) there are no more Jakarta virtual directories in each site.
It’s possible that while you always did a “Run as admin” to add connectors, someone else could have missed that. Or they could have hand-crafted the above CF-related settings in IIS. The wsconfig tool may not know to remove those.
While you could check the above one at a time in each site, you can also check it by looking for the related XML entries that IIS would put into its respective config files. You would look a) in any web.config for the webroot of each site, then b) the \windows\system32\inetsrv\config folder and its applicationhost.config. There should be no remaining references to coldfusion or the cfm extension (for instance) in those files, once you use the wsconfig tool to remove all connections.
Now, removing things from those (if left there) is indeed a bit “surgical”, to use your term, but it’s minor surgery if done right. But even minor surgeries can turn deadly if an unprotected germ gets in (or for Seinfeld fans, if Kramer drops a junior mint into the patient from the surgical observation balcony). So do be very careful. Once false removal of a bracket (or mistakenly leaving one) and either the IIS UI for that feature won’t work, or perhaps the site itself won’t start, or in a worst case perhaps IIS would not, or would not work right. But it’s really easily done if one is familiar with it.
And it’s these things that I’d have led you through. I can’t elaborate on every point, or on other testing I’d have done before removing them. But Dave’s right that it should not require uninstall/reinstall of CF or IIS itself. So I add this in case you try the removal and recreation of all connectors, which is at least less onerous, if done carefully.
/charlie
/Charlie (troubleshooter, carehart.org)
15
Replies
AdChoices