tracker issue : CF-3859968

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

Upgrade from CF10 to CF11 leaves the IIS Handler Mappings pointing to CF10 directory

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Eric Tabet / Eric Tabet (etabet)

Created: 12/01/2014

Components: Installation/Config, Installer

Versions: 11.0

Failure Type: Usability Issue

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Normal / Most users will encounter

Locale/System: English / Win 2012 Server x64

Vote Count: 1

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on February 18, 2019 using build 2016.0.01.298513
Problem Description:
When upgrading from CF10 to CF11, the IIS connector doesn't change the IIS handler mapping directory, resulting in issues extremely difficult to troubleshoot.

Steps to Reproduce:
Install CF11 on existing CF11.
Select "Replace" (and not "Coexist")

Actual Result:
ISAPI filter is properly updated to new CF11 location but:
Handler mapping for cfc, cfm, cfml, cfr; cfswf are still pointing to CF10 directory
This results in 503 errors.

Expected Result:
Handler Mapping should be updated with latest directory, in sync (both ISAPI filter and handler mapping should be coherent)

Any Workarounds:
Manually updating IIS handler mapping - but this is not documented anywhere.

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

Watson Bug ID:	3859968

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

Windows 2012 x64


  1. December 02, 2014 00:00:00: 1_Wrong_Handler.PNG
  2. December 02, 2014 00:00:00: 2_Previous_CF_Detected.PNG


etabet, Can you please elaborate on the following step mentioned in the bug description: "Select "Replace" (and not "Coexist")" At what point in the installation, un-installation or configuration workflow, do we see this? When you are re-configuring a website that is already configured with and old version of CF (say 10), with a new version of CF (say 11), without un-installing the older CF, the old connector should first be manually un-installed, by running the wsconfig tool (<cf_root>\cfusion\runtime\bin).
Comment by Piyush K.
9837 | December 02, 2014 12:29:59 AM GMT
This question gets asked during install on the step labelled "Previous ColdFusion Installation Detected" I am attaching a screen shot of that step. If the installer detects the previous version, why doesn't it say that we should uninistall the previous connector - or why doesn't it actually offers to do it. Regardless, the option "Configure my web server for ColdFusion 11" is unambiguous and, obviously, does NOT work. So it should be fixed.
Comment by External U.
9838 | December 02, 2014 05:00:36 AM GMT
Hi Piyush, I see this is marked Open/ToFix, so I want to add an important note: I (and I'm sure others) run CF10 and CF11 side-by-side (especially for testing) and do not want installer automatically unconfiguring all IIS sites. If an _option_ to do so is added to installer, then that's fine (and a good idea). But please don't make it happen automatically. Thanks!, -Aaron
Comment by External U.
9839 | December 08, 2014 04:06:31 AM GMT
+1 for an installer _option_ to unconfigure IIS (but pls do not make it happen automatically, b/c sometimes devs actually want CF10 and CF11 co-existing in IIS)
Vote by External U.
9843 | December 08, 2014 04:08:05 AM GMT
Aaron, Please take a look at the attached image "Previous CF Detected.PNG". The option to "replace" or "coexist" is *already* part of the installer. But when you select "replace", it does NOT replace. That's the bug.
Comment by External U.
9840 | December 08, 2014 04:16:23 AM GMT
Hi etabet, I never choose the "coexist" option, as I have my CF10 and CF11 co-existing inside IIS (not co-existing by having 1 version using the built-in server). Example: 1) Install CF10 and choose to configure IIS for all sites 2) Install CF11 and choose "Configure my web server for ColdFusion 11 (recommended)" 3) On next screen, I choose the option to only configure CF11 for 1 specific IIS site (not "All") That said, I think I misunderstood the actual issue. I believe I do recall that 1 site not being unconfigured for CF10 nor configured for CF11. When I get a chance, I'll uninstall/re-install and see if I in-fact see the same too. Thanks!, -Aaron
Comment by External U.
9841 | December 08, 2014 05:17:14 AM GMT
To avoid issues arising out of this scenario, connector configurations to already configured sites (with another version of ColdFusion) will not be allowed.
Comment by Immanuel N.
9842 | September 28, 2015 05:20:48 AM GMT
Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). wsconfig disallows configuring already-configured sites. Thanks!, -Aaron
Comment by Aaron N.
30314 | February 18, 2019 09:37:20 AM GMT
Hi Adobe, This was not properly fixed. I'm reverting my 02/18/2019 comment. Issues: 1) wsconfig doesn't hide websites configured for future CF versions (ex: CF2016's wsconfig incorrectly lists websites configured for CF2018) 2) wsconfig doesn't correctly configure the virtual dirs (ex: jakarta) if the website was already configured for a future CF version (ex: CF2016's wsconfig leaves a previously-CF2018-config'd site's virtual dirs config'd for CF2018) To repro: 1) Add a new site in IIS: mysitecomcf2018 2) Using CF2018's wsconfig, configure mysitecomcf2018 for CF2018 3) Using CF2016's wsconfig, see mysitecomcf2018 is listed (bad) 4) Using CF2016's wsconfig, configure mysitecomcf2018 for CF2016 5) See mysitecomcf2018's virtual dirs (ex: jakarta) are still config'd for CF2018 (bad) Suggestion: wsconfig should -always- hide already-config'd websites, even if the website was config'd for a future CF version. I believe that was the intent of this fix, so can this ticket please be re-opened and my repro verified? Thanks!, -Aaron
Comment by Aaron N.
31140 | August 22, 2019 07:55:40 AM GMT