tracker issue : CF-3190071

select a category, or use search below
(searches all categories and all time range)

Cannot configure IIS connector, even with all required options installed

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Henry Ho / Henry Ho (Henry Ho)

Created: 05/15/2012

Components: Installation/Config, Connector

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final / 282511

Priority/Frequency: Major / All users will encounter

Locale/System: English / Windows 7 SP1 64-bit

Vote Count: 5

Problem Description:  I have installed all the required options, but still cannot configure IIS connector.

Steps to Reproduce: Run CF10.0 Release setup, and config with IIS for all IIS websites.

Actual Result:  "Cannot configures IIS connector.  Enable the required options ASP.NET, ISAPI Extensions and ISAPI Filter in IIS under Windows Features and try again.

Any Workarounds:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3190071


External Customer Info:
External Company:  
External Customer Name: henrylearn2rock
External Customer Email:  
External Test Config: My Hardware and Environment details:

- 64bit Win 7 Pro with IIS 7.5.7600.16385


  1. May 15, 2012 00:00:00: 1_Capture.PNG
  2. May 15, 2012 00:00:00: 2_Adobe_ColdFusion_10_Install_05_15_2012_01_34_04.txt


Found in Build should be Final (released May 14)
Comment by External U.
19460 | May 15, 2012 02:42:01 AM GMT
Same issue. I did notice that using the "Web Server Configuration Tool" does correctly list CGI in the error, but that's not much use when your still trying to install it for the first time.
Vote by External U.
19474 | May 16, 2012 08:40:11 PM GMT
Same error but I found that you needed to also have CGI installed.
Comment by External U.
19461 | May 16, 2012 08:41:09 PM GMT
I wonder what has changed that we now need CGI? ColdFusion has never ever needed this module installed for IIS in the past, so is there any documentation as to why we now need CGI module installed for IIS?
Comment by External U.
19462 | May 16, 2012 08:52:03 PM GMT
Found the problem! CGI is actually required, but the error message during the setup did not mention it. The one in Web Server Config Tool did.
Comment by External U.
19463 | May 16, 2012 10:52:41 PM GMT
CGI Option is needed to unlock the configuration setting for isapiCgiRestriction config in IIS configuration file. For more detail refer This option is required to be enabled to run any ISAPI modules (connector) inside IIS.
Comment by Kiran S.
19464 | May 17, 2012 12:01:25 AM GMT
Encountered on Final build
Comment by External U.
19465 | June 11, 2012 01:25:26 PM GMT
I was not able to install either. Error message needs tweaking, or Adobe needs to determine why CGI is needed.
Vote by External U.
19475 | August 23, 2012 03:54:29 PM GMT
In prod build.
Comment by External U.
19466 | August 23, 2012 03:55:04 PM GMT
Same Issue. Where to go from here?
Comment by External U.
19467 | September 13, 2012 09:18:41 PM GMT
Check the comment from Kiran below. You need to enable CGI option in IIS.
Comment by Rupesh K.
19468 | September 13, 2012 11:51:12 PM GMT
I ran into this as well and needed to enable CGI. Is this a bug in the installer or does CF10 really need the CGI option enabled in IIS?
Comment by External U.
19469 | September 25, 2012 04:44:15 PM GMT
I found this bug affecting Server 2008R2 Standard. It was a huge time waste! Small change of error message would resolve the immediate need. I can't understand why this hasn't been corrected yet.
Comment by External U.
19470 | October 14, 2012 12:48:20 PM GMT
Well I just wasted an hour tonight trying to figure out this one. This error still is occurring. You can't just issue an update for download later. You need to change the installer that we download from Adobe. This affects the installation process.
Comment by External U.
19471 | December 20, 2012 12:16:38 AM GMT
You have to update the installer we download from the Adobe website - patching CF AFTER the install fails to resolve the problem that happens DURING installation.
Vote by External U.
19476 | December 20, 2012 12:20:06 AM GMT
The problem with Kiran's answer is that even that website specifically says "You need to use this element to configure your Web server only when a site or application uses an application pool that runs in Classic mode." ColdFusion has never required this option for a number of years, so the question remains what has changed during the ColdFusion 10 beta installer, and the final product? The argument that the CGI option has never been needed in the past, is a strong indication in why it is needed know. So for peace of mind, why can't someone state very clearly why this has now a requirement during installation? Removing it after ColdFusion is installed, doesn't make ColdFusion not work any more. Unless it is a security risk, but again ColdFusion doesn't run in classic mode either, so it is not a required IIS feature either.
Comment by External U.
19472 | December 28, 2012 12:39:36 AM GMT
It doesnt install on windows 8
Vote by External U.
19477 | January 02, 2013 09:40:31 AM GMT
Whiskey tango... Nearly two years later, this is still the case in Coldfusion 11 for Windows Server 2012 R2. Enabling CGI lets me bypass this issue; message didn't say I needed it, nor did it say what version of Adobe are so incredibly useless at reading any sort of feedback to Coldfusion that it really *hurts*. I have developed on the platform for well over a decade.
Comment by External U.
19473 | September 19, 2014 08:58:14 PM GMT
Message needs to say CGI is also needed. Adobe seriously needs to read their feedback and keep up to date. This is a two year old issue still not resolved in CF11.
Vote by External U.
19478 | September 19, 2014 08:59:35 PM GMT