Error 7 at Invoke Node During Different Builds in LabVIEW

Issue Details

• When trying to build a Source Distribution or from a LabVIEW project, I receive an error 7.
• When I attempt to build a Packed Project Library from the LabVIEW project results in error 7.
• When I try to build an EXE in LabVIEW, I get the following error:

Error 7 occurred at Invoke Node in AB_Engine_Write_Linker_Wrapper.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_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller

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. 

• If I do a preview before the build, I get a successful preview, but nearing the completion of the build, results in the following:

LabVIEW prevented a file name collision during the build. Duplicate file names cannot be copied to the same destination. You can rename files as part of the build process to avoid name conflicts.

The following files were moved to a unique location:

C:\Program Files\National Instruments\LabVIEW 2016\vi.lib\Utility\NIReport.llb\NI_report.lvclass
C:\Program Files\National Instruments\LabVIEW 2016\vi.lib\Utility\NIReport.llb\NI_ReportGenerationCore.lvlib
C:\Program Files\National Instruments\LabVIEW 2016\vi.lib\Utility\NIReport.llb\Excel\NI_Excel.lvclass
C:\Program Files\National Instruments\LabVIEW 2016\vi.lib\Utility\NIReport.llb\HTML\NI_HTML.lvclass
C:\Program Files\National Instruments\LabVIEW 2016\vi.lib\Utility\NIReport.llb\Standard Report\NI_Standard Report.lvclass

Solution

The LabVIEW Application Builder Module is installed with LabVIEW but needs to be activated to work with the Base and Full versions, if you have Pro version it is already activated and included in the LabVIEW activation. To address this error, ensure that your LabVIEW Application Builder Module is activated in the first place.

The above errors generally point to missing files or mismatched locations. Take the following steps to resolve missing item issues:

1. Right-click on the root of your project in the LabVIEW Project Explorer.
2. Select Find Missing Items from the shortcut menu.
3. Look at the list of missing items and try to find them on your computer.
4. If you can resolve the missing items in the window, do so. Otherwise, try removing missing items from your project and manually adding them back again.
5. If the error still occurs, try creating a new build specification and building your application or source distribution again.

Some other causes for error 7 occurring in reference to an Invoke Node during a build are as follows:

• The build process might be failing because LabVIEW does not have sufficient permissions to access or modify certain files or directories. Try running LabVIEW as an administrator.
• This error can be caused by LabVIEW finding multiple VIs with the same name or a single VI saved in multiple locations on a disk. This can be resolved by ensuring VIs are not saved in multiple locations and all VIs have unique names. Check your LabVIEW project explorer for conflicting items and fix them.
• The build can report this error in LabVIEW due to write permissions on the file directory. Check the permissions of the destination directory. When building an application on a shared network drive, there may be insufficient write permissions on the drive. Save the build in a user-accessible directory or modify the permission settings. Try building on another computer.
• This error can appear if one of the VIs is corrupted. Check and ensure that all your VIs are working properly. Follow the instructions in the article How Can I Fix my Corrupted VI in my LabVIEW Project? for more information.
• This error can be caused if you have a VI being called in a disable conditional structure. 
• This error can be caused by your executable build location exceeding Windows' maximum allowable path length during the build process. The maximum path length is 260 characters, so if your executable location is longer, error 7 can be thrown. Shorten the path length of your output directory to address this problem, either by creating a new folder in a location at a higher level or changing the names of your current file locations to shorten them.

Additional Information

This issue is commonly referred to as cross-linking. Refer to this discussion of application management best practices for more information on cross-linking and conflicts, and how to prevent and resolve them. 

Standard file names should not exceed 260 characters per the Windows Operating System, but it is recommended to keep them as short as possible.