Geek Answers Handbook

HTTP 500 Error Diagnostics in Classic ASP

I recently inherited a site written in classic ASP, and I'm currently trying to understand the state of things. The website works in production, but the development environment (hosted in a Windows Server 2003 window) causes an HTTP 500 error when trying to access it.

I understand that HTTP 500 errors simply mean that an unexpected server error has occurred, and that this is more than likely ASP code failure for one reason or another. I tried many browsers (IE, Firefox and Chrome), but they all have the same information.

As a first-class ASP.NET developer, I use the yellow death screen , which you can configure to display the stack trace.

So my question is: how do I convince IIS and / or classic ASP to give me the best hint of what causes the error?

Update: At first I had to stop in more detail, but here are some of the things that I looked at.

  • I looked at the event logs (Application, security, system, etc.) and nothing exists there.

  • I looked through the IIS access logs and I see access attempts and a total of 500 errors. It is even producing 500 errors on favicon.ico

+5
source share
5 answers

, " HTTP", , "On Error Resume Next" response.write. , , .

, , - IIS dev?

+5

- Event Viewer ?

+1

alex, , " HTTP" Internet Explorer, ; , , ( - ASP.NET) .

+1
source

If you have a global.asa file in your web directory, you can rename this file and try downloading the favicon.ico file again. If it loads, the problem is global.asa

0
source

It is clear that the old question, but why is it worth it, if you have access to the development server (direct or remote desktop), you can access the site from there. Local queries show more debugging information about classic ASP, including line numbers.

0
source

More articles:


All Articles