Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

fatal error compatexport.cpp line 38 Labview 7.1.1

 

I have an application (EXE built on LV7.1.1) which used to run fine.

Meanwhile we sent out one our devices(CVI 1/2m Digikrom) for repairs and got it back. No installations by human.

 

Now sam EXE produces the attached error:

"Fatal Internal Error, Compatexport.cpp, line 38, LabVIEW version 7.1.1. You will loose any unsaved work..."

 

(Although this is just an EXE, LabVIEW also is present on this computer)

 

0 Kudos
Message 1 of 3
(3,763 Views)

Got lucky to get into :http://forums.ni.com/ni/board/message?board.id=170&thread.id=162835 Thanks

 

removed "Beep.VI" from the  prev. source code. Tested the source.Then recreated EXE. Worked Ok.

 

But still wondering ..given that it was running ok before equipment went out for a fix and came back (computer stayed her) what might have happenned meanwhile ?

 

Thanks.

Message 2 of 3
(3,760 Views)

Sandeepvd,

 

The fact that you got the error after your hardware underwent modifications points to the fact that the problem is somehow hardware-related (if in fact the code was unmodified). However, most problems relating  to the removal of Beep.vi and "compatexport.cpp" error relate to upgrading your code and seem to be caused by the change of interface in the Beep.vi between Labview versions. 

This problem has been submitted to our R&D department before, but was closed due to inability to reproduce this error, so unfortunately there isn't much insight into the root cause and hence it's difficult to say  what exactly was the origin of the problem in your case. It is possible that reconnecting the hardware that underwent modifications caused some changes to the system on which the EXE was running. Glad you got it up and running though. Good luck!

Misha
0 Kudos
Message 3 of 3
(3,742 Views)