Classic ASP logbook (errors 500 and 500.100)

Question

I have a client that runs a classic asp site on IIS7. To see any errors on the classic asp pages, I changed the IIS7 error pages with errors 500 and 500.100 to a special classic asp page that detects the last error and then correctly writes it to the future (pretty much what Elmah does for asp .net). What we see in IIS7 is a random error message on the page of the exception logging asp page itself. And it seems for 500 errors; It seems that 500.100 errors are logged without problems.

So, two questions:

• How can I cause a regular old 500 (not 500.100) error on this website to test the classic asp logging page exception?
• Is there a better way to exclude capture and log from classic asp pages in IIS7?

Answer 1

Two questions - two answers:

• you can raise an error with the following err.raise nr, source, description
• The error handling you use (modifying error pages) seems to be a common way for classic asp applications.

Answer 2

Write down the code, mostly bad. Create a connection to db that does not exist. Create an object that is not installed. Create a string variable that is a word and multiply it by 5.