Application has generated an exception that could not be handled.

[Guest]

Out .Net application is crashing occasionally after running for several hours with the error below in the EventLog.
We have attached a handler for the UnhandledException in the AppDomain which simply logs errors to the EventLog, but it looks the the CLR is going down in flames. Any ideas on how to track this down? Note that this is occuring on our production machine, so we don't have access to the debugger there

===============================================================
EVENT # : 82
EVENT LOG : Applicatio
EVENT TYPE : Erro
SOURCE : .NET Runtim
EVENT ID :
COMPUTER : MACHINE
TIME : 4/16/2004 9:38:30 A
MESSAGE : .NET Runtime version 1.0.3705.288- QMApp.exe - Common Language Runtime Debugging Services: Application has generated an exception that could not be handled
Process id=0x310 (784), Thread id=0xfc8 (4040)
Click OK to terminate the application
Click CANCEL to debug the application. ================================================================

 

[Christopher Kimbell]

Hi Philip

How about logging the StackTrace from the exception that is thrown? It may
give you some idea where in the program things go wrong.

Chris

Out .Net application is crashing occasionally after running for several

hours with the error below in the EventLog.

We have attached a handler for the UnhandledException in the AppDomain

which simply logs errors to the EventLog, but it looks the the CLR is going
down in flames. Any ideas on how to track this down? Note that this is
occuring on our production machine, so we don't have access to the debugger
there.

================================================================
EVENT # : 829
EVENT LOG : Application
EVENT TYPE : Error
SOURCE : .NET Runtime
EVENT ID : 0
COMPUTER : MACHINE2
TIME : 4/16/2004 9:38:30 AM
MESSAGE : .NET Runtime version 1.0.3705.288- QMApp.exe - Common

Language Runtime Debugging Services: Application has generated an exception
that could not be handled.

Process id=0x310 (784), Thread id=0xfc8 (4040).
Click OK to terminate the application.
Click CANCEL to debug the application.

================================================================

 

[Tian Min Huang]

Hi,

I agree with Chris that you should catch the exception and dump the call
stack so that we can check where the problem is originated from.

In addition, is it possible for your to post a simple project which is able
to reproduce the problem? That will be most helpful for us to pinpoint the
problem and resolution.

Have a nice day!

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

 

[Tian Min Huang]

Hi,

I am currently standing by for an update from you and would like to know
how things are going there. Should you have any questions or concerns on
the recent questions/ information I've posted, please don't hesitate to let
me know directly. It's my pleasure to be of assistance.

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.