Global .NET objects in IIS issues

[Evan Freeman[C++ Samuri]]

Ok I have recently run into an issue in our production environment, and am
looking for solutions to error handling.

Inside the Global.asa file I use the object tags to create an application
level instance of my C# object. The object itself is a class that
encapsulates a thread. What it does is wake up every few minutes and cleans
up a hash table.

The problem is that on new machines the thread wakes up then ends up in a
Stopped State. I'm pretty sure this has to do with recent patching of some
kind, in if you patch before installing the application it fails, but if you
patch after install it works.

What I need to do is find a way to catch exceptions over the whole global
instance, but am unable to find a way to accomplish this. I have determined
that some exception of some sort is happening outside the scope of the
objects internal workings, but where it is a global created inside the
global.asa using the object tags I don't know how to trap the error so that
I can get useful information.

Is there a way to trap the error or is there some sort of IIS exception
trap/logging that I can turn on?

Any help is appreciated.

Thanks.

-Evan