Removing Corrupt Connector Dependencies from IIS

This blog post talks about a few scenarios related to connector misconfiguration and ways to handle them. The most common scenarios discussed in this article are

• Connectors that are created for ALL and individual websites at the same time.
• Multiple attempts to add/remove the connectors during configuration.

As a best practice, remove the connector using the WSCONFIG utility. Once the connectors are removed, verify that there are no residual files/settings/configuration remains, using the steps mentioned below. (WSCONFIG Utility location: ColdFusion<instance>runtimebin)

Consider a scenario where, upon launching the WSCONFIG utility, you see the following dialog box:

In this scenario, configuration conflict might occur, since the same connector is created for both ALL and individual website (for this case).

Follow the below steps to fix the connector misconfiguration:

1. Remove both the connectors one by one, as shown in the below image. Select the connector and click “Remove”.

2. In the dialog below, click “Yes” to continue.

3. You can see that the first connector is now removed.

4. Repeat the process for the other connectors. In this scenario, there are only two connectors.
5. Launch IIS Manager.
6. Click on any website (in this case, CF11) and double-click Handler Mappings.

7. Manually remove all the ColdFusion handlers as shown below (if present):

8. Navigate to “CF11” website and double-click ISAPI Filters.

9. Remove “tomcat” entries (if any), as shown below:

10. Repeat steps “-6-” to “-9-”, for all the sites with duplicate or corrupted connector settings.

11. Navigate to the IIS Server home and double-click Handler Mappings.

12. Remove all ColdFusion handler entries (if any), as shown below:

13. Navigate to IIS Server and double-click on ISAPI Filters

14. Remove entries for tomcat if any as shown below:

15. Navigate to IIS Server and double-click ISAPI & CGI Restrictions.

16. Remove all entries of tomcat as shown below:

17. Once all the above entries have been verified and removed, launch the command prompt as Administrator (or with elevated privileges) and run IISRESET.

18. Run the WSCONFIG utility to recreate the connector and test your website