none
Error - How can I trace it down?

    Question

  • I have an app I made in VS2005- and it uses 2.0 framework, and some sqlreader and a MSHFLEXGRID activex control.

    This application runs fine on a majority of computers, but on 3 so far it will not run. I put a try/catch around everything with a messagebox to display the exception and it never even gets that far. I have all the patches from windows update and the 2.0 framework installed on all machines.

    The box I get is "Program Name has encountered a problem and needs to close. We are sorry for the inconvenience" and a button to send this to microsoft.

    The error I get is really unhelpful but here is the event log.

    Event Type: Error
    Event Source: .NET Runtime 2.0 Error Reporting
    Event Category: None
    Event ID: 5000
    Date:  11/16/2005
    Time:  3:25:13 PM
    User:  N/A
    Computer: TTS5041
    Description:
    EventType clr20r3, P1 jtdcc.exe, P2 1.0.0.0, P3 437b9da3, P4 jtdcc, P5 1.0.0.0, P6 437b9da3, P7 e, P8 e9, P9 system.invalidoperationexception, P10 NIL.
    Data:
    0000: 63 00 6c 00 72 00 32 00   c.l.r.2.
    0008: 30 00 72 00 33 00 2c 00   0.r.3.,.
    0010: 20 00 6a 00 74 00 64 00    .j.t.d.
    0018: 63 00 63 00 2e 00 65 00   c.c...e.
    0020: 78 00 65 00 2c 00 20 00   x.e.,. .
    0028: 31 00 2e 00 30 00 2e 00   1...0...
    0030: 30 00 2e 00 30 00 2c 00   0...0.,.
    0038: 20 00 34 00 33 00 37 00    .4.3.7.
    0040: 62 00 39 00 64 00 61 00   b.9.d.a.
    0048: 33 00 2c 00 20 00 6a 00   3.,. .j.
    0050: 74 00 64 00 63 00 63 00   t.d.c.c.
    0058: 2c 00 20 00 31 00 2e 00   ,. .1...
    0060: 30 00 2e 00 30 00 2e 00   0...0...
    0068: 30 00 2c 00 20 00 34 00   0.,. .4.
    0070: 33 00 37 00 62 00 39 00   3.7.b.9.
    0078: 64 00 61 00 33 00 2c 00   d.a.3.,.
    0080: 20 00 65 00 2c 00 20 00    .e.,. .
    0088: 65 00 39 00 2c 00 20 00   e.9.,. .
    0090: 73 00 79 00 73 00 74 00   s.y.s.t.
    0098: 65 00 6d 00 2e 00 69 00   e.m...i.
    00a0: 6e 00 76 00 61 00 6c 00   n.v.a.l.
    00a8: 69 00 64 00 6f 00 70 00   i.d.o.p.
    00b0: 65 00 72 00 61 00 74 00   e.r.a.t.
    00b8: 69 00 6f 00 6e 00 65 00   i.o.n.e.
    00c0: 78 00 63 00 65 00 70 00   x.c.e.p.
    00c8: 74 00 69 00 6f 00 6e 00   t.i.o.n.
    00d0: 20 00 4e 00 49 00 4c 00    .N.I.L.
    00d8: 0d 00 0a 00               ....   

    Any ideas on how I can track this down- a try catch with a messagebox around each exception really doesn't work at all for this instance - and I have had it occur on both windows 2000 and xp machines, while at least 75% of machines have no problems with this app at all.

    Jeremy
    Wednesday, 16 November 2005 9:59 PM

Answers

  • I have the same problem, my app is running in w2003 server.
    Jeremy have you working with thread s?
    i'm using
    Control.CheckForIllegalCrossThreadCalls = false;
    at the begining ,
    maybe the warnings of the migrated app from VS2003 is the key of the problem.

    Elmer

    Friday, 18 November 2005 4:11 PM

All replies

  • I have the same problem, my app is running in w2003 server.
    Jeremy have you working with thread s?
    i'm using
    Control.CheckForIllegalCrossThreadCalls = false;
    at the begining ,
    maybe the warnings of the migrated app from VS2003 is the key of the problem.

    Elmer

    Friday, 18 November 2005 4:11 PM
  • I got this error too. Is there a way to fix it?

    thanks
    Sunday, 27 November 2005 9:22 PM
  • Same problem here for win2k3sp1, ASP.NET application. Never seen under .Net 1.1. I waisted a week on this already.
    Worst thing is it appears rarely, never happen in testing or ppe after converting project to .Net 2.0, but now it dies in production once in few hours, when thousands of people actively using the website.
    Any hint is greatly appreciated.
    I'm very disappointed, guys... sick and tired.

    EventType clr20r3, P1 aspnet_wp.exe, P2 2.0.50727.42, P3 4333aece, P4 app_code, P5 1.0.2158.27707, P6 438b9177, P7 2b, P8 93, P9 system.invalidoperationexception, P10 NIL.

    For more information, see Help and Support Center at

    Tuesday, 29 November 2005 8:49 AM
  • Hey guys.  I just switched to .NET 2.0 and got a similar situation in my Windows app.  I'll tell you what I figured out so far for my situation to see if it gives you guys ideas for your own situations.

    The problem was an exception being thrown in one of my worker threads.  .NET 1.1 just let the worker threads die quietly when the exception was thrown, which was fine by me, but .NET 2.0 gets all cranky.  I was able to catch these exceptions with the following code:

                AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(WorkerThreadHandler);

    ......

            void WorkerThreadHandler(object sender, UnhandledExceptionEventArgs args)
            {
                if (!(args.ExceptionObject is ThreadAbortException))
                {
                    Exception exc = args.ExceptionObject as Exception;
                    // Here I now have the exception for any worker thread.
                }
            }


    So I can catch these exceptions that show the message you guys were discussing above, but I haven't figured out how to get .NET 2.0 to not force my app to quit.  If anyone knows how to do this, please let me know.

    Atlas
    Friday, 9 December 2005 5:37 AM
  • I fixed the error in my program. It is because I'm using multithread. In some threads, I changed some controls property in main UI, such as text, color, ....

    I used MethodInvoker to fix this problem. So far it seems ok. The problem did not happen again.



    Friday, 9 December 2005 5:44 AM
  • To prevent your app from quitting, set the ExitApplication member of UnhandledExcetpionEventHandler to false.

     

    void WorkerThreadHandler(object sender, UnhandledExceptionEventArgs args)
            {

                  args.ExitApplication = false;
            }

    Wednesday, 4 January 2006 9:52 PM
  • Where do I put this code?

    void WorkerThreadHandler(object sender, UnhandledExceptionEventArgs args)
            {

                  args.ExitApplication = false;
            }


    Thanks!


    Monday, 9 October 2006 12:46 PM
  • i got the same error in my winform app.and the Situation was similar to yours ablove.
    Monday, 5 March 2007 6:38 AM
  • I have just fixed such an error up with my Windows Service that I needed to install on a MS Windows Server 2003 STD.

    The server had .Net Framework 2.0 showing in Add?Remove Programs. I realize it came as part of SQL Express. This is not enough to run custom .Net based applications. So after I added the regular .Net Framework 2.0 redistributable as part of my install package all worked. (In MS VS 2005 use Prerequisites from install proj properties to have the .Net 2 downloaded from the same location for instance).

    Regards,

    Arthur

    Thursday, 29 March 2007 4:42 PM
  • Error 1 'System.UnhandledExceptionEventArgs' does not contain a definition for 'ExitApplication' 
    Friday, 13 April 2007 5:27 PM
  •  

    Hi everyone,

    I am running my application 24*7. It works fine in day time but at night it get crashed. I am running it through scheduler.

    It is giving following error in application event...

     

    EventType clr20r3, P1 deduplix.exe, P2 1.0.3014.28632, P3 47f35fed, P4 system.windows.forms, P5 2.0.0.0, P6 471ebf68, P7 16c6, P8 159, P9 system.componentmodel.win32, P10 NIL.

     

    please help me and tell what can i do?

    Server OS is Windows server 2003 standard edition.

    I am using one COM dll and one OCX.

    Monday, 12 May 2008 9:32 AM
  • Hi, I experienced this error. 
    In my case I used an OCX, which is not part of the set that comes with Visual Studio...
    so I simple used it...
    * i made the setup (was o.k.)
    * installed it (was o.k.)
    * when i tried to run the application (was not o.k.)
    it burst with the "... EventType clr20r3, P1 spopclientapp.exe, P2 1.0.0.0, P3 4aba31ec, P4 spopclientapp, P5 1.0.0.0, P6 4aba31ec, P7 e, P8 e9, P9 system.invalidoperationexception, P10 NIL"  error...


    Solution:
    I registered the ocx, and the error was corrected...


    How to Register an OCX File
    If you are receiving errors about an ocx file, registering the file may solve the problem. To register an ocx file simply follow the simple steps below.


    1.Locate the file using windows explorer or My Computer. Alternatively search for the filename.

    2.Hold down the shift key and right click on the file. Then click 'Open With...' from the menu.

    3.An 'Open With' dialog box should appear. Click the button 'Other...'.

    4.Navigate to your windows\system32 directory and select the file 'RegSvr32.exe'. Do a file search for it if you have trouble locating the exact folder. On Windows 2000 it is typically located in c:\WINNT\System32. Click Open to select the file. Then click OK on the 'Open With' dialog.

    5.You should see a message indicating the file was successfully registered. If you see an error message, try restarting your computer and going through the above process again.
    (this is taken from: http://www.aliensoftware.co.uk/Files/Register_an_ocx_file.asp)


    Regards...
    Wednesday, 23 September 2009 3:05 PM