CurrentDomain.UnhandledException being bypassed

23 Jan 2006 2:25 PM

Mark M

Hi All,

I have a transient problem that causes my .Net based NT Service to exit
unexpectedly. I have all code wrapped with exception handlers that write
to log file, Application event log or both. I hook
currentDomain.UnhandledException in the service's Main() entry point. The
handler logs error data to event log.

My service (.net 1.1 based) crashes and bypasses ALL exception handlers.
The only thing I have is an error message in the application log that
indicates the .Net Runtime encounted an unhandled exception. What sort of
problem would cause the .Net runtime to bypass all exception handlers in the
application?

Thanks!
- Mark

24 Jan 2006 10:05 PM

David Levine

An EngineExecutionException might do it; this indicates that the runtime
itself has been corrupted. This may be caused by incorrect interop that
causes internal structues to get overwritten. Another might be a stack
overflow or an out of memory exception.

Show quote

"Mark M" <m***@nospan.com> wrote in message
news:er7MqjCIGHA.1424@TK2MSFTNGP12.phx.gbl...
> Hi All,
>
> I have a transient problem that causes my .Net based NT Service to exit
> unexpectedly. I have all code wrapped with exception handlers that write
> to log file, Application event log or both. I hook
> currentDomain.UnhandledException in the service's Main() entry point. The
> handler logs error data to event log.
>
> My service (.net 1.1 based) crashes and bypasses ALL exception handlers.
> The only thing I have is an error message in the application log that
> indicates the .Net Runtime encounted an unhandled exception. What sort of
> problem would cause the .Net runtime to bypass all exception handlers in
> the application?
>
> Thanks!
> - Mark
>