LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Fatal Internal Error: "linker.cpp" when running an exe

Subject: Fatal Internal Error: "linker.cpp" when running an exe

I'm recieving the following error when running an executable:

    Fatal Internal Error: "linker.cpp", line 1926
    LabVIEW version 7.0
   
You will lose any unsaved work. For more assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.

I've read about errors regarding linker.cpp and can't quite figure it out.  My main program is a front panel which lets the user select which action he would like to execute, when he selects an action the program calls the appropriate subVI.  When the user is done with the current action he can clear out that subVI and go back to the main front screen, in which again he can select another action.  The error occurs when an action is selected the second time.  It seems to me that LabVIEW has a problem calling the subVI a second time.  It calls it the first time ok but after it's cleared out the second call to it always bring up that error.

Thank you for any help,

~Matt

LV 7.0
Windows XP
LV 8.2.1
WinXP
0 Kudos
Message 1 of 7
(1,806 Views)

Hi,

does this link help

http://digital.ni.com/public.nsf/allkb/3D4D80041B26EF8986256F710074F5AB

regards

Ray Farmer

Regards
Ray Farmer
Message 2 of 7
(1,789 Views)
I don't think that article helps.  My main VI and all my subVIs have unique names, as they are all in the same directory.  Also, my program will load and execute, that error only arises when a subVI gets executed more than once in the main execution.

Thank you,

~Matt
LV 8.2.1
WinXP
0 Kudos
Message 3 of 7
(1,785 Views)

Hello!

Does your application contain Express VIs? If so is the case check out the following posts by my colleagues Philip Courtois and Jochen Klier:

http://forums.ni.com/ni/board/message?board.id=170&message.id=131760&requireLogin=False

http://forums.ni.com/ni/board/message?board.id=170&message.id=138244&requireLogin=False

It is a bug with LabVIEW 7.0 and was fixed in 7.1.

 

 

 

Message Edited by Jimmie A. on 07-10-2006 08:02 AM

Regards,
Jimmie Adolph
Systems Engineering Manager, National Instruments Northern European Region

Message 4 of 7
(1,784 Views)

Hello!

Does your application contain Express VIs? If so is the case check out the following posts by my colleagues Philip Courtois and Jochen Klier:

http://forums.ni.com/ni/board/message?board.id=170&message.id=131760&requireLogin=False

http://forums.ni.com/ni/board/message?board.id=170&message.id=138244&requireLogin=False

It is a bug with LabVIEW 7.0 and was fixed in 7.1.

 

 

 

Regards,
Jimmie Adolph
Systems Engineering Manager, National Instruments Northern European Region

0 Kudos
Message 5 of 7
(1,784 Views)

Hello...

Defining your Sub-VIs as "Reentrant" might solve this issue. You could do this by clicking on "File" menu, "VI Properties" and then selecting "Execution" as the category. Under the execution property page check the option for "Reentrant Execution".

Regards,

Chetan K.

Application Engineer

NI

 

Message 6 of 7
(1,765 Views)
Success!

Between taking out all the ExpressVIs I had and making the subVIs all reentrant the error as yet to show it self again.

Thank you all very much for your help.

~Matt
LV 8.2.1
WinXP
0 Kudos
Message 7 of 7
(1,758 Views)