Hi there,
You can customize the <customErrors> section in the web.config file, so on server errors (statuscode 500) the user is transferred to Error.aspx. In Error.aspx you can access the exception that occurred using Server.GetLastError().GetBaseException() and then diagnose the error.
For some errors, you can then customize your error message, or even redirect to an entirely different page.
However, it seems that you know in advance that certain exceptions can occur. Wouldn't it be much better to use a Try Catch block, catch the known exceptions and handle them at the class level?
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to:
Johnny, Kick A Hole In The Sky by
Red Hot Chili Peppers (Track 13 from the album:
Mother's Milk)
What's This?