LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 7 Build Error - File not found

Solved!
Go to solution

I am trying to build my software to another computer over the network. I am able to  access the directory I am installing to and the program is not indicating any build errors(all VI's are not broken). This error only occurs when building. Any suggestions would be great.

Thanks,

Nate 

 

 

The Build was unsuccessful

Possible Reasons:

An included VI or one of its dependencies does not exist. Open all  Startup/Exported/Dynamically called VIs, recompile them  (Ctrl-Shift Click the run arrow), and save them to update their dependencies.

 

\\PAINESTORAGE\Engineering\Test & Manufacturing Software\AutoTest Software\Current Version\AutoTest ...

 Extended Details:

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

 

Error 7 occurred at ABAPI Dist Report Read Link Info Error.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 not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.

=========================

NI-488:  Non-existent board.

-Nate
0 Kudos
Message 1 of 4
(6,642 Views)

Error 7 means it is looking for a dynamically called VI that was not included in your build. Make sure all your dynamically called VI's are included in the build.

 

-Cristian

0 Kudos
Message 2 of 4
(6,639 Views)
Is there a way to see a report of the dynamically called VI's? I inherited this software and am relatively new to LabView...
-Nate
0 Kudos
Message 3 of 4
(6,628 Views)
Solution
Accepted by N8D11
Problem was resolved- Needed to re-compile all VI's and link some missing files.
-Nate
0 Kudos
Message 4 of 4
(6,609 Views)