Installing ColdFusion 9.0.1 Update

Some people might face a problem when installing ColdFusion update on their Windows 2008 Server. This is because they will have to remove ColdFusion 9 connector settings and IIS6 Metabase Compatability from IIS 7.

So, here is what you need to do to update your CF 9:


  1. Remove existing ColdFusion connectors from IIS 7.
  2. Shutdown ColdFusion services
  3. Run the installer (downloaded in step one)
    You'll note that after installation you'll get a message like this one:
    Congratulations. Adobe ColdFusion 9.0.1 has been successfully installed to:

       C:\ColdFusion9

    Press Done to quit the installer.

    Notes
    =====

    Solr Server has been upgraded. Reindex all the collections.

    Connector has been upgraded. If you use IIS 6 Management Compatibility, to use IIS 7 support, unconfigure (already configured) websites.
    Then uncheck all IIS 6 Management Compatibility options (Start > Control Panel > Programs > Programs and Features > Turn Windows features on or off > Internet Information Services > Web Management Tools) and then reconfigure all your configured websites using wsconfig tool. Ensure that unconfiguring of the websites is done before you disable IIS 6 Mangement Compatibility options.

    Note that this step is not mandatory. You have the option to continue using IIS 6 Management Compatibility.
  4. Start 'Server Manager' from Control Panel/Administrative Tools
  5. Scroll to 'Roles Summary' and Click on Web Server (IIS). (shown below)
  6. You will see a screen similar to the one below. The image below shows three sections: Events, System Services and Role Services.
  7. Since we have to remove specific services from Web Server (IIS) - click on 'Remove Role Services'
  8. You will see a window like the one below. Uncheck, IIS 6 Metabase Compatability and IIS 6 Management Console.
  9. When you uncheck, you might see a message saying that there are dependent services. Don't bother if it talks about IIS6 related services. Simple click 'Remove Dependent Role Services'. See below:
  10. Go ahead and finish the removal process.
  11. When the feature is removed, you will get confirmation (may get an error - just ignore). You will be asked to restart your windows server - click yes.
  12. Once your server completes the reboot, run the WSConfig.exe under Start menu > Adobe ColdFusion 9.
  13. Click 'Add' - a pop up window will appear that looks like the one below:
  14. Select the Configure web server for ColdFusion applications option, and click OK.
  15. Click ok.
  16. Now restart your IIS7 and you're done.

I hope this helps. If you face any issues, let me know.

Comments

  1. Step 1 and Steps 12-15 can incur a lot of server down time if your server has many sites on it.

    On the server that I'm working on it takes approximately 25 seconds to remove the connector for each site and it takes the same amount of time to add it back.

    I have 800+ sites on the server. 333 minutes for step 1 and 333 minutes for steps 12-15.

    That totals approximately 12 hours of down time on a production server.

    There is no progress bar for either process so you have no idea how much time it will run.

    Plan accordingly...

    ReplyDelete
  2. Given the above time commitment, you may consider keeping the IIS 6 metabase role. From what I have read on other blogs/sites this is possible and is a much faster upgrade.

    ReplyDelete
  3. Two more apparent reasons not to upgrade to IIS7 native support:

    1) The Web Config tool requires ASP.NET to be installed in this mode. This means adding and running modules that you otherwise don't need (assuming your apps are all CF only). For security and simplicity I prefer only to run services/modules I need.

    2) Having switched ot IIS7 support, each time you add a new website you will need to run the Config tool again to add CF support to it (unlike IIS6 mode where all new sites inherit the config).

    Given all these downsides, are there any compelling reasons why you'd want to switch to IIS7 native support?

    ReplyDelete
  4. Correction to 1) above: it seems the web config tool in CF9.0.1 requires ASP.NET regardless of whether you use IIS6 or 7 modes. In which case I suppose you might as well go with the native support.

    ReplyDelete
  5. sorry for a silly question but how do we Remove existing ColdFusion connectors from IIS 7?

    ReplyDelete
  6. @Anonymous

    You can run the wsconfig.exe tool.... then choose to remove from 'All IIS website'.

    wsconfig is available from Windows start menu > Adobe ColdFusion.

    Or you can directly to *ColdFusion-Install-Directory*/bin

    -Sameer

    ReplyDelete
  7. I have just installed ColdFusion 9 (FOR 10th TIME) After installing 9 i went ahead and installed the update (9.0.1) - I did the installation be following your instructions - CF installed without any error,
    But now... I cannot get CF Application to restart. It give me the following error:
    "Windows could not start the ColdFusion 9 Application Server ... services-specific error code 2"
    I have checked the log file but cannot find anything???
    PLEASE - can someone help - this is driving me nuts

    ReplyDelete
  8. I know this is quite old, but I have just been through this pain but I have found a way to move the config from the individual sites (web.config) to the master IIS config file (applicationHost.config). In essence it means that sites inherit settings from the server level, like you used to be able to do. I have blogged it here as its a bit long winded
    http://mumblestiltskin.blogspot.com/2012/01/coldfusion-901-native-iis-7-support.html

    ReplyDelete
  9. We also facing problem but after reading your and its step we install easily.

    ReplyDelete

Post a Comment

Be relevant. Spammers will be banned.

Popular posts from this blog

Installing ColdFusion on IIS 7 + Configure IIS for ColdFusion in Windows Vista and Windows Server 2008

ColdFusion Manual Configuration & Issues with TCP ports 51011, 51010 and 51800 on IIS and Apache

Configuring Apache Tiles to Avoid Caching During Development