LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application Builder

I recently created an executable and when I tried to run it I got a message stating the the "Instance 1 29Saved T1 Manual Operation.vi" (the last is the VI I am making the execuatble from). At this point none of the executables that previously worked will run.
0 Kudos
Message 1 of 5
(2,755 Views)
Hello �

It is not very clear to me whether the �TI MANUAL OPERATION C.vi� window in your picture is the VI or the executable.
If it is the VI itself, then when does the �Please find the VI�� pop up window appear? When you go to Tools >> Build Application or Shared Library? Or when you try to run it?
If it is the executable, then when does the pop up window appear? Does it appear as soon as you double click on the executable file to open it?

This error is very common when you are calling a subVI dynamically and it was not specifically included in the Application Builder at the time of the build. Please follow this link.

Another good question to ask is whe
ther this is a reentrant VI or not. The pop up window does not seem to ask for the MANUAL OPERATION C.vi but for an instance of it. Are you using the same VI as a subVI? Do you have several copies of this program in different directories?

S Vences
Applications Engineer
National Instruments
0 Kudos
Message 2 of 5
(2,755 Views)
Thank you for replying SVences:)

1)I name the executable the same as the main VI. So, the screen shot is what happens after I start the executable.

2)During the Build the main VI (T1 Manual Operation C.vi) is the only file listed under the Source File tab.

3)The main VI is not being used as a sub VI. However, I do have copies of it in other directories. Our system is set up in a way that I do my program editing on a file in my local directory and when finished I build the executable to a shared directory. I have tried to copy the main VI into the shared directory but this did not solve the problem.

Another problem is that since I have tried to install the version C of this VI, none of the older versions will run. I get the same error for eve
ry executable.

I really need to get the Executable building process hammered out, since I will be creating several of these test units.

Thank you for you help!
0 Kudos
Message 3 of 5
(2,755 Views)
Hello �

Looks like you modified one of the subVIs used in the main application and your executable cannot locate the file. Are these subVIs called dynamically? If they are, you need to include them as dynamic VIs when you build your executable.

S Vences
Applications Engineer
National Instruments
0 Kudos
Message 4 of 5
(2,755 Views)
Actually I talked to my IT deepartment and they believe that it may be an issue with how they have the sharing set up between the directory I build the VI on and the directory that the Executable is located. I made a copy of the all files and placed them in one directory where the execuatable resides and that solved the problem.

Thank you very much for your help.
0 Kudos
Message 5 of 5
(2,755 Views)