Copy link to clipboard
Copied
I have installed ColdFusion 2016 in IIS 10 and when I browse to http://localhost/mysite/ I get HTTP Error 404.17 - Not Found but when I browse to http://localhost/mysite/index.cfm it works just fine. It seems there is some confusion about the default documents being served as static files rather than dynamic files. This is supported by reading further details in the IIS error message:
It seems that IIS knows that I want to serve index.cfm as the default document, but it's treating it as a static file rather than a dynamic file. Wondering if anyone has any ideas on how to fix this? Thanks.
Copy link to clipboard
Copied
Hi,
Can you please check the default document and check what it set there. Also, remove the connector and add the individual connector for that specific website and then run the index page.
Thanks,
Priyank Shrivastava
Copy link to clipboard
Copied
Thanks for your response Priyank. The default document setting is below:
index.cfm
default.cfm
index.php
Default.htm
Default.asp
index.htm
index.html
iistart.htm
default.aspx
Regarding your suggestion to remove the connector and add it again, I used the ColdFusion 2016 setup program to install the IIS connector, so are you suggesting that I use the Web Server Configuration Tool to remove ColdFusion from IIS and then add it again?
Just to be clear, ColdFusion is working fine if I specifically browse to http://localhost/mysite/index.cfm, it's just that if I browse to http://localhost/mysite/ that it thinks the index.cfm page is static content.
Copy link to clipboard
Copied
Hello Priyank. I appreciate your previous reply. I'm wondering if you have any other suggestions for me?
Copy link to clipboard
Copied
Hi,
Can you please remove all the connectors and create the connector with individual sites and then try.
Thanks,
Priyank Shrivastava
Copy link to clipboard
Copied
Hi Priyank. Unfortunately that did not fix the problem. Any other ideas? Thanks.
Copy link to clipboard
Copied
Uninstall all connectors. Reinstall them, making sure you run the web server configuration tool as administrator. After installing, check each site in the IIS Management Console and see whether the CF IIS Handler Mappings for each site actually point to the right site number - each IIS site has its own number and each web server configuration will have a corresponding directory. Also, make sure each IIS site has a /jakarta virtual mapping in IIS.
Dave Watts, CTO, Fig Leaf Software
Copy link to clipboard
Copied
Hello,
I am also having the same issue, I have followed all the instructions mentioned here but continue to get the same error, Any suggestions on how to resolve this issue.