C
Charles Evans
Morning!
I have this C# application that occasionally crashes complely and doesn't
return any error to the VS IDE. The crash comes as a Microsoft error dialog
stating "Application.Exe has encountered a problem and needs to close.". It
allows me to examine an error signature but i have no idea how to use this
to my advantage. When I click debug I get an error message from the JIT
debugger stating that an "Unhandled Win32 Exception" has occured in
Application.exe. However, a debugger that cannot handle the exception type
is already attached to the process." FYI: I am running the application
through the VS IDE.
The strange thing about this error is that sometimes the application is
dormant (no user activity) but will crash when another application starts.
My question is how I should go about trying to find out what is actually
causing this error. Are there some advanced debug tool out there that might
be able to provide some more information? I don't even know where to begin.
Also interesting to note is that this error only occurs when using the SAP
..NET connector. (v2.0). I have posted on the SAP connector forums about
this but so far no one else seems to have experienced this problem.
If anyone has any tips I would really appreciate them.
Thanks in advance,
Charles
I have this C# application that occasionally crashes complely and doesn't
return any error to the VS IDE. The crash comes as a Microsoft error dialog
stating "Application.Exe has encountered a problem and needs to close.". It
allows me to examine an error signature but i have no idea how to use this
to my advantage. When I click debug I get an error message from the JIT
debugger stating that an "Unhandled Win32 Exception" has occured in
Application.exe. However, a debugger that cannot handle the exception type
is already attached to the process." FYI: I am running the application
through the VS IDE.
The strange thing about this error is that sometimes the application is
dormant (no user activity) but will crash when another application starts.
My question is how I should go about trying to find out what is actually
causing this error. Are there some advanced debug tool out there that might
be able to provide some more information? I don't even know where to begin.
Also interesting to note is that this error only occurs when using the SAP
..NET connector. (v2.0). I have posted on the SAP connector forums about
this but so far no one else seems to have experienced this problem.
If anyone has any tips I would really appreciate them.
Thanks in advance,
Charles