Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

vb.net - Fatal Execution Engine Error

using gpib 488 commands within my VB.Net program (e.g. ibrd, ibwrt), i get the .Net runtime crashing randomly.  it occurs frequently, but not consistently - in other words, it may crash after 100 calls, or may crash after 1000 calls to the dll, but eventually it will always crash.  this is very frustrating because we are trying to collect data and having the program crash half-way through a long (two or three hour) test causes LOTS of wasted time and effort.  i have tried many of the different types of marshalling that vb.net provides, but to no avail.  what do i need to do to keep this from crashing? 
 
below are the errors from the Windows Application Log:
 
Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1023
Date:  12/12/2006
Time:  5:02:54 PM
User:  N/A
Computer: MN01W0090
Description:
.NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506)
 
 
 
----------------
 
 
 
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date:  12/12/2006
Time:  5:03:07 PM
User:  N/A
Computer: MN01W0090
Description:
Faulting application commonserialinterface.exe, version 1.0.0.0, stamp 457f081d, faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? 0, fault address 0x000a163b.
Data:
0000: 41 00 70 00 70 00 6c 00   A.p.p.l.
0008: 69 00 63 00 61 00 74 00   i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00   i.o.n. .
0018: 46 00 61 00 69 00 6c 00   F.a.i.l.
0020: 75 00 72 00 65 00 20 00   u.r.e. .
0028: 20 00 63 00 6f 00 6d 00    .c.o.m.
0030: 6d 00 6f 00 6e 00 73 00   m.o.n.s.
0038: 65 00 72 00 69 00 61 00   e.r.i.a.
0040: 6c 00 69 00 6e 00 74 00   l.i.n.t.
0048: 65 00 72 00 66 00 61 00   e.r.f.a.
0050: 63 00 65 00 2e 00 65 00   c.e...e.
0058: 78 00 65 00 20 00 31 00   x.e. .1.
0060: 2e 00 30 00 2e 00 30 00   ..0...0.
0068: 2e 00 30 00 20 00 34 00   ..0. .4.
0070: 35 00 37 00 66 00 30 00   5.7.f.0.
0078: 38 00 31 00 64 00 20 00   8.1.d. .
0080: 69 00 6e 00 20 00 6d 00   i.n. .m.
0088: 73 00 63 00 6f 00 72 00   s.c.o.r.
0090: 77 00 6b 00 73 00 2e 00   w.k.s...
0098: 64 00 6c 00 6c 00 20 00   d.l.l. .
00a0: 32 00 2e 00 30 00 2e 00   2...0...
00a8: 35 00 30 00 37 00 32 00   5.0.7.2.
00b0: 37 00 2e 00 34 00 32 00   7...4.2.
00b8: 20 00 34 00 33 00 33 00    .4.3.3.
00c0: 33 00 65 00 37 00 65 00   3.e.7.e.
00c8: 63 00 20 00 66 00 44 00   c. .f.D.
00d0: 65 00 62 00 75 00 67 00   e.b.u.g.
00d8: 20 00 30 00 20 00 61 00    .0. .a.
00e0: 74 00 20 00 6f 00 66 00   t. .o.f.
00e8: 66 00 73 00 65 00 74 00   f.s.e.t.
00f0: 20 00 30 00 30 00 30 00    .0.0.0.
00f8: 61 00 31 00 36 00 33 00   a.1.6.3.
0100: 62 00 0d 00 0a 00         b..... 
0 Kudos
Message 1 of 2
(1,898 Views)
Hello dang,

The dll that is causing this issue (mscorwks.dll) is not a National Intstruments dll.  It looks like it is part of the Microsoft .NET framework, so Microsoft may be able to help.  If you do believe this is an issue with National Instruments, create a small application that will cause this error and attach it here, so that I can replicate the error and help you further.

Thanks!

Meghan
Applications Engineer
0 Kudos
Message 2 of 2
(1,879 Views)