Unhandled exception in .NET runtime

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Arulvendan - 23 Dec 2005 11:59 GMT

We have developed a windows service in .NET 1.1 that uses Serviced components
for handling transactions. Some times, the service stops unexpectedly by
logging the following information in the Event log.

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

I understand that there can be a number of conditions that could have caused
this exception. How do I debug/trace the cause of this kind of exceptions?

Thanks,
arul

Reply to this Message

Naveen - 28 Dec 2005 15:22 GMT

There are few ways of debugging the unhandled exceptions

1)Sign for AppDomain.UnhandledException in your main method and log the
exception so that you can view the stack trace.
2)The other one is using the adplus.vbs (part of the windows debugger)
. use the adplus.vbs and the dump the memory using the "-crash"
option and investigate for the exception and the stack trace of the
exception.

.

Reply to this Message

Rate this thread:

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...