I have a new website on CF2016 Enterprise. Its returning 500 - Internal Server Error when browsing .cfm pages. seems to be okay for .htm
The new second wesbite is my first time installing a second website on a CF server running mutliple CF servers which may be compunding the problem.
The website that is working does have a jakarta VD pointing to: C:\ColdFusion2016\config\wsconfig\2
The website that does NOT work has a virtual directory is pointing to C:\ColdFusion2016\config\wsconfig\1
I've run WSCONFIG ( as admin ) from the folder C:\ColdFusion2016\my new website folder\runtime\bin and it displays both websites the same:
I'm probably missing something obvious.
Ill try posting the image of wsconfig again:
Actually the error isn't related to setup.
A CF error message ( related to templates not being mapped ) displayed when I browsed the website on the desktop of the IIS server itself.
Something about the CF error message is causing the 500 error when the website is viewed.
Did you define the needed mapping in the instance whose web site is having the error?
Note that since you are using multiple instances (not multiple "servers" as you put it), each instance has is OWN cf admin. And since cf2016, that admin is reachable using cf's built in web server. The default cfusion admin would be at port 8500. The others two would be at 8501.and 8502, typically.
Note that the cfusion admin would offer a enterprise manager > instance manager page, which would be where you created your instances (the names on the right of your image above), and that same page would show you the actual ports of each admin. And the last button to the left of each row in that ui will open the admin in your browser for you.
If your code (running in the first instance) needs a mapping, that can be defined in that instance's admin. FWIW, any settings in the cf admin of the cfusion / 8500 instance would have been propogated into a new instances admin: but only at instance creation. After that, they are independent of each other.
Finally, it's worth mentioning also that you can define needed mappings in the application.cfc or cfm rather than (or to override those) in the cf admin.
Let us know how things turn out.
Try removing and adding back web server configuration for that website in wsconfig(Every time you remove and add please do a refresh on the website for that website). In IIS, make sure you've all 5 .cfm handler mappings for the newly configured website. Then create a test.cfm with some dumping CGI or any output and browser this file from IIS. In first attempt place this test.cfm outside of your project folder because it might override any logic blocking in your app.cfc or app.cfm.If everything goes well repeat the same step this time adding test.cfm in your project folder. (This process is to make sure you have the configuration between web and app server.
If this is blocking in your project start the debugging process in app.cfm and index.cfm.
You can also give a try in contacting email@example.com for installation Adobe provides free support.