Can't build exe LV2011 - error 7

[pkristop]

Here's the error message:

Error 7 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Save.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 have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488:  Nonexistent GPIB interface.

Not familiar with decoding these error messages. Where are the file(s) supposed to be?

[RavensFan]

Vote for this idea.  Better error descriptions for Application Builder

If we had this, maybe figuring out the problem that you have would be much easier.

[pkristop]

I gave you a kudo, now can someone give me some help?

[Zach J]

Hi pkristop,

Typically, Error 7 has to deal with a file path being incorrect for building an executable.  Can you post some screenshots of your code?  Particularly, any components of the code that open and read from files?  Can you provide an explanation of what the code is supposed to be doing?  Let me know!

[pkristop]

That would be a very tall order. There are 567 vi's in the build, not including the dependencies from vi.llb, which is where I think the error is coming from. Here are some things I've tried:

1. My vi's used to be in 3 llb's. Extracted all into one folder based on some info in another post. Didn't help.
2. I'm running LV2011, but I also still had 2010 installed. Based on another post, I renamed a bunch of files in the Resource folder under LV2010. I then mass compiled all of my vi's, and added some code to the LV2011 ini file. Didn't help.
3. Uninstalled LV2010. Didn't help.

I didn't write the original code - I inherited it, which makes debugging much more time consuming. The original author - Brian, are you out there??? - has not responded to my request for help.

The program is for used data acquisition and analysis using (primarily) a SCXI hardware platform. It reads and writes various types of files - many of them. It was originally written in a very early version of LV, and has evolved over the last 18 years.

I usually run the program under the LV environment, but I need to give a copy to a coworker. I'm trying to avoid asking for the $$ to purchase another copy of LV, but at this time it would have been well worth it, as I've been trying to build the app for 4 days.

I'm not a pro, but I'm not a novice, either. This one has kicked my butt.

[RavensFan]

Where is the project located within your drive structure? 

Is it deep down a bit, like under a documents and setting\username path?

Is it on a network drive?

If it is on a network drive, don't.  Move it to your local hard drive.  I think people have had problems with network directories in the past.

If it is kind of deep on your local drive, move it up to the root drive to something like c:\MyProj.  If you use the Microsoft preferred method of saving stuff to My Documents, then your path might be C:\Documents and Settings\UserName\My Documents\MyProj   You could be adding 40-50 characters to the filepath of your files.  If the project itself starts nesting too deeply, then you might run out of characters for the AppBuilder to work.  I think it might be limited to something like 256 characters for the full file path.

It's been awhile since I've seen threads where people were having this sort of problem, but if you search, you might find them.

Not guaranteeing anything.  But if these things apply to your situation, it would be worth changing them and trying to build your app again.

[pkristop]

Tried moving and building the exe for just the top level vi. Made sure that the "builds" folder had all permissions checked. Here's the latest error: Error copying files. Source: ..\..\Program Files (x86)\National Instruments\LabVIEW 2011\resource\lvanlys.dll Destination: C:\LV Projects\builds\ViP 2011 no llbs\VIP1\data\data0\lvanlys.dll Librarian Path Location.vi Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference: Error 1 occurred at AB_Destination.lvclass:Copy_File.vi -> AB_Source.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_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: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @. ========================= NI-488: Command requires GPIB Controller to be Controller-In-Charge.