Troubleshoot Process id Errors

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

G Hustis - 24 Jul 2006 16:36 GMT

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

Reply to this Message

Laura T - 24 Jul 2006 17:16 GMT

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.

> 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
[quoted text clipped - 10 lines]
> Thanks
> Gary

Reply to this Message

G Hustis - 25 Jul 2006 19:28 GMT

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

> Catch the unhandled exception to get the inner reason and possibly the call
> stack.
[quoted text clipped - 16 lines]
> > Thanks
> > Gary

Reply to this Message

Laura T - 27 Jul 2006 08:50 GMT

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.

> Now a basic question, How would I go about using the
> Application.ThreadException event as you suggest? Would I have to
[quoted text clipped - 32 lines]
>> > Thanks
>> > Gary

Reply to this Message

G Hustis - 28 Jul 2006 15:55 GMT

Thanks i'll give this a try

> Just once, in the Main for example.
>
[quoted text clipped - 41 lines]
> >> > Thanks
> >> > Gary

Reply to this Message

Troubleshoot Process id Errors

Free Magazines