LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Installer Build failed: Not A Path

I built my application without incident. When I tried to build the installer, I got a "Build Errors" dialog box containing the following text:
 
The build was unsuccessful.
Possible reasons
 
The following file(s) are not found on the system:
<Not A Path>
<Not A Path>
 
Details
 
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_PreBuild.vi >> CDK_Engine_FileExists.vi

This project was transferred from another computer. I don't think the installer has ever been built on this computer before.
 
Thanks in advance.
0 Kudos
Message 1 of 7
(3,332 Views)

RonW,

I'm going to guess that your installer includes your .exe and a couple additional installers such as Run Time Engine, NI-Visa runtime etc.  My best guess is that the last time the installer was built it used cached copies of the extra installers and is now returning to the same path to find them again.  You can check this by looking at the Additional Installers that have been selected in the Installer Properties.  If you right click on a checked installer, a path should be displayed in a box labeled "Installer Source Location".  You should be able to change the path to be your CD drive ( D:\  for instance ) and the builder should then prompt you for the disks it needs.

0 Kudos
Message 2 of 7
(3,326 Views)
The only checked additional installer is NI LabVIEW Run-Time Engine 8.5.
 
The installer source location is C:\Program Files\National Instruments\Shared\ProductCache\NI LabVIEW Rutime Engine [8.5]
 
This directory exists, and contains a directory called lv85rte, which itself contains six files.
 
Furthermore, I unchecked the 8.5 Run-Time Engine and tried to create the installer again, and it failed for the same reason.
0 Kudos
Message 3 of 7
(3,320 Views)
Have you tried creating a new build spec in your project for the installer?  Any chance that the path to the LV executable has changed from the other computer? 
0 Kudos
Message 4 of 7
(3,314 Views)
In the installer, under Source Files, I deleted the contents of the ProgramFilesFolder, then added it again. For some reason, kernel32.dll didn't show up there before. It does now, and I can build the installer.
0 Kudos
Message 5 of 7
(3,274 Views)
Glad to hear you got that figured out and thanks for posting the solution. 
0 Kudos
Message 6 of 7
(3,266 Views)
Thanks for posting this.  I had the same problem and was able to fix it by deleting the exe files in the Source Files tab of the Installer and reloading them.  Glad it was so easy to correct.
0 Kudos
Message 7 of 7
(3,197 Views)