Issues with building a VI into a .exe in Labview 2016

[Chickeneatman]

Hello,

I am trying to build a VI I have created into and executable. Unfortunately my computer seems to be having issues with this. I have sent my VI to a coworker and he was able to build it into an executable without any issues. I have checked my licenses and they are all up-to-date. I have tried to do this with all windows closed, except the build window and project window, I have even restarted my PC, and still no luck. I keep getting these errors:

Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_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_Create_Build_Application.vi->EBUIP_Global_OnCommand.vi->EBUIP_Global_OnCommand.vi.ProxyCaller

Possible reason(s):

LabVIEW: File permission error. You do not have the correct permissions for the file.

C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2016\errors\VI-Analyzer-errors.txt

My file is not set to Read-Only and I have full Admin permissions. Any ideas?

Thank you.

[Bob_Schor]

Where are you trying to save the Build?  You should not use Program Files or Program Files (x86) as output directories.

Bob Schor

[Chickeneatman]

I have tried a few different locations. One time my desktop, another was my project folder on my C drive. I never tried to output to my program files.

[Chickeneatman]

I still have not found a solution. Any help would be greatly appreciated. Maybe a reinstall is the next step. My coworkers have no trouble at all building my vi into an executable.

[Bob_Schor]

This is a "long shot", but is it possible you might have a License issue (something didn't get activated)?  Go to the Start Menu, National Instruments, and look in the folder for NI License Manager.  Run it and be sure everything says "Activated".  Note that mine shows "Application Builder" as a separate "thing to activate".License Manager

Bob Schor

[natasftw]

Try this.

Create a new project.

Add a blank VI, save it.

Create a new executable only changing the build specs to choose your blank VI as the startup VI.

Hit OK

Save the project

Right-click and try to build this executable.

Does it build successfully?  (This shows you have the capability TO build an executable.)

Essentially, the goal of this step is it's trivial effort and it tells you if the build is an issue with your specific project or if it's with building in general.

If that builds, does your project build on your colleague's PCs?  You said they can build things but didn't specify it was this same project.

[altenbach]

Some other possibilities:

- Some overzealous antivirus software.

- Disk errors/corruption.

- corrupted LabVIEW install.

- malware

- ...

[Chickeneatman]

Here is my license manager.

[Chickeneatman]

I attempted to build a blank vi and received the same errors.

My colleagues can successfully build my project. I sent it to them to build for me. The issue is definitely localized to my PC.

[Frozen]

Now that you have isolated the problem ie your computer and your setup, next logical step would be to re-install LabVIEW to see if that fixes the problem.

Let us know how it goes.