Thread: Error Handling
View Single Post
  #3 (permalink)  
Old November 14th, 2003, 10:51 AM
planoie's Avatar
planoie planoie is offline
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts

Something note with ASP error handling is that there is no "On Error Goto ...". You can only ".. Resume Next".

If you can expect what errors might occur (like a database call where the database might be unreachable), then you can use "On Error Resume Next" before you run that code. Then you can query the Err object for error specifics and close out gracefully by displaying a more pleasant message.

For unexpected errors, I'm recommend what Balakumar suggested even though it's not really handling the error. In IIS you can choose Custom Errors for a web site or virtual directory and specify what page it goes to. In IIS there is usually a web already set for IISHelp. Go to the properties dialog of your "Default Web Site" in IIS manager. Go to the "Custom Errors" tab, and scroll down to the HTTP Error "500;100". Click "Edit Properties", change the "Message Type" to "URL" and enter "/iisHelp/common/500-100.asp" for the URL value. OK everything. Now at least you will get detailed error messages. For a production system, you could change this default 500-100 page with another page that is actually in your application. You could have this page generate an email with the error details that goes to your webmaster account (or wherever you choose).

Work smarter, not harder.
Reply With Quote