October 7, 2016
Removing Corrupt Connector Dependencies from IIS
October 7, 2016
Removing Corrupt Connector Dependencies from IIS
Staff 2 posts
Followers: 0 people

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”.

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

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

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



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


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



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


  1. Repeat steps “-6-” to “-9-”, for all the sites with duplicate or corrupted connector settings.
  1. Navigate to the IIS Server home and double-click Handler Mappings.



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


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



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



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


  1. Remove all entries of tomcat as shown below:


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

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

2016-10-19 05:39:28
2016-10-19 05:39:28

@Peter, this doesn’t look like a ColdFusion issue. As suggested by James, you can try posting on http://stackoverflow.com/

2016-10-13 10:17:26
2016-10-13 10:17:26
2016-10-12 09:36:35
2016-10-12 09:36:35

I have a problem which I think is similar to the one you are addressing. I am a non-programmer, non-developer, and have inherited a web application. It’s running on Windows 2008r, IIS 7.5, Apache 2.2, ColdFusion 11.

For security reasons, I was informed that I needed to upgrade Apache 2.2 to Apache 2.4, which would take care of OpenSSL vulnerabilities (SWEET32).

I stopped Apache 2.2, disabled it, installed Apache 2.4 (and updated the references in the relevant .conf files to the new Apache24 directory). Installed Apache 2.4 as a service (it shows up in IIS Manager), but it won’t start. Instead, it gives me the following error message:

D:Apache24bin>httpd.exe -k install
Installing the ‘Apache2.4’ service
The ‘Apache2.4’ service is successfully installed.
Testing httpd.conf….
Errors reported here must be corrected before the service can be started.
httpd.exe: Syntax error on line 669 of D:/Apache24/conf/httpd.conf: Syntax error
on line 1 of D:/ColdFusion11/config/wsproxy/1/mod_wsproxy.conf: API module stru
cture ‘websocket_module’ in file D:/ColdFusion11/config/wsproxy/1/mod_websocket.
so is garbled – expected signature 41503234 but saw 41503232 – perhaps this is n
ot an Apache module DSO, or was compiled for a different Apache version?

I followed your directions to remove connections using WSCONFIG as admin, looked for the mappings and filters (none), and then used WSCONFIG as admin to reconnect to /Apache24/conf. The above error message is still there.

Is there anything I can do about that mod_webocket.so file?

Add Comment