asked on

CF 11 throws error after following lock-down procedure

Hi,

I installed CF 11 in a 2012 server a week ago using the CF 11 Lockdown Guide by Pete Freitag. I used the built-in web server to provide extra protection for the admin function. Am also using IIS 8.5. The initial process appeared to go smoothly. Was able to test the site internally using IE with both a test.htm and test.cfm file (it returned the #cgi.remote_addr# value).

Fast forward a couple of days and the application staff installed the real site. Can still access static pages but not CF driven pages any longer. Throws a HTTP Error 500.0 - Internal Server Error with an error code of 0x800700c1 from the cfmHandler. Looking that up, it gets thrown when a script mapping is not valid. Looking at the mapping for .cfm files it points to D:\ColdFusion11\config\wsconfig\2\isapi_redirect.dll, which is correct. That file does exist; the handler is invoked if the request is mapped to file or folder. I also see an entry under ISAPI Filters for tomcat which also points to the same dll.

Any suggestions where to look on this one?

--Ben

_agx_

CF 11 throws error after following lock-down procedure

I don't have an answer, but ... the title suggests the install was working at some point, but stopped working after applying the lock-down. However, the question suggests this is completely new install and you're not 100% certain whether the lock-down is what caused it to stop working or not. Can you clarify?

UPDATE:
1) Also, it might help to see the complete message from the IIS / Event Log
2) I assume everything is 64bit - Windows / CF Server / IIS Application pool?

Ben Conner

ASKER

Hi,

Yes, after the initial install, a simple 'hello world' type test.cfm file worked. Will pull the logs and post them later today. Am away from the office at the moment.

And yes, all is 64 bit; 2012R2, IIS 8.5 and application pool is 64, and the JVM is the 64 bit version.

--Ben

ASKER CERTIFIED SOLUTION

Ben Conner

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

_agx_

Glad to hear you got it sorted out.

Ben Conner

ASKER

Was able to isolate the problem to the root cause. And it was outside the scope of Cold Fusion in this instance, so continuing the thread would have no benefit.

--Ben