LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application builder... error file not found

I feel like it shouldn't be this difficult to successfully build an app....

   OK,  So I have successfully built this exe numerous times.  But for the last 2weeks I can't get it to go. 
Reference:  My app calls  ~100sub-VIs and VIs from the VI.lib

The VI runs fine & with out errors, all the files exist and are seem fine, but it won't let me actually build it

  The error message says: ... An included vi or one of its dependencies does not exist ... File not found ...  Error 7  ...   NI-488: Nonexistent GPIB interface ... 

I have now re-opened, pressed Ctrl-Shft Run  and saved all of my sub-vis, started from scratch with a new project & copy of all my files,  I have checked the paths to all my sub-vis and they check out.   I have tried almost every combination of things I can think of (except extracting VI's from the VI library and individually adding them to my project).  
   I don't know what to try next,  I don't know where to look further for problems....  except maybe in trying to re-compile VIs from the VI.Lib.  But I have never had to do anything with the VI.lib on previous successfull builds.  

   Any Help???

0 Kudos
Message 1 of 5
(4,486 Views)
If you are using project libraries, check to see if there are any missing files that are part of the library. Also, there is a known issue with LabVIEW 8.5 when trying to build an app out of a VI that uses a static VI reference to reference itself.
George M
National Instruments
0 Kudos
Message 2 of 5
(4,473 Views)
Hi Catsh16,
 
Did you find any missing files in your project libraries?  Another suggestion could be that this is actually a GPIB error.  Although the error says "file not found", the GPIB Error 7 occurs when no GPIB board is present at the I/O address specified in the configuration file.  What does the rest of the error say?  The bit about a "nonexistent GPIB interface" makes me think it could be a hardware issue that is manifesting when you try to build the application.  Take a look at this link for more information on GPIB errors and how to fix them.  Thanks!
 
 
Stephen S.
National Instruments
1 Test is worth 1000 expert opinions
0 Kudos
Message 3 of 5
(4,443 Views)
I did finally manage to get it to build yesterday.   What made it work is only putting the primary Startup Vi in the 'startup VI' Box,  and leaving the dynamic VI box empty.... If it works- it works!

I occasionally get the GPIB error when running my application from the wrong directory on my computer-  I call some explicit & relative file paths, and if the files don't exist in the right location, then it sends this error while starting.  
   I don't know if there is any relation between that GPIB error and the one I was getting when trying to compile

thanks,   Kevin
0 Kudos
Message 4 of 5
(4,438 Views)
Hi Catsh16,
 
Perhaps the 488.2: Nonexhistant GPIB Interface...is actually referring to a vi named GPIB Interface....(something after the...) that was not being found because you were putting it in the startup vi category when it is stored in an llb as a part of the hierarchy of the startup vi.  This could confuse LabVIEW on where to find the vi. 
Stephen S.
National Instruments
1 Test is worth 1000 expert opinions
0 Kudos
Message 5 of 5
(4,417 Views)