Skip to main content
S
sikandera93427573
Participating Frequently
September 4, 2018
Answered

404 - File or directory not found for second coldfusion site in IIS

  • September 4, 2018
  • 1 reply
  • 4673 views

Hi,

I've installed coldfusion 2018 on windows server 2016 and added 2 websites in IIS one is loading coldfusion page fine and second one is throwing 404 error physical path of both IIS websites is same C:\inetpub\wwwroot\ Any idea what would be going wrong ? Hosting server is AWS EC2 windows instance.

Thanks !

Sikander

This topic has been closed for replies.
Correct answer Priyank Shrivastava.

Hi Sikander,

You have to remove the connector using the wsconfig utility and re-add it. Please follow the steps.

Go to ColdFusion2018\cfusion\runtime\bin and run the wsconfig.exe as Run as Admin. Remove the current entry and re-add it with ALL website and then check your other website.

Thanks,

Priyank Shrivastava

1 reply

Priyank Shrivastava.
Community Manager
Priyank Shrivastava.Community ManagerCorrect answer
Community Manager
September 4, 2018

Hi Sikander,

You have to remove the connector using the wsconfig utility and re-add it. Please follow the steps.

Go to ColdFusion2018\cfusion\runtime\bin and run the wsconfig.exe as Run as Admin. Remove the current entry and re-add it with ALL website and then check your other website.

Thanks,

Priyank Shrivastava

Thanks, Priyank Shrivastava
S
sikandera93427573Author
Participating Frequently
September 6, 2018

Hi Priyank,

I'm having this issue all over again site 1 working http://18.223.41.230/index.cfm site 2 throwing 404 again http://18.223.38.196/test.cfm​ and it isn't going away this time around by adding removing connector PFA

I'm wondering if it's Coldfusion 2018 that sucks or if it is AWS ec2 hosting that is not compatible with cf ?

Any idea ?

Best,

Sikander

D
Community Expert
Dave WattsCommunity Expert
Community Expert
September 6, 2018

There is nothing about EC2 that would make it incompatible with CF. It's just a virtualized environment like VMware. We run tons of EC2 servers with many different versions of CF.

And I don't think it's CF 2018 that "sucks". It works pretty much like every other version of CF does, in this regard.

So my guess is that you haven't completely uninstalled the previous connectors before reinstalling them. This seems more to be an IIS and Tomcat issue than anything else. It can be annoying until you've gotten it right. You should look for any traces of the connectors before reinstalling them. Through the IIS console, you can do this by looking at handler mappings, ISAPI filters (I think, it's been a while), jakarta virtual directories, etc. If you prefer looking at text/XML files, you can look at each site's web.config and the server's applicationHost.config.

Dave Watts, Fig Leaf Software

Dave Watts, Eidolon LLC
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices