CLR20r3 error in WinForms application
we're having issue 1 particular application on 1 particular server. we've got dozens of installations of application have worked years, it's 1 customer's server can't execute it. application developed in vs2005 (we can't move 2010, 1 , assembly reference doesn't work in vs2008 or 2010 solutions , we've verified assembly's vendor case). server issues brand new server 2008 r2 current on system updates.
that being said:
1) can't capture unhandled exception @ either application or appdomain level...it crashes before involved , can't attach debuggers because process never starts
2) message we're getting is:
description: stopped working problem signature: problem event name: clr20r3 problem signature 01: routedesigner.exe problem signature 02: 2.0.0.0 problem signature 03: 4dcd5df4 problem signature 04: routedesigner problem signature 05: 2.0.0.0 problem signature 06: 4dcd5df4 problem signature 07: 18 problem signature 08: e9 problem signature 09: system.invalidoperationexception os version: 6.1.7601.2.1.0.272.7 locale id: 1033
now, points out issue invalidoperationexception in routedesigner assembly (our .exe). points out in methoddef 18 (converted: 0x06000024) @ il offset e9. problem there no offset e9 in in method , method appears built-in method, not anywhere in our solution, of generated code in solution.
the methoddef 06000024 is:
method #5 (06000024) ------------------------------------------------------- methodname: create__instance__ (06000024) flags : [private] [static] [reuseslot] (00000011) rva : 0x00005dbc implflags : [il] [managed] (00000000) callcnvntn: [default] generic type arity:1 returntype: mvar!!0 1 arguments argument #1: mvar!!0 1 generic parameters (0) genericparamtoken : (2a000004) name : t flags: 00000010 owner: 06000024 1 parameters (1) paramtoken : (0800000e) name : instance flags: [none] (00000000) customattribute #1 (0c00006f) ------------------------------------------------------- customattribute type: 0a00001b customattributename: system.diagnostics.debuggerhiddenattribute :: instance void .ctor() length: 4 value : 01 00 00 00 > < ctor args: ()
this methoddef inside of following typedef:
typedef #5 (02000006) ------------------------------------------------------- typdefname: mywebservices (02000006) flags : [nestedassembly] [autolayout] [class] [sealed] [ansiclass] (00000105) extends : 01000005 [typeref] system.object enclosingclass : routedesigner.my.myproject (02000004)
the actual method in il is:
.method private static !!t create__instance__<.ctor t>(!!t 'instance') cil managed { .custom instance void [mscorlib]system.diagnostics.debuggerhiddenattribute::.ctor() = ( 01 00 00 00 ) // code size 32 (0x20) .maxstack 2 .locals init ([0] !!t create__instance__, [1] bool vb$cg$t_bool$s0) il_0000: nop il_0001: ldarg.0 il_0002: box !!t il_0007: ldnull il_0008: ceq il_000a: stloc.1 il_000b: ldloc.1 il_000c: brfalse.s il_0018 il_000e: call !!0 [mscorlib]system.activator::createinstance<!!0>() il_0013: stloc.0 il_0014: br.s il_001e il_0016: br.s il_001d il_0018: nop il_0019: ldarg.0 il_001a: stloc.0 il_001b: br.s il_001e il_001d: nop il_001e: ldloc.0 il_001f: ret } // end of method mywebservices::create__instance__
there no offset e9 in method, i'm confused on number of points:
1) application nothing webservices
2) routedesigner.my.myproject.mywebservices must generated class @ build time, doesn't exist in of solution files, generated/hidden ones
3) there's no offset e9 in method specified watson dump?
4) application works on dozens of customer systems , has done years...this system issue , it's fresh install.
we've run microsoft .net verification tool , of runtimes including 2.0 verified perfectly. in case, uninstalled runtimes , reinstalled them no avail. we've cleaned , rebuilt solution no avail. there 1 administrator account on server , using it. tried running exe run administrator option same result. we've pretty exhausted can think of, question masses is: have other ideas on how figure issue out?
my problem .dll in wrong folder. it didn't make sense because applications looks in directory i originally had in. but moved .dll 1 one applications root directory , fixed it. not sure if @ all, maybe of install setting got jacked , cause reference misplaced.
what had sort of similar. in our case, external dll reference had 7-ish year old vb6 assembly 3rd party vendor. old enough wouldn't support anyway, purchased newer version built on .net , magically worked again. no idea why of sudden broke or caused it, because application had been using exact same assembly file pretty entire 7-ish year period @ least works now.
that solution won't rest of you, unfortunately. :(
.NET Framework > Common Language Runtime Internals and Architecture
Comments
Post a Comment