Classic ASP application on IIS7 throwing 500 error

Question

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

I have done the following (as suggested in other posts) and still get the 500 error:

1. Set Send Errors To Brower = true in ASP properties in IIS
2. Unchecked show friendly errors in browser
3. Set Error Pages properties to show Detailed Error in IIS

ASP handler does seem to be mapped correctly.

The application pool has been set to Classic mode.

Any other ideas?

Solution 1

Finally sorted this out with the help of my sys admin!

The classic asp application was in a sub-folder. To get it working, the classic asp application's app pool had to be given access to the main folder and not just the sub-folder as it was using assets from the main folder.

Thanks heaps to all those who tried to help. Much appreciated.

Solution 2

From the IIS blog...

Script errors no longer shown in browser by default

As a result of our security paranoia, we turned off ASP's default behavior of sending script errors (including line number and code snippet to the browser.

...

To revert back to IIS6- behavior, simply run the following command:

%windir%\system32\inetsrv\appcmd set config -section:asp -scriptErrorSentToBrowser:true

Hopefully that will at least get you to the line that's throwing the error...

Solution 3

I suspect your running your AppPool under "Integrated" pipeline mode, change this to "Classic" and you should be right.

see this blog Running classic ASP on IIS 7