Grrrrr @ VS Errors - Plz help if u can (clr20r3) | The Coffeehouse

phreaks

Today, all of a sudden out of nowhere, my service started dying, with nothing but this little gem in the event log.

I went in and placed General Catch(Exception ex) statements anywhere it could trigger an exception, and it still isn't being caught.

Does anyone know what this even means? It's 2:13 in the AM, I need to get up in less than 3.5 hours and I've been trying to resolve this issue for almost 5 hours now.

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date:  8/9/2007
Time:  1:57:43 AM
User:  N/A
Computer: XDEV
Description:
EventType clr20r3, P1 matlabprocessingservice.exe, P2 1.0.0.0, P3 46baa5a0, P4 matlabprocessingservice, P5 1.0.0.0, P6 46baa5a0, P7 10, P8 2c, P9 pszqoadhx1u5zahbhohghldgiy4qixhx, P10 NIL.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
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 6d 00 61 00 74 00    .m.a.t.
0018: 6c 00 61 00 62 00 70 00   l.a.b.p.
0020: 72 00 6f 00 63 00 65 00   r.o.c.e.
0028: 73 00 73 00 69 00 6e 00   s.s.i.n.
0030: 67 00 73 00 65 00 72 00   g.s.e.r.
0038: 76 00 69 00 63 00 65 00   v.i.c.e.
0040: 2e 00 65 00 78 00 65 00   ..e.x.e.
0048: 2c 00 20 00 31 00 2e 00   ,. .1...
0050: 30 00 2e 00 30 00 2e 00   0...0...
0058: 30 00 2c 00 20 00 34 00   0.,. .4.
0060: 36 00 62 00 61 00 61 00   6.b.a.a.
0068: 35 00 61 00 30 00 2c 00   5.a.0.,.
0070: 20 00 6d 00 61 00 74 00    .m.a.t.
0078: 6c 00 61 00 62 00 70 00   l.a.b.p.
0080: 72 00 6f 00 63 00 65 00   r.o.c.e.
0088: 73 00 73 00 69 00 6e 00   s.s.i.n.
0090: 67 00 73 00 65 00 72 00   g.s.e.r.
0098: 76 00 69 00 63 00 65 00   v.i.c.e.
00a0: 2c 00 20 00 31 00 2e 00   ,. .1...
00a8: 30 00 2e 00 30 00 2e 00   0...0...
00b0: 30 00 2c 00 20 00 34 00   0.,. .4.
00b8: 36 00 62 00 61 00 61 00   6.b.a.a.
00c0: 35 00 61 00 30 00 2c 00   5.a.0.,.
00c8: 20 00 31 00 30 00 2c 00    .1.0.,.
00d0: 20 00 32 00 63 00 2c 00    .2.c.,.
00d8: 20 00 70 00 73 00 7a 00    .p.s.z.
00e0: 71 00 6f 00 61 00 64 00   q.o.a.d.
00e8: 68 00 78 00 31 00 75 00   h.x.1.u.
00f0: 35 00 7a 00 61 00 68 00   5.z.a.h.
00f8: 62 00 68 00 6f 00 68 00   b.h.o.h.
0100: 67 00 68 00 6c 00 64 00   g.h.l.d.
0108: 67 00 69 00 79 00 34 00   g.i.y.4.
0110: 71 00 69 00 78 00 68 00   q.i.x.h.
0118: 78 00 20 00 4e 00 49 00   x. .N.I.
0120: 4c 00 0d 00 0a 00         L.....

CannotResolveSymbol
{insert caption here}

Did you click the link? It looks generic and pointless, but it's not (if clicked from within Event Viewer)... it sometimes provides more information about what's actually happening.

RichardRudek
So what do you expect for nothin'... :P

phreaks wrote:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date:  8/9/2007
Time:  1:57:43 AM
User:  N/A
Computer: XDEV
Description:
EventType clr20r3, P1 matlabprocessingservice.exe, P2 1.0.0.0, P3 46baa5a0, P4 matlabprocessingservice, P5 1.0.0.0, P6 46baa5a0, P7 10, P8 2c, P9 pszqoadhx1u5zahbhohghldgiy4qixhx, P10 NIL.

Not that much help, given that you say you've added catches for ALL (?!) of the places that can produce an exception. But this is from EventID.net:

This problem occurs because the default policy for unhandled exceptions has changed in the .NET Framework 2.0. By default, the policy for unhandled exceptions is to end the worker process. In the Microsoft .NET Framework 1.1 and in the Microsoft .NET Framework 1.0, unhandled exceptions on managed threads were ignored.

So, you probably need to look into how to add your own, 'global' exception handler, rather than trying to find all of the places that can trigger and exception and adding a catch.

Also, have you tried attaching your debugger (Visual Studio) to the process (service) ?

phreaks

RichardRudek wrote:

phreaks wrote:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date:  8/9/2007
Time:  1:57:43 AM
User:  N/A
Computer: XDEV
Description:
EventType clr20r3, P1 matlabprocessingservice.exe, P2 1.0.0.0, P3 46baa5a0, P4 matlabprocessingservice, P5 1.0.0.0, P6 46baa5a0, P7 10, P8 2c, P9 pszqoadhx1u5zahbhohghldgiy4qixhx, P10 NIL.

Not that much help, given that you say you've added catches for ALL (?!) of the places that can produce an exception. But this is from EventID.net:

This problem occurs because the default policy for unhandled exceptions has changed in the .NET Framework 2.0. By default, the policy for unhandled exceptions is to end the worker process. In the Microsoft .NET Framework 1.1 and in the Microsoft .NET Framework 1.0, unhandled exceptions on managed threads were ignored.

So, you probably need to look into how to add your own, 'global' exception handler, rather than trying to find all of the places that can trigger and exception and adding a catch.
Also, have you tried attaching your debugger (Visual Studio) to the process (service) ?

Bah. No, I haven't tried it. I don't think it's possible.

This is only happening on 1 machine and that machine doesn't have VS installed.

I know roughly where it is breaking, just not the specific line or reason, so yes, there are 3 catches that should catch the darn error, but it's not.

phreaks

RichardRudek wrote:

phreaks wrote:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date:  8/9/2007
Time:  1:57:43 AM
User:  N/A
Computer: XDEV
Description:
EventType clr20r3, P1 matlabprocessingservice.exe, P2 1.0.0.0, P3 46baa5a0, P4 matlabprocessingservice, P5 1.0.0.0, P6 46baa5a0, P7 10, P8 2c, P9 pszqoadhx1u5zahbhohghldgiy4qixhx, P10 NIL.

Not that much help, given that you say you've added catches for ALL (?!) of the places that can produce an exception. But this is from EventID.net:

This problem occurs because the default policy for unhandled exceptions has changed in the .NET Framework 2.0. By default, the policy for unhandled exceptions is to end the worker process. In the Microsoft .NET Framework 1.1 and in the Microsoft .NET Framework 1.0, unhandled exceptions on managed threads were ignored.

So, you probably need to look into how to add your own, 'global' exception handler, rather than trying to find all of the places that can trigger and exception and adding a catch.
Also, have you tried attaching your debugger (Visual Studio) to the process (service) ?

I'm almost positive that it's an Interop assembly that's failing, which is run off on its own thread.

There was a versioning issue originally, the Matlab version i generated the interop assembly against was 2006b, but this server had version 2006a installed.

Upgraded Matlab on the host server to 2006b and it ran fine for a few hours, then I deployed a new version of my app, with very minor changes and it blows up with this cryptic error.

Again, I almost 100% positive the interop assembly is generating the error.

Is there a way I can generate the interop assembly from the tlb file on the host machine, like via a command line?

gemanet

After many hours working with this error in a application in VB NET, i find the solution trapping the error in VB NET

using this:

Sub UnhandledExceptionEventRaised(ByVal sender As Object, ByVal e As UnhandledExceptionEventArgs)
        If e.IsTerminating Then
            Dim o As Object = e.ExceptionObject
            MessageBox.Show("Error: " & o.ToString)
            Debug.WriteLine(o.ToString) ' use EventLog instead
        End If
    End Sub

    Public Sub New()
        MyBase.New()
        AddHandler AppDomain.CurrentDomain.UnhandledException, AddressOf UnhandledExceptionEventRaised

Application.EnableVisualStyles()
Application.DoEvents()

        'This call is required by the Windows Form Designer.
        InitializeComponent()
    End Sub

In my application the problem occurs when the thread is closing because a tcpip connection are closing, and this interrupt an sql query execution. This, generate a exception similar to describe here. I think that all the people that have the same problem, search all the procedures without try and catch, because this problem occurs when the trapping errors system in your application is not good implemented.