Skip to main content
S
SSTWebworks
Known Participant
January 31, 2018
Question

ColdFusion 2016, IIS 8.5, ColdFusion pages 404 out

  • January 31, 2018
  • 2 replies
  • 1355 views

All,

I have an unusual issue with ColdFusion. I'm running ColdFusion 2016, IIS 8.5 on Windows 2012 R2. in a VMWare virtual machine. I've had to do several things to accommodate a new site on this server . We're also running the CommonSpot Content management system.

The original site  "http://site-comspotAuth" runs fine ("site-comspotAuth" is the machine name with DNS being handled by Windows DNS servers inside our network). In order to add a new site to this server, I've had to change the site name to siteCSAuth and the new site is https://site2CSA.

NSLOOKUP, PING and TRACERT all appear normal

here's where things go weird:

The original site site-comspotAuth works, CommonSpot comes up and users can author, however the second site site2CSA delivers html but not cfml, I've run the WSCONFIG tool and the handler mappings seem correct.  This also occurs if I change the name and IP of the existing site which will be siteCSAuth in the IIS bindings. This all ran smoothly on our development server.

i'm at a loss to explain this and I'm under the gun to get this working.

This topic has been closed for replies.

2 replies

Charlie Arehart
Community Expert
Charlie ArehartCommunity Expert
Community Expert
February 7, 2018

SST, you didn't indicate if the site has the jakarta virtual directory, as I had also asked in my last comment. You only replied to the "run as admin" suggestion.

If you confirm that it's there and things still don't work, I'll offer this: there are too many variables that could explain what's happening. But I suspect I could get this working for you if we got together in a screen-share, where I could assess those variables and drive you to the explanation and solution, in perhaps as little as 15 minutes. I also have a satisfaction guarantee, so if we didn't solve it, you wouldn't have to pay for any time at all. For more, see carehart.org/consulting.

I appreciate that you may feel you should not need to pay at all for this help. Totally your call. It's just that some problems are not easily solved via back and forth in the forums. You see it's already been 8 days since you opened the thread. But some problems ARE easily solved once we're on your machine together and can assess the various variables.

/Charlie (troubleshooter, carehart. org)
S
SSTWebworksAuthor
Known Participant
February 7, 2018

Charlie,

I appreciate the offer, however this is a federal site and there are clearance issues involved.

The the jakarta virtual site was created by the wsconfig tool.

I've got this working, by using a port bind. Both sites are set to the same "All unassigned" with the site requiring SSL on port 443 and the one that doesn't in on port 80. While this doesn't use the domain names that I wanted it does get my users back into CommonSpot Authoring, at least until I can take this server down for an extended period to perform major surgery. I'm suspecting that this may require a reinstall of ColdFusion 2016, or worse an attempt at reinstalling IIS (or just have a new base VM created and move the code over).

D
Community Expert
Dave WattsCommunity Expert
Community Expert
February 7, 2018

I've never found a situation like this which reinstalling either CF or IIS fixes. But I have found situations where the wsconfig stuff that's been created previously has conflicts with new wsconfig entries - there's a numeric list of them that is supposed to match the list of numbers that IIS assigns to sites. In one or two cases, I've found that this didn't match, and I would either have to directly make entries in the appropriate config files (web.config and applicationHost.config) or remove and reinstall all connectors.

Dave Watts, CTO, Fig Leaf Software

Dave Watts, Eidolon LLC
D
Community Expert
Dave WattsCommunity Expert
Community Expert
January 31, 2018

You need to take CommonSpot and some bits of ColdFusion out of the picture. Create a subdirectory in the new site, create an Application.cfm/cfc in the new subdirectory to prevent CommonSpot from interfering, create an index.cfm file in there, try accessing it using the file name and not using the file name. That will let you see if basic connectivity is working properly.

Then, look at your bindings. Chances are, your HTTPS binding is not working properly.

Dave Watts, CTO, Fig Leaf Software

Dave Watts, Eidolon LLC
S
SSTWebworksAuthor
Known Participant
January 31, 2018

This produced the same thing. I even turned off the require SSL settiing and created a standard binding to port 80.
steps: created a directory called test in the site root, added a blank Application.cfc to it and a file called test.cfm, inside test.cfm is a "hello world" wrapped in cfoutput tags, still 404s

S
SSTWebworksAuthor
Known Participant
January 31, 2018

More: created test.htm in the same directory, it 404s as well.
but.... index.htm in the root works.

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