none
What does this mean?

    Question

  • Problem Event Name: CLR20r3
      Problem Signature 01: myapp.exe
      Problem Signature 02: 2.1.0.4
      Problem Signature 03: 4f42dd46
      Problem Signature 04: mscorlib
      Problem Signature 05: 2.0.0.0
      Problem Signature 06: 4ca2b889
      Problem Signature 07: 12a8
      Problem Signature 08: 14
      Problem Signature 09: System.IO.FileLoadException
      OS Version: 6.1.7601.2.1.0.256.4
      Locale ID: 1033

    Thursday, February 23, 2012 3:46 PM

Answers

  • We can see problem signature description as below:

    01

    EXE file’s name (32-character limit)

    02

    EXE file’s assembly version number

    03

    EXE file’s timestamp

    04

    EXE file’s full assembly name (64-character limit)

    05

    Faulting assembly’s version

    06

    Faulting assembly’s timestamp

    07

     

    Faulting assembly’s type and method. This value is a MethodDef metadata

     token (after stripping off the 0x06 high byte) identifying the method that

     threw the exception. From this value, you can use ILDasm.exe to determine

    the offending type and method.

    08

     

     Faulting method’s IL instruction. This value is an offset within the faulting

    method of the IL instruction that threw the exception. From this value, you

    can use ILDasm.exe to determine the offending instruction.

    09

     Exception type thrown (32-character limit)


    Paul Zhou [MSFT]
    MSDN Community Support | Feedback to us

    • Marked as answer by Paul Zhou Friday, March 02, 2012 4:13 AM
    Monday, February 27, 2012 2:55 AM

All replies

  • It means, CLR failed to load a required assembly and hence theexecution failed.

    Please mark this post as answer if it solved your problem. Happy Programming!

    • Proposed as answer by Pengpeng Song Monday, April 08, 2013 1:56 AM
    Thursday, February 23, 2012 3:51 PM
  • We can see problem signature description as below:

    01

    EXE file’s name (32-character limit)

    02

    EXE file’s assembly version number

    03

    EXE file’s timestamp

    04

    EXE file’s full assembly name (64-character limit)

    05

    Faulting assembly’s version

    06

    Faulting assembly’s timestamp

    07

     

    Faulting assembly’s type and method. This value is a MethodDef metadata

     token (after stripping off the 0x06 high byte) identifying the method that

     threw the exception. From this value, you can use ILDasm.exe to determine

    the offending type and method.

    08

     

     Faulting method’s IL instruction. This value is an offset within the faulting

    method of the IL instruction that threw the exception. From this value, you

    can use ILDasm.exe to determine the offending instruction.

    09

     Exception type thrown (32-character limit)


    Paul Zhou [MSFT]
    MSDN Community Support | Feedback to us

    • Marked as answer by Paul Zhou Friday, March 02, 2012 4:13 AM
    Monday, February 27, 2012 2:55 AM