Skip to main content
Participating Frequently
January 2, 2018
Question

ColdFusion 2016 in IIS 10: HTTP Error 404.17 - Not Found

  • January 2, 2018
  • 1 reply
  • 3531 views

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:

HTTP Error 404.17 - Not Found

The requested content appears to be script and will not be served by the static file handler.

Most likely causes:

  • The request matched a wildcard mime map. The request is mapped to the static file handler. If there were different pre-conditions, the request will map to a different handler.

Things you can try:

  • If you want to serve this content as a static file, add an explicit MIME map.

Detailed Error Information:

Module   StaticFileModule
Notification   ExecuteRequestHandler
Handler   StaticFile
Error Code   0x80070032

Requested URL   http://localhost:80/mysite/index.cfm
Physical Path   C:\inetpub\wwwroot\mysite\index.cfm
Logon Method   Anonymous
Logon User   Anonymous

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.

This topic has been closed for replies.

1 reply

Priyank Shrivastava.
Community Manager
Community Manager
January 9, 2018

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

Thanks,Priyank Shrivastava
Participating Frequently
February 5, 2018

Hello Priyank. I appreciate your previous reply. I'm wondering if you have any other suggestions for me?

Known Participant
February 8, 2019

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


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.