LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to get application to build -- error copying files

Trying to build an application (which has been built with the same build spec in the past). But partway through I get this message and the build fails:

 

_____________________________________________________________

error copying files.
Source: C:\Program Files\National Instruments\LabVIEW 2017\help\_LaunchHelp.vi
Destination: C:\_Development\Neural Suite\Builds\Neural Vision Suite V4\Executables\Production Generic.exe\1abvi3w\help\_LaunchHelp.vi

Invoke Node in AB_Source_VI.lvclass:Set_VI_Path.vi->AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Set Path</b>

 

Error 7 occurred at AB_Source_VI.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi

Possible reason(s):

LabVIEW: File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
=========================
Nonexistent GPIB interface.

_______________________________________________________________

 

 

I navigated to the path of the _LaunchHelp.vi in Program Files and it is most definitely there, so I'm not sure why LabVIEW is unable to find the file. Any ideas why this is failing?

 

Thank you!

Michael

 

0 Kudos
Message 1 of 13
(4,634 Views)

Additional Information! This error only occurs when the destination for the application is on the C:\ drive. When I move the build location to my personal network drive, it builds just fine...

0 Kudos
Message 2 of 13
(4,633 Views)

Are some of the destination paths very long?

0 Kudos
Message 3 of 13
(4,620 Views)

This is the path that the file is supposed to save to when the build errors. C:\_Development\Neural Suite\Builds\Neural Vision Suite V4\Executables\Production Generic.exe\1abvi3w\help\_LaunchHelp.vi

 

There aren't many paths much longer than that. Maybe 1 layer deeper, 2 at most.

0 Kudos
Message 4 of 13
(4,617 Views)

Sometimes build errors are caused by your antivirus program grabbing onto a file, and my workaround for that is the same as yours, to build on a network drive.

Message 5 of 13
(4,608 Views)

@michael.lambert wrote:

This is the path that the file is supposed to save to when the build errors. C:\_Development\Neural Suite\Builds\Neural Vision Suite V4\Executables\Production Generic.exe\1abvi3w\help\_LaunchHelp.vi

 

There aren't many paths much longer than that. Maybe 1 layer deeper, 2 at most.


I didn't count that out.  But, is it longer than 140 characters?  If so, that is likely what you're running into.

Message 6 of 13
(4,601 Views)

I'm not sure, but I will check! I thought the char limit was greater than that, so that could be the problem

0 Kudos
Message 7 of 13
(4,574 Views)

It should be 260 characters, I think 140 is for twitter 🙂

0 Kudos
Message 8 of 13
(4,570 Views)

This path: C:\_Development\Neural Suite\Builds\Neural Vision Suite V4\Executables\Production Generic.exe\1abvi3w\help\_LaunchHelp.vi

Is 121 Characters

0 Kudos
Message 9 of 13
(4,568 Views)

@Gregory wrote:

It should be 260 characters, I think 140 is for twitter 🙂


There are too many character requirements these days =/

0 Kudos
Message 10 of 13
(4,561 Views)