index.cfm not recognized as default document in IIS 7 after upgrading to ColdFusion 10

Today, I ran into a new problem when I re-installed ColdFusion 10 on a Windows Web Server 2008 R2. The ColdFusion page, index.cfm, is no being recognized as default document even though it is the highest priority one in IIS Default Document settings. I started with brief Googling with not much luck. I went back to the server and thought for a minute ‘why would the┬áindex.cfm not recognized as default doc in IIS 7?’. Then, it struck my mind that it could be missing handlers. Yes, that was the actual problem! When I uninstalled ColdFusion, the script mapping got deleted and did not get added during the re-installation.

Index.CFMProblem_Screen0

 

For those who have the same problem, here are the steps to follow:

1) Open IIS Manager (Start > Administrative Tools > Internet Information Services (IIS) Manager)

IndexCFMProblem_Screen1

2) Double click on Handler Mappings

IndexCFMProblem_Screen2

3) Right click and select ‘Add Script Map’

IndexCFMProblem_Screen3

4) Add entry to *.cfm pointing to isapi_redirect.dll executable from ColdFusion installation path.

IndexCFMProblem_Screen4

5) Repeat the same step for *.cfc as well.

BTW, this could happen when upgrading from ColdFusion 9 to ColdFusion 10 as well. The sites added in IIS after re-installation or upgrade of ColdFusion will not have this problem though. Hope this helps!

If you have any other problem or need help in installing or upgrading to ColdFusion 10, feel free to contact us.

2 Comments

  1. Andrew Scott says:

    The most simplest solution, would be to remove everything to do with ColdFusion in the IIS settings and run the Web Configuration tool to do all this for you.

    Works for me… Also the only reason this happens, is because sometimes ColdFusion doesn’t remove the handler mappings etc.

  2. If you create the connector at server level, then you may face this issue. Andrew’s suggestion works in almost all such scenarios. However, in case the same fails, the above workaround works fine. Just add cfm/cfml/cfc/cfswf/cfr.

    Alternatively, you can create site level connectors (only feasible, if you have less number of sites, otherwise, it becomes hectic) and you will not face the “default document” issue.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>