01-19-2009 07:38 PM
Hi justAris,
Have you tried the steps listed in Knowledge Base 4PAIRE3H Not A Path Error Received When Building an Installer found at http://digital.ni.com/public.nsf/allkb/314E972C1717AE3E862574C20002B36A?OpenDocument? Let me know if this does or does not help.
10-09-2009 06:00 AM
I am migrating an application from LV 6.1 to LV 8.5.1. The first step is to verify that a DAQ card replacement (E series to M series) will work correctly. For this I updated a copy of the source VI's to interface to the new DAQmx card and built a small test VI.
I set the test VI's property, "Application Top-Level" and configured a Build Specification (executable) for the test VI. The goal is to deploy the test executable onto the target and verify that DAQ works, then port the rest of the application.
However, AppBuilder is unable to build a small test VI.
I receive error code 7, File not found for the following file:
C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\libraryn.bin
Which does exist at that location.
What gives?
10-09-2009 06:39 AM
Application Builder Issue?
To start from scratch, I create a simple, "hello-world" dialog VI and build it into an executable. (Top-level app window). And it worked!
Then, I create a new build spec for my EXE from my simple VI, with no other AppBuilder settings. And it worked!?!
Next, I opened the LVProj in notepad to copy out those XML properties. Comparing the properties in MS Excel revealed that the main difference was in the BAD build specification, I had checked the versioning category, "Auto Increment" property.
The difference between my BAD BuildSpec and my GOOD BuildSpec was the AutoIncrement (version number) property.
I could not clear that property in the BAD specification to get it to compile.
Hmm, is something missing from my LabVIEW installation?
10-12-2009 11:29 AM
10-19-2009 04:46 PM
I had a similar problem, same errors when I was trying to create a new executable from an older project (LabVIEW 8.0) in LabVIEW 8.6. To correct this, I deleted the executable and build files. Created a new installer and new build, and it all work fine.