LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error (13) Building 8.2 .EXE

    I get the following error when trying to build an .exe of my LabVIEW 8.2 object based program:

Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:

Error 13 occurred at Invoke Node in ABAPI Dist read linkages.vi->ABAPI Dist Cmp Settings to Disk Hier.vi->ABAPI Get Settings From File2.vi->EBEP_Invoke_Build_Engine.vi->EBUIP_Build_Invoke.vi->EBUIP_Build_Rule_Editor.vi->EBUIP_Item_OnDoProperties.vi->EBUIP_Item_OnDoProperties.vi.ProxyCaller

Possible reason(s):

LabVIEW:  File is not a resource file.
=========================
NI-488:  Sharable board exclusively owned.

Method Name: Linker:Read Info From File

C:\Projects\LaserWireTransferLine\TransferLineApp\TransferLineApp.lvclass\TransferLineApp.ctl

Any idea what this is/ how to fix it? 
TransferLineApp is an object.  It has a cluster in for its private data, that cluster contains a single object.  That object's private data is composed of strings, numbers, and a cluster array. The cluster has again base elements, strings/ numbers/booleans, etc, i.e. nothing to do with 488.  I don't know how it can not be a resource file.
0 Kudos
Message 1 of 5
(4,120 Views)

I don't work with LVOOP, but I can tell you that the GPIB text is simply because error 13 exists for both 488 and LabVIEW and LV simply gives you both explanations.

I have experienced these kinds of problem occasionally and usually restarting LV makes the problem go away. If that doesn't help, you can try resaving the file under another name, or maybe even creating it from scratch.


___________________
Try to take over the world!
0 Kudos
Message 2 of 5
(4,116 Views)
    Thanks for your help.  That suggestion didn't work, but I did get it fixed.  I had included the transferline class as a "Dynamic and support VIs".  This wasn't neccessary.  Once I took the class out of that list, the build was successful.


0 Kudos
Message 3 of 5
(4,108 Views)
I'm not sure whether this is desired behavior or not, since I don't know exactly what you did and I don't know how LV classes are built, but I would think that even if you include a file which is already in the build, you shouldn't get this error. If you can reliably reproduce this and think it is a bug, I suggest you contact NI and tell them about it, or at the very least upload a detailed example to this thread.

___________________
Try to take over the world!
0 Kudos
Message 4 of 5
(4,105 Views)

Came across this thread researching "Error 13 occurred at Invoke Node" while using Project Explorer to build an LLB.

 

[For me] the problem seems to be related to making the Destinations\"Support Directory" the same path as "Destination Directory" AND selecting "Destination Type" = LLB.  Could be this implies copying DLLs and other dependencies into LLB(?)

 

Cheers!

 

"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
0 Kudos
Message 5 of 5
(3,684 Views)