Classic ASP application on IIS7 throwing 500 error [closed]?

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...

Sorry, that didn't seem to work either. Still have same issue. – Shirlz Sep 14 at 2:11 Bummer.

How about this answer: stackoverflow. Com/questions/1453791/… – Farray Sep 14 at 2:21 Nope, have tried that too :( – Shirlz Sep 14 at 2:39.

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.

AppPool is running on classic mode only. – Shirlz Sep 14 at 2:07.

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.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.