Fatal Internal Error: "Compatexport.cpp", line 37

[VictorY]

I am trying to migrate a large application from LabVIEW 5 to LabVIEW 7.0.  I am using NI-DAQ 6.9.3f on a WinXP platform. When I run the application I get the message:

Fatal Internal Error: "compatexport.cpp", line 37

LabVIEW then closes.  Upon restarting LabVIEW, it generates the following error log file:

####
#Date: Jan 23, 2006 12:43:46 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 7.0
#AppKind: FDS

D:\lvworm\src\lvsource\compatexport.cpp(37) : DAbort: Called a routine not in the compatibility LVRT table
$Id: //labview/branches/Wormhole/dev/lvsource/compatexport.cpp#11 $
0x004BDC0B - LabVIEW GetCIntVIServerFuncs + F5CB
0x096FE082 - <unknown> <unknown> + 0
0x096F7DA5 - <unknown> <unknown> + 0
0x098BB56C - <unknown> <unknown> + 0
0x004D7F70 - LabVIEW ThMutexAcquire + 1A330
0x8B535CEC - <unknown> <unknown> + 0

Can someone tell me what this error message is related to / refers to?  Do someone have a suggestion on where to look in the code for the source of the error?

Victor

[Darren]

Have you tried mass compiling your application in 7.0 before running it?  That's the first thing I would try...

-D

[VictorY]

Thanks for the suggestion.  I did do a mass compile and I also upgraded to NI-DAQ 7.1, but the error still occurs.

[Darren]

Hi Victor,

From what I can tell, that error will occur when there is a bad call to either a CIN or a DLL in your code.  For example, if you have any code that is making internal calls to LabVIEW with a Call Library Node, if the internal LabVIEW call was changed from one LabVIEW version to another, this compatexport.cpp failure can occur.

I think you should use breakpoints and execution highlighting on your application to determine where specifically (i.e. which subVI, CIN, or DLL call) your application is crashing.  Then remove that part of the code and see if the crash goes away.

Keep me posted, and good luck,

-D

[VictorY]

Hi Darren,

I tracked down the problem to the "Beep.vi" file in my application.   This file did not update during the mass compile.  I simply deleted the Beep.vi file in my application folder; LabVIEW 7 then loads the Beep.vi from vi.lib.  My application now runs without crashing LabVIEW.

The application still requires other changes to accomodate the migration from LV5 to 7, but (hopefully) they should be easier to sort out now that LabVIEW doesn't crash.

Thanks for your help.

Victor

[Darren]

I'm glad you solved the problem, Victor.  Beep.vi is one of the many examples I found looking through old bug reports of VIs that had a change of interface between LabVIEW versions that might cause a problem.  This is why you should never save your own copies of vi.lib VIs and port them around with your application unless you have actually modified those VIs.

Good luck,

-D

[TeaAndBiscuits]

This helped me also.

I had problem of error 38 on compatexport.

Got lucky.....Removed "Beep". Everything worked then.

Thanks