ERROR: Application has generated an exception that could not be ha

[Guest]

I'm not a developer, so please bear with me on this.

We have several Win2k Pro machines with .NET Framework 1.1 SP1 (KB886903)
installed. A Ghost image was taken from one PC and applied to all the
others. Our developer created a .NET app that works on the original PC,
but not on the others. The following error occurs as soon as the app is
executed:

"Application has generated an exception that could not be handled" followed
by process and thread IDs.

Then when I click OK, I get the following:

"Registered JIT debugger is not available. An attempt to launch a JIT
debugger with the following command resulted in an error code of 0X2 (2).
Please check computer settings."

"cordbg.exe !a 0x2d0"

I'm at my wits end on this, and I can't find anything helpful at the MS site.

Anyone have an idea of what's going on here, and what I can do to fix it?

Thanks in advance.

 

[Nick Hertl]

Hi John,

I can't say for sure what the actual problem is, but here are some
steps that you can take to figure it out.

First of all, the dialog that you are seeing ("Application has
generated an exception..."), this just means that your program crashed.
That can happen for any number of reasons. You probably want to find
out what that reason is so that your developer can fix the problem.

When you say that you clicked "OK", I suspect that you actually clicked
"Cancel" which will attempt to launch the registered debugger. You
probably don't have one, so the default is "cordbg.exe !a 0x%x" where
%x is the hex value of your process ID (2D0 in your case, or 720 in
decimal). This is why you get the error dialog that the debugger could
not be found. I know it's a confusing error message, but this story
will be much better in the next release (v2.0).

To determine what is wrong with you application, you have a couple
options:

1) Run it using Visual Studio as your debugger on this machine where it
is crashing.
When your program causes an unhandled exception, Visual Studio
will tell you where in the code was the problem.
2) Open a cmd.exe window and launch the program from there. Be sure to
click OK when it crashes. If this still doesn't work, you can
temporarily set the registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgJITDebugLaunchSetting"
to 1 and the dialog won't come up at all.
The result here will be that you get a StackTrace dumped to the
cmd window console.

In either case, once you know what the exception was and where in the
code it was thrown from, you should be able to have you developer fix
the code and give you a new version to try.

 

[Guest]

Thanks, Nick. I'll pass this along to our developer and have him give your
suggestion a try.