I have a client that is running a classic asp site on IIS7. In order to see any errors from the classic asp pages, I modified the IIS7 Error Pages to point 500 and 500.100 errors to a special classic asp page that finds the last error and then appropriately logs it for the future (pretty much what Elmah does for asp.net). What we are seeing on IIS7 is an occasional error message from the exception logging classic asp page itself. And it appears it is for the 500 errors; 500.100 errors seem to get logged without any problems.
So two questions:
- How can I cause a plain old 500 error
(not 500.100) on this website to test
the classic asp page exception
- Is there a better way to
capture and log exceptions from
classic asp pages in IIS7?