Tracking down exceptions in IIS Application

Is there any way to use dotTrace to track down the source of many exceptions getting thrown in an IIS Application.  These are handled exceptions that I'm trying to figure out if I can modify the code to not throw them.  Based on some perfmon data from a load test is seems I'm getting roughly one exception per request so I'm thinking something is not right, but need a way to find it.

1 comment

Hello Mark,

Sorry for the delay in replying. If you know the type of the exception being thrown, you can find where the corresponding constructor was called. Then you can open this call in a new tab and reverse the call stack (Back Traces).

Kind regards,


Please sign in to leave a comment.