ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 7 when compiling (Labview 8.2)

When I try to compile my code into an EXE I Get this Error:
 
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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 Invoke Node in ABAPI Get Library Reference.vi->ABAPI Load All Libraries And VIs.vi->ABAPI Dist Build LLB Image.vi->ABAPI Copy Files and Apply Settings.vi->EBEP_Invoke_Build_Engine.vi->EBUIP_Build_Invoke.vi->EBUIP_Build_Invoke.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.
Method Name: Library:Open
------------------------------------------------------------------------------------------------------------------------------------------------------------
 
I have tried to mass compile and that didn't work.
 
It compiled fine before.  All I did is add a read file vi to my code.  I tried taking out the new code and same results.
 
Any Ideas?
 
Thanks
Glenn Ellis
0 Kudos
Message 1 of 4
(3,135 Views)
I have no experience with the 8.x app builder, but this probably means that the builder has some file listed somewhere which it can't find. I suggest you simply try creating the build from scratch.

___________________
Try to take over the world!
0 Kudos
Message 2 of 4
(3,122 Views)
Hey glennjammin,
    There are a couple of possibilities for this error.  A few customers have reported in the discussion forums that they had success just deleting that build and creating a new one.  Also, if you have shared variables that are contained within a subVI, that can lead to this issue.  Perhaps try slowly adding parts of your VI to a new blank VI until the build breaks, that would help point us in the direction of the issue.


Brian B
Account Manager
National Instruments
0 Kudos
Message 3 of 4
(3,105 Views)

Smiley Very HappySmiley Very Happy 

 

I finally fixed it!  For some reason Labview decided it can't find a vi I was using to control an instrument even though it was there.  I Copied the vi from a different folder and replaced the vi in my diagram and it worked. 

It was very annoying that Labview didn't specify which vi it was having a problem with.  Error 7 seems to be a catch all.

I spent way too much time on this stuped error.

Thanks for all the replies though.

Glenn

Glenn Ellis
0 Kudos
Message 4 of 4
(3,084 Views)