none
Microsoft .NET Framework Unhandled exception has occurred in your application.

    Question

  • I recently downloaded and installed updates using Windows Update.  Since then I continuously get the following message popping up:

    Microsoft .NET Framework
    Unhandled exception has occurred in your application.  If you click Continue, the application will ignore this error and attempt to continue.  If you click Quit, the application will close immediately.

    Conversion from string "<br/>
    <b>Warning</b>: mysql_co" to type 'Double" is not valid.

    See the end of this message for details on invoking

    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************

    System.InvalidCastException: Conversion from string "<br />

    <b>Warning</b>: mysql_co" to type 'Double' is not valid. ---> System.FormatException: Input string was not in a correct format.

    at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)

    at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)

    --- End of inner exception stack trace ---

    at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value, NumberFormatInfo NumberFormat)

    at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(String Value)

    at CPAX20.utilities.Dec(String strCode)

    at CPAX20.Form1.tmrLink_Tick(Object sender, EventArgs e)

    at System.Windows.Forms.Timer.OnTick(EventArgs e)

    at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

     

    ************** Loaded Assemblies **************

    mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

    ----------------------------------------

    CPAX2

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Program%20Files/Common%20Files/alg.exe

    ----------------------------------------

    Microsoft.VisualBasic

    Assembly Version: 8.0.0.0

    Win32 Version: 8.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

    ----------------------------------------

    System

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

    ----------------------------------------

    System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

    ----------------------------------------

    System.Drawing

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

    ----------------------------------------

    System.Runtime.Remoting

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

    ----------------------------------------

    System.Management

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll

    ----------------------------------------

    System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

    ----------------------------------------

    System.Core

    Assembly Version: 3.5.0.0

    Win32 Version: 3.5.30729.1 built by: SP

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

    ----------------------------------------

    Microsoft.mshtml

    Assembly Version: 7.0.3300.0

    Win32 Version: 7.0.3300.0

    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll

    ----------------------------------------

    System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

    ----------------------------------------

    ************** JIT Debugging **************

    To enable just-in-time (JIT) debugging, the .config file for this

    application or computer (machine.config) must have the

    jitDebugging value set in the system.windows.forms section.

    The application must also be compiled with debugging

    enabled.

    For example:

    <configuration>

    <system.windows.forms jitDebugging="true" />

    </configuration>

    When JIT debugging is enabled, any unhandled exception

    will be sent to the JIT debugger registered on the computer

    rather than be handled by this dialog box.


    My operating system is Windows Vista Home Premium Service Pack 2 and the version of Microsoft .NET Framework installed is 3.5 Service Pack 1.
    Tuesday, October 06, 2009 10:16 AM

Answers

  • Hi Irish_Doctor,

    Thank you for your post.

    Some clarification with you:
    When did you receive JIT debugging box?

    Based on your description, it might be hard to troubleshoot this issue since there would be many causes. It might be caused by some application when you run your PC.

    For System.FormatException, it is thrown when the format of an argument does not meet the parameter specifications of the invoked method.
    For more information, please check: http://msdn.microsoft.com/en-us/library/system.formatexception.aspx

    However, to narrow down the possible cause of corrupted .NET Framework, we can try Verification tool to verify .NET Frameworks on your machine.

    Are you going to doing JIT debugging?
    If not,, you can just simply turn off this feature.
    Please see:  How to: Enable/Disable Just-In-Time Debugging

    Hope this helps. If you have any concern, please feel free to let me know.

    Best regards,
    Yichun Chen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by Irish_Doctor Thursday, October 08, 2009 4:57 AM
    • Unmarked as answer by Irish_Doctor Thursday, October 08, 2009 4:58 AM
    • Marked as answer by YiChun Chen Monday, October 12, 2009 5:47 AM
    Wednesday, October 07, 2009 10:12 AM
  • Hi Irish_Doctor,

    ************** Loaded Assemblies **************

    mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

    ----------------------------------------

    CPAX2

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Program%20Files/Common%20Files/alg.exe

    ----------------------------------------


    After doing some research, for Alg.exe, it seems to be a virus when it is located in other folders instead of C:\Windows\System32. Could you please try running Anti-virus software to have a check?
    See: http://www.neuber.com/taskmanager/process/alg.exe.html

    Hope this helps.

    Best regards,
    Yichun Chen

    (This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.)


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Edited by YiChun Chen Thursday, October 08, 2009 5:09 AM typo
    • Marked as answer by YiChun Chen Monday, October 12, 2009 5:48 AM
    Thursday, October 08, 2009 5:06 AM

All replies

  • Hi Irish_Doctor,

    Thank you for your post.

    Some clarification with you:
    When did you receive JIT debugging box?

    Based on your description, it might be hard to troubleshoot this issue since there would be many causes. It might be caused by some application when you run your PC.

    For System.FormatException, it is thrown when the format of an argument does not meet the parameter specifications of the invoked method.
    For more information, please check: http://msdn.microsoft.com/en-us/library/system.formatexception.aspx

    However, to narrow down the possible cause of corrupted .NET Framework, we can try Verification tool to verify .NET Frameworks on your machine.

    Are you going to doing JIT debugging?
    If not,, you can just simply turn off this feature.
    Please see:  How to: Enable/Disable Just-In-Time Debugging

    Hope this helps. If you have any concern, please feel free to let me know.

    Best regards,
    Yichun Chen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by Irish_Doctor Thursday, October 08, 2009 4:57 AM
    • Unmarked as answer by Irish_Doctor Thursday, October 08, 2009 4:58 AM
    • Marked as answer by YiChun Chen Monday, October 12, 2009 5:47 AM
    Wednesday, October 07, 2009 10:12 AM
  • Hello Yichun Chen,

    Thank you for your help.

    The JIT debugging box seems to appear at random.  Sometimes it appears frequently (3-4 times per hour) other times infrequently (1-2 times per day).  It appears whenever the computer is running even when  I am not actually using it.

    I guess I will just disable Just-In-Time Debugging, if you think this will solve the problem.

    Best reagrds,

    Geoff
    Thursday, October 08, 2009 5:05 AM
  • Hi Irish_Doctor,

    ************** Loaded Assemblies **************

    mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

    ----------------------------------------

    CPAX2

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Program%20Files/Common%20Files/alg.exe

    ----------------------------------------


    After doing some research, for Alg.exe, it seems to be a virus when it is located in other folders instead of C:\Windows\System32. Could you please try running Anti-virus software to have a check?
    See: http://www.neuber.com/taskmanager/process/alg.exe.html

    Hope this helps.

    Best regards,
    Yichun Chen

    (This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.)


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Edited by YiChun Chen Thursday, October 08, 2009 5:09 AM typo
    • Marked as answer by YiChun Chen Monday, October 12, 2009 5:48 AM
    Thursday, October 08, 2009 5:06 AM
  • Hi Irish_Doctor,

    Thank you for your reply. :)

    Please try the suggestion that I posted above to check whether your issue is caused by any virus.

    If you can use your machine as usual and don't want to do JIT debugging, you can just turn off this dialog box.

    Best regards,
    Yichun Chen

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    Thursday, October 08, 2009 5:13 AM
  • I have the exact same problem, and the alg.exe process is in program files\common files.  I used Microsoft Security Essentials to scan and it says no threats detected.

    Is it possibly Microsoft/MSE hasn't learned the behavior of this file/virus/trojan yet?
    ~Luke
    Tuesday, October 20, 2009 3:35 PM
  • Please post your original error. i mean your error window.
    Tuesday, March 27, 2012 4:21 PM
  • My problem is exactly the same. Error message is as following:

    Unhandled exception has occured in your application. If You click Continue, the application will ignore this error and attempt to continue. If you click Quit, the applicationwill close immediately.

    I found out this happens only in multi-processor computers while a multi-threaded application runs. I cannot catch this error while tracing the application and dlls I'm using are MS office MODI (image OCR) liberaries. Increasing memory size also did not help.

    The only way that user can avoid this error is to reboot or wait few minutes and re-run the application; I assume OS will clean up memory and make it usable for application again.

    In my case it happens almost 1 among every 10 application runs when system does not shutdown at all.

    Friday, May 25, 2012 3:33 PM