Troubleshoot Process id Errors

[Guest]

We have a .Net application developed under FW 1.1 sp1. We run it under
Windows XP, Win 2000 Server & Pro & 2003 Server and it runs just fine. But on
one machine at one customer it will not run. Upon start up it throws this
error "Application has generated an exception that could not be handled.
Process id = 0x890(2192), Thread id = 0X1154(4436)"
The customer tells me that this machine is built exactly like another
machine (hardware & O/S, Win 2000 server) where it runs fine.
Customer has uninstalled & reinstalled the Framework as well as our app, to
no avail.
SO how do I go about figuring out what the real problem is to solve it?
Thanks
Gary

 

[Laura T]

Catch the unhandled exception to get the inner reason and possibly the call
stack.
Application.ThreadException event might just do it.
The reasons for unhandled exceptions are very broad, from security to
resources.

 

[Guest]

Now a basic question, How would I go about using the
Application.ThreadException event as you suggest? Would I have to reference
it just once at the beginning of the app or throughout where ever there is a
possiblity of an error?
Since this box is not available to our development enviornment we would have
to deploy a new app with this in it.
Thanks

 

[Laura T]

Just once, in the Main for example.

Application.ThreadException += new
ThreadExceptionEventHandler(Application_ThreadException);
// Load the form
Application.Run(new Form1());
Otherwise if you might want to attach a debugger (VS2005/WINDBG+SOS) in the
box.

 

[Guest]

Thanks i'll give this a try

Just once, in the Main for example.

Application.ThreadException += new
ThreadExceptionEventHandler(Application_ThreadException);
// Load the form
Application.Run(new Form1());
Otherwise if you might want to attach a debugger (VS2005/WINDBG+SOS) in the
box.