Link to home
Start Free TrialLog in
Avatar of KingstonDeveloper
KingstonDeveloper

asked on

ASP classic app returns 500 - Internal Server Error on windows 2008 IIS 7

Hello,
I have 2 classic ASP applications: A and B. Application B is a sub app of app A.

Everything works fine from Windows 2000 IIS5 to Windows 2003 IIS6. However, when we migrate them to Windows 2008 server and IIS7, ASP pages under sub folder of app B return "500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed."

I tried to put a static html page under one of these folders and it was loaded on the web browser. So for some reason, ASP pages stop working on these folders. Here is the depth of the 2 apps A, B together:
http://webserver.company.com/appA/appB/employee/employee.asp

Anyone has come accross something like this? Anything I need to turn/set on/off in IIS7?

Thank you
Avatar of stevepicks
stevepicks

have a look at this
http://learn.iis.net/page.aspx/381/aspnet-20-breaking-changes-on-iis-70/
maybe it will give you an idea
Cheers
ASKER CERTIFIED SOLUTION
Avatar of Wayne Barron
Wayne Barron
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You'll need to switch "Show Friendly HTTP Error Messages" off in your browser first to get the correct error message.
There is no real problem running classic asp on IIS 7.x I know many large site do this.

A few things to do make sure the asp subrole to IIS is there.

Look in the IIS logs for any 500 error for classic asp.
 Here it logs more information if it is a general problem you will see the an additional subcode 500.xx etc that will point you in the right direction.

If it is to do with the code then just look in the fields for the error message (I think query string field) as this displays the full error message in words,.
Avatar of KingstonDeveloper

ASKER

Thanks for the link, Carrzkiss. I was able to find the error "Disallowed Parent Path". Looks like I will have some tidious work to do.

Thanks again.
Your welcome.
I know that I will one day need this information as well, so I have come somewhat familar with some of the issue with Classic ASP and Microsoft TRYING to get rid of it.
Of which will never happen, as if they completely get rid of ASP Classic.
Then the systems that still run it will thrive over the newer.

Take Care
Carrzkiss