Error 7: File not found for executable

Question

Hello all,
I have a problem with a VI server call.  I am currently using LV 2011 on Windows 7.  Here's the problem - I have a subpanel in a larger VI into which I drop the interface of a (potentially) stand-alone VI.  The path to the called VI is good (in both the exe and in the development application).  However, I am getting an error 7 when I try to use the "Open Config Data.vi".  More specifically, I am getting the description that it can not find the VI in the library Load.vi (called by Open Config Data).  I have tried specifically adding the whole config library into the build, but this does not seem to help.  Also, the config VIs are called in the main application with no problem.  Does anybody have any thoughts? 
Thanks, Matt
Matt Richardson
Certified LabVIEW Developer
MSR Consulting, LLC
Solved!
Go to Solution.

Answer 1

OK - so maybe my description was not so great.  First - I know that the file paths are good because when they are not, the VI run dynamically in the subpanel via a VI server call will not load (there will be nothing in the subpanel).  In this case, it loads and is running (can check this through debugging).  Second, the error is occurring in both the exe and in the development system.  The absolute path (although this is not an issue - see previous comment) is not possible given that this is built into an installer and deployed on other platforms (on which the directory structure is not necessarily duped).  And finally, the VI that is loaded dynamically is already in the "always included".  I don't have a problem calling and running this VI, the error crops up when I attempt to use "Open Config Data.vi" in that is called by that VI.  This VI that is not loading (Load.vi) is located in the NI library NI_LVConfig.lvlib (located on the disk under the folder vi.lib).  I currently have a workaround for this, but it is not the best (a pop-up dialog comes up that allows the user to configure everything from the UI rather than from the config file). 
One thing that may help that I neglected to mention is that, in the development environment,  I can run the calling VI one time and I get the error.  However, in subsequent runs, I do not get the error.
Thanks for all of your responses.  I hope this further explanation helps.
Cheers, Matt
Matt Richardson
Certified LabVIEW Developer
MSR Consulting, LLC