Classic ASP on IIS7: refusing to send errors to browser on 500 Internal Server Error

60
votes

I have classic ASP running on IIS 7.

Even though I configured the ASP "Debugging Properties" to "Send Errors to Browser = True", the web app REFUSES to send errors to the browser and continues to send a 500 internal server error.

  • My browser has "Show Friendly HTTP Error Messages" unchecked.
  • Failed Request Tracing is installed (not sure if that's related)
  • Happens both on web pages loaded locally on the server and remotely
  • The App Pool is integrated (not sure if that matters)

Any ideas?

6
iis-7asp-classiciis-7.5

6 Answers

93
votes

Try : Internet Information Services (IIS) Manager —> Default Web Site —> Click Error Pages properties and select Detail errors

9
votes

I was having the same issue with a Classic ASP app running in a subfolder of a site. I had enabled detailed errors and the 500 was still showing. My resolution was to enable parent paths in the ASP section in IIS for the site as the application was referencing the parent folder using "../":

CEnable Parent Paths for Classic ASP - IIS

7
votes

I had this occuring on a Classic ASP application running in a subfolder of a site. The solution was:

IIS > Click into your Site > Click into your Application folder > Error Pages > Edit Feature Settings > set to: Detailed Errors

7
votes

IIS Manager >> double click the ASP icon to open the ASP page. Expand the Debugging Properties node and set Send Errors To Browser to True.

enter image description here

enter image description here

Refer : http://www.chestysoft.com/asp-error-messages.asp

3
votes

If you are hosting the project in a shared environment then you can use the following snippet to view the errors.

<configuration>
<system.webServer>
    <httpErrors errorMode="Detailed" />
</system.webServer>
<system.web>
    <customErrors mode="Off" />
    <compilation debug="true" />
</system.web>

Refer this URL for complete information http://blogs.iis.net/rickbarber/working-past-500-internal-server-error

Hope it helps someone

2
votes

If your website is configured to connect to the physical path of the website as a specific user, instaed of using pass-through authentication, you may get this error if there is a permissions error with this user. It may also be necessary to restart the Windows Process Activation Service and then restart IIS.