Skip to main content
September 4, 2013
Question

need help with legacy application.cfm Getting 500-internal server error (with CF-10) it used to work

  • September 4, 2013
  • 2 replies
  • 10001 views

We bought CF-10 standard edition and pulled legacy .cfm over.  When we try to open it in a browser, I get a 500 - internal server error.

When I rename my application.cfm  and open the browser, my legacy pages display,  but with "session errors" due to the session variables not being passed.

My logon code is built into the application.cfm

we still have our older version of CF installed on another server, and the logon page displays fine. My application.cfm doesn't have errors.

I read that others can use legacy application.cfm and I need to use mine. I don't know where to start to correct a 500 internal server error.

Can someone help me with this? (please?)

    This topic has been closed for replies.

    2 replies

    Inspiring
    November 18, 2013

    This worked for me today. And yes CF10 handles errors differently than previous versions!!!

    In the CF Administrator, go to the "Settings" section. You'll see "Settings" in the left menu near the top.

    If there is a checkmark in the area labeled "Enable HTTP status codes", remove it. Go to the bottom of the page and click on "Submit Changes."

    When I did this, my errors including line numbers appeared again.

    Hope it works for you...

    Anit_Kumar
    Inspiring
    September 4, 2013

    Hello sqlgirl,

    Thank you for your post. The error 500 is a generic error thrown by IIS. IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.

    One possibility is, IIS was not able to access the web.config file for the Web site or application. Please check the permissions.

    The handlers might be causing the issue. Please remove the connector. Make sure you launch wsconfig with Run as Administrator while remove/adding connector. Check in the IIS manager for handlers, cgi restriction for connector dll entry (isapi_redirect.dll) and remove them manually if exist. Then only recreate the connector.

    Also, please tune your application by applying the steps mentioned at http://blogs.coldfusion.com/post.cfm/tuning-coldfusion-10-iis-connecto r-configuration

    Hope it helps.

    Regards,

    Anit Kumar

    September 4, 2013

    Thank-you for the quick reply.

    I hope this fixes the error.