Skip to main content
Known Participant
March 16, 2013
Question

Trying to access my site without index.cfm fails

  • March 16, 2013
  • 1 reply
  • 941 views

Hi folks

Today installed CF10 Standard edition on a server that had been using CF7.  Figured it was time to get current.  This server is running Win2003/32bit and IIS 6. 

Anyway, after configuring CF10, if I access a few of my sites using just the URL without "/index.cfm", I get the following IIS error:

Page Cannot be displayed:

HTTP Error 403.1 - Forbidden: Execute access is denied.
Internet Information Services (IIS)

Now, if I include "/index.cfm" all seems to work fine and I can login/navigate my site fine. 


I've confirmed that index.cfm is in my default documents panel in IIS6 and I've even run the remove_ALL_connectors.bat and then reconfigured them and still no luck.  The same ones that worked before, work now.  The ones that didn't, still don't.


Now full disclosure, since I read CF10 could live alongside CF8, CF9, I stopped CF7 but left it installed when I installed 10.  Then after 10 seemed to be working fine, I uninstalled CF7.   So that's when I noticed this issue.  Upon looking at it, I decided to reboot and reconfigure the IIS connectors but that didn't seem to help.

Any ideas?  Thanks.


S

This topic has been closed for replies.

1 reply

srushingAuthor
Known Participant
March 16, 2013

So just to add to this a little...i decided to uninstall CF10 since it felt like maybe the CF7 uninstall may have screwed things up.  Anyway, I uninstalled CF10 and then reinstalled it and it still acts the same way. URLs with /index.cfm seem to work fine but URLs without it fail.  All have index.cfm as the only default document in the IIS setup. 

Anit_Kumar
Inspiring
March 19, 2013

Hi,

Please ensure all of these IIS features are enabled:

  • ASP.NET
  • CGI
  • ISAPI Extensions
  • ISAPI Filters

The Default Document list (this list will be created when the configuration is added) is mentioned in web.config file at C:\inetpub\wwwroot\. Just rename the web.config to web.config_old and restart IIS.

Regards,

Anit Kumar

Participant
March 22, 2013

Same problem here. With IIS6. web.config is used only in IIS7.