none
.Net 2.0 runtime error reporting

    Question

  • Hi,

    Following event log error happens when executing asp.net 3.5  dll,which is called by third party application.

    i have tried  to debug the dll and found out exact spot, which happens to be when calling another dll from this one. i don't have

    source code for that. Is there any way i can trace out this.

    Another important thing to note is there seems to be no error when using .Net framework 2.0. It all happen when it iw upgraded to 3.5.

     

    Any help on this appreciated.

     

     

    Event Type: Error
    Event Source: .NET Runtime 2.0 Error Reporting
    Event Category: None
    Event ID: 5000
    Date:  14/04/2010
    Time:  4:56:00 PM
    User:  N/A
    Computer: APVTHAU86102
    Description:
    EventType clr20r3, P1 dllhost.exe, P2 5.2.3790.3959, P3 45d6967a, P4 mhonyxintegration, P5 1.0.0.0, P6 4bc442a2, P7 133, P8 270, P9 exception, 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 64 00 6c 00 6c 00    .d.l.l.
    0018: 68 00 6f 00 73 00 74 00   h.o.s.t.
    0020: 2e 00 65 00 78 00 65 00   ..e.x.e.
    0028: 2c 00 20 00 35 00 2e 00   ,. .5...
    0030: 32 00 2e 00 33 00 37 00   2...3.7.
    0038: 39 00 30 00 2e 00 33 00   9.0...3.
    0040: 39 00 35 00 39 00 2c 00   9.5.9.,.
    0048: 20 00 34 00 35 00 64 00    .4.5.d.
    0050: 36 00 39 00 36 00 37 00   6.9.6.7.
    0058: 61 00 2c 00 20 00 6d 00   a.,. .m.
    0060: 68 00 6f 00 6e 00 79 00   h.o.n.y.
    0068: 78 00 69 00 6e 00 74 00   x.i.n.t.
    0070: 65 00 67 00 72 00 61 00   e.g.r.a.
    0078: 74 00 69 00 6f 00 6e 00   t.i.o.n.
    0080: 2c 00 20 00 31 00 2e 00   ,. .1...
    0088: 30 00 2e 00 30 00 2e 00   0...0...
    0090: 30 00 2c 00 20 00 34 00   0.,. .4.
    0098: 62 00 63 00 34 00 34 00   b.c.4.4.
    00a0: 32 00 61 00 32 00 2c 00   2.a.2.,.
    00a8: 20 00 31 00 33 00 33 00    .1.3.3.
    00b0: 2c 00 20 00 32 00 37 00   ,. .2.7.
    00b8: 30 00 2c 00 20 00 65 00   0.,. .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               ....   

    Wednesday, April 14, 2010 9:24 AM

Answers

  • EventType clr20r3, P1 dllhost.exe, P2 5.2.3790.3959, P3 45d6967a, P4 mhonyxintegration, P5 1.0.0.0, P6 4bc442a2, P7 133, P8 270, P9 exception, P10 NIL.

     

    Here is the explanation for the above exception (data from the event viewer) in case if you are unable recreate the problem to debug. CLR from v 2.0 started integrating in to watson buckets and anytime there is an unhandled exception watson buckets gets populated. FYI P1- P10 are watson buckets

    Bucket P4 describes the faulting module which is" mhonyxintegration", bucket P9 displays the type of exception that went unhandled, and bucket P8 represents the IL offset at which the exception was originally thrown.

    Here is an msdn article which explains in detail of these watson buckets . With the above information you can essentially get call-stack and the type of exception without having to debug it.

     

     


    Thanks Naveen http://naveensrinivasan.com
    • Proposed as answer by NaveenS Tuesday, April 20, 2010 4:13 PM
    • Marked as answer by eryang Wednesday, April 21, 2010 2:07 AM
    Tuesday, April 20, 2010 4:13 PM
  • If you debugged it, then you know which code threw the exception, right? Check out its inner exceptions. If the original exception is comming from third party component, then you will have to contact their support.

    -Karel

    • Marked as answer by eryang Thursday, May 06, 2010 6:31 AM
    Wednesday, April 14, 2010 7:01 PM
    Moderator

All replies

  • If you debugged it, then you know which code threw the exception, right? Check out its inner exceptions. If the original exception is comming from third party component, then you will have to contact their support.

    -Karel

    • Marked as answer by eryang Thursday, May 06, 2010 6:31 AM
    Wednesday, April 14, 2010 7:01 PM
    Moderator
  • Hi,

    If you are runing an ASP.NET application, I think, this website is really helpful for you to debug your program and generate the dump file. Or just debug you program through the instruction of the website step by step.

    Hope this helpful to you!


    Sincerely,
    Eric
    MSDN Subscriber Support in Forum
    If you have any feedback of our support, please contact msdnmg@microsoft.com.
    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.
    Tuesday, April 20, 2010 2:31 AM
  • EventType clr20r3, P1 dllhost.exe, P2 5.2.3790.3959, P3 45d6967a, P4 mhonyxintegration, P5 1.0.0.0, P6 4bc442a2, P7 133, P8 270, P9 exception, P10 NIL.

     

    Here is the explanation for the above exception (data from the event viewer) in case if you are unable recreate the problem to debug. CLR from v 2.0 started integrating in to watson buckets and anytime there is an unhandled exception watson buckets gets populated. FYI P1- P10 are watson buckets

    Bucket P4 describes the faulting module which is" mhonyxintegration", bucket P9 displays the type of exception that went unhandled, and bucket P8 represents the IL offset at which the exception was originally thrown.

    Here is an msdn article which explains in detail of these watson buckets . With the above information you can essentially get call-stack and the type of exception without having to debug it.

     

     


    Thanks Naveen http://naveensrinivasan.com
    • Proposed as answer by NaveenS Tuesday, April 20, 2010 4:13 PM
    • Marked as answer by eryang Wednesday, April 21, 2010 2:07 AM
    Tuesday, April 20, 2010 4:13 PM
  • Hi AnandKrishnan,

    I marked the answer. If you have any further question, please feel free to unmarked it and we will discuss this issue again.


    Sincerely,
    Eric
    MSDN Subscriber Support in Forum
    If you have any feedback of our support, please contact msdnmg@microsoft.com.
    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.
    Wednesday, April 21, 2010 2:08 AM