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


  • Our custom got an error when startup our .NET windows form application.

    XXXXX.exe - Common Language Runtime Debugging Services
    Application has generated an exception that could not be handled
    Process id=0x654(1620), Thread id = 0x5b0 (1456)
    Click OK to terminate the application
    Click CANCEL to debug the application

    If they click on "CANCEL" then following error message appears:

    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 the computer settings
    cordbg.exe !a0x654
    Click on Retry to have the process wait while attaching a debugger
    Click on Cancel to abort the JIT debug request

    We can not duplicate this problem in our development environment and test environment. So, we ask them to uninstall application, .NET Framework 1.1 and resinstall .NET Framework 1.1 and application. They still got same error. We further ask them to install .NET Framework SDK 1.1. They got some detail error message.

    [thread 0x840] Thread created.
    Unable to determine existence of prolog, if any
    [thread 0x188] Thread created.
    [thread 0xba8] Thread created.
    [thread 0x840] Unhandled exception generated: <0x00c0344c> <System.IO.FileNotFoundException>
     _message=<0x00c04cc8> "The specified module could not be found."
     _stackTrace=<0x00c04d2c> array with dims=[156]

    Thread 0x840 R 0x00000000: <unknown>

    Looks like the problem is casued by missing component. But we don't know which component missing and how to find it. Is there anybody can give us some clue what we need to check next and what tool we can use to detect missing component.



    13 iulie 2006 16:53


Toate mesajele

  • The error code hints that LoadLibrary failed.  That's probably because an assembly is missing or a P/Invoke call referenced a DLL that is not available.  The stack trace might be just a little useful; "array with dims", does that mean anything to you?

    13 iulie 2006 19:12
  • Thank you for your response!!

    I don't know what "array with dims" means. You are proably right, there are something not available, but becasue it is happen on client's laptop, we are not able to try. So, is there a way can let client do something and give us more information or any tool available to gather more information.

    14 iulie 2006 14:31
  • Try profiling the app with Depency Walker.  If a DLL is missing, it should be quite obvious from the trace.

    14 iulie 2006 17:21
  • I tried Dependency Walker in our development environment, looks like it's useless for .NE T Window Form application, the result I got is like bellow,


    I know we used some other DLL like Mirosoft Office Object Library, but MSCOREE.DLL (.NET Runtime Engine) covered them. Any other idea? Thanks!!!!

    14 iulie 2006 18:23
  • Hit F7 to start profiling the app.  You'll see notifications in the bottom panel, pay attention to the LoadLibrary calls.

    14 iulie 2006 18:40
  • Cool, that's exactly what I am looking for. I know this tool for a while, but didn't speed any time to study how to use it. Thanks a lot!!!!!
    14 iulie 2006 19:28
  • Hi.  I have the same error...was this error ever resolved?
    29 august 2006 13:45
  • You can use Depency Walker to narrow down the problem.
    30 august 2006 02:18
  • Any final solution about it?

    7 ianuarie 2015 15:13