Error 15 at "Run VI" Invoke Node When Building a LabVIEW Executable

I am trying to run a vi by using the "run VI" method of the invoke node. The source code works perfect. However, I cannot run the vi when I use the executable version. Specifically, I get the Error code 15 at the "error out" output of the invoke node while using the executable version. Why is this occuring?
Thanks

Hello ameng,
This behavior is typically the result of trying to call VI that has had its front panel removed. The KnowledgeBase linked below has more information on this issue.
Error 1 or 15 Opening Dynamic VI from LabVIEW Application
Please let me know if you have any other questions about this issue.
Regards,
Matt F
Keep up to date on the latest PXI news at twitter.com/pxi

Similar Messages

LabVIEW Application throws Error in Run VI Invoke node

Hi All,
We are facing an issue with an application developed from LabVIEW 2010SP1.
Application Description:
In our application, there is a top level VI which tries to run VIs dynamically[using Run VI invoke node] from a particular folder. This folder is like a plugin - not part of Exe. This implies when the top level VI is launched, the plugin VIs under particular folder will not be in memory. When we try to run a VI dynamically from the top level VI, the VI execution works perfectly in LabVIEW development mode.
Problem Faced:
When we created an EXE, it worked well in my PC [LabVIEW is installed]. We created an installer and tested in few other PCs.
[Non LabVIEW PCs – Win XP and 7]. In few PCs it throws the following error, when the plugin VI is run dynamically.
Error 1003 occurred at Invoke Node
Possible reason(s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.
Method Name: Run VI
We tried the following possible ways to find the reason for the issue:
1. Installed LabVIEW - Issue got fixed.
2. Installed .net 2.0 without installing LabVIEW - Issue got fixed.
3. But in one of the Windows 7 [Non - LabVIEW PC] in which .net was already installed, we faced the same error.
Only after installing LabVIEW the error got fixed.
4. When .net 2.0 is uninstalled the EXE itself is broken.
We are not sure what is the Exact reason fo the issue. Anyone faced these kind of issues? Please share the solution. Thanks in advance.
Note:
1. The VIs which are dynamically called is a plugin and not a part of EXE.
2. These plugin VIs have no dependencies from vi library and is completely isolated.
3. We are not using any .net related objects in any of the VIs.
4. The plugin VIs use Call library function node in which a C DLL developed from Microsoft Visual Studio 2010 is used.
Thanks,
Meena
Solved!
Go to Solution.

Error 1003: This clearly indicates that the 'Dynamic VI' is broken and now you should check for the various reasons, why the 'Dynamic VI' is broken.
Also path of 'Dynamic VI' is not a problem.
One thing that you may try is:
-> First open just the 'Dynamic VI' in a new LabVIEW project and check for the 'Dependencies'.
-> Now if any of the item in 'Dependencies', other than what is listed in vi.lib (lets call it 'Dependency.VI'), is also a part of your 'Main Exe', then its a problem. Because when you will execute the 'Main Exe', say in a new computer other than your development computer, it will load all its dependencies including 'Dependency.VI' (and the path will be within the 'Main Exe', but when it will try to (dynamically) load the 'Dynamic VI', this VI will also try to load the same 'Dependency.VI' but from different path and that will cause a conflict. I had experienced this.
-> If thats the issue, you may want to rename (add suffix/prefix) to all dependencies of your 'Dynamic VI' which is common to the 'Main Exe'.
Hope this solves your issue.
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.

Does "Run VI" invoke node work on strict references to REENTRANT VIs?

I am using LV 6.02 on Windows 2000.
I am trying to use the "Run VI" invoke node method with a reference to a Reentrant VI, with no success. (It works when VI is not reentrant. Perhaps there is a reason this cannot work. But if not, I wonder if there is a workaround, or if LabVIEW 6.1 has a fix?
Hopefully the picture of the block diagram I included is sufficient...but I also included the actual code just in case.
Thanks!
Steve
Attachments:
block_diagram.jpg ‏66 KB
Parent_VI_Example.vi ‏43 KB
Prototype_subVI_shell_for_Simplex_Fit.vi ‏40 KB

Hi, Labviewguru,
Thanks for taking the time to look at my admittedly messy (flawed) block diagram. I will try to state my ultimate goal:
You may be familiar with Levinberg-Marquardt nonlinear curve fit in Labview, which is about 5 VIs in a LLB file. In order to change the type of curve fitting, one has to either modify a formula node in the lowest subVI (Target Func and Deriv), or place a different subVI in there. That's fine until I want to have many different sorts of algorithms.
What I was thinking of doing is instead passing Target Func and Deriv a reference to the VI which would perform the calculations. This would allow me to use the same fitting code to fit different types of data with substantially different methods--without modifyin
g the low-level fitting code at all.
I'm not sure this is going to make any sense to you, but thanks again for your help.
In regards to your answer above, let me clarify somewhat. I had the call by reference node in there to prove that the reference to the VI was "good" and worked fine...this same reference was passed to the invoke node, which didn't have any apparent effect.
Also, I don't think the path to the VI I am opening the reference to is redundant. It is required to tell the "Open VI reference" which VI to load.
I agree that using references to pass values around is not generally a good idea: I was using that method for my supposed versatility in the future.
Thanks,
Steve

Multiple VI instance will not RUN using invoke node

Hi,
I need to have multiple instances of the same VI running.
I've created a template of the VI i wan't to call multiple times.
The VI is called via Open VI reference with a reference to the VI template.
Parameters to the instance is passed via set control value.
When opened and parameters has been passed, I use a invoke node to run the VI.
An error occur.
"Error 1000 occurred at Invoke Node in Template_Call plot window.vi
Possible reason(s):
LabVIEW: The VI is not in a state compatible with this operation.
Method Name: Run VI
VI Path: NULL"
Note ! The VIs should stay open after the call running independently of each other and the caller should not be waiting until the VI stops.
Any ideas what I am doing wrong
Regards Kahr
Certified LabVIEW Architect
CIM A/S
Solved!
Go to Solution.
Attachments:
Call_Plot Window.png ‏31 KB
Template_Plot window.png ‏23 KB

As simple as that Kumar !
Thank You all
Regards Kahr
Certified LabVIEW Architect
CIM A/S

Run VI Invoke Node: VI works, EXE doesn't?

This is LV2009 with no patches or updates. I am calling buffer.vi by static reference with an invoke node set to Run VI. I don't have an incredibly good reason for doing this, but just don't want that code on the block diagram. I hate to put alot of effort into this since I can just drop the code on the main diagram and I'm sure it will work, but I don't understand why it gives me the error 1000: VI not in a state compatible with this operation?
In the EXE, when I check the execution state of the buffer.vi before I tell it to run, it comes up bad. Same code in the VI, comes up idle. I also tried replacing the static VI reference with an open VI reference using the name of the buffer and received the same error. I have the buffer VI included in the build under always included.
Solved!
Go to Solution.

"You did not compile the vi to be in the EXE, did you?"
I'm not sure what you mean. I have included buffer.vi and all of its sub VIs in the build as Always Included. I am investigating creating a source distribution. Never done that before. I will let you know if it works.
I attached snippets of the caller and buffer.vi itself. I was playing around with the caller, trying to abort if running and such...
Edit: Sorry if its confusing, what I'm calling buffer.vi is actually Waveform FIFO AE.vi
Message Edited by deskpilot on 04-08-2010 09:04 AM
Attachments:
Remote Call.png ‏34 KB
Buffer.png ‏42 KB

Sun.applet.appletPanel.run() is invoked twice when applet is loaded.

When I am loading my applet in the browser, sun.applet.appletPanel.run() function is invoked 2 times according to JProfiler.
How can we solve this problem to reduce the number of calls to one???
TIA
Ashish

Anyone having slightest of idea about this problem please reply....

Error 0 occured at printing invoke node blb bla bla..., if I try to change the Postscript printing to bitmap printing using Options-printing menu.

Who might comment why I can not change the printing type without Error message in LV8.0.1. LV6.0 worked OK. Info: It is Russian locale system.
BR Vladi

Anyone?

Where is the best target location to put configuration files (.csv), report templates (,dotm) and instructions (.pdf) when building a LabVIEW program and installer?

I am unsure of the best location to the above type of support files. I would like the files to be available to all users accounts. If I place them into something like c:\LabVIEW support files this can create an issue if manual changes are made to any of these files by a user without administrative rights. I can also place them into public documents. Any recomendations?
Related. I have added a PDF "help" file to the project. and given a path in the VI properties documentation field. I have then added a custom runtime menu with "Help for This VI". Running the application on my development machine, it works just fine. Making this in an application installed on a test machine, results in the application crashing. The PDF file is in the correct location on the target machine. Any ideas?

It seems you want to put the files where just any user can't get to them to edit them. Unfortunately, if the user account can't get to them, I don't think LV will be able to get to them. I could be wrong. To test this out, use a target location somewhere under your user account folder and then have another user try to run the app. if LV finds them then that gives you more options. If not, then you are going to have to have a common location that users are not likely to go to.
I generally create a dedicated folder structure for LV apps on a target system as shown below. I also make this the My Documents folder so that the LabView Data folder is created under this structure. Yea, it means that users can get to the files but that's where training needs to be executed. If you are in a network environment, you can place the templates, config (ini) files, etc on a network location and users are a bit less likely to inadvertently navigate to them.
I use both for some apps, Local folders for system specific files and Common folders on the network for files that all systems will share.
Not sure if this will address your location issues but thought I would share it nonetheless.
Doug
"My only wish is that I am capable of learning each and every day until my last breath."

Possible to use an icon other than the default when building a distribution executable for a third party customer ?

I build stand-alone exe's for customers, and would like to know if in the "Build Distribution Kit" dialog there is an option for using a non-standard icon? If not, what else will work...? Thanks.

1. Using windows "START" button,
START->Programs->National Instruments CVI
->Utility Programs->Icon Editor.
2. Double click the icon editor.
Create your ICON.
3. Save your icon by,"FILE" "SAVE AS"
xxxxxx.ico. I suggest you save the
icon in your program folder.
4. Now build a stand alone executable.
CVI will ask for "name" and "path"
of the icon.
5. By dragging the .exe to your desktop
your icon will follow.
6. When you create a distribution kit the
icon will be placed into the kit.
7. After the customer installs the kit
the icon will show up in a small window
they can drag the icon to the disk top
or drag the .exe to the disk top at a
later time.
James Holmes
Trak Microwave Tampa Fl.
(813)884-1411 ext. 247
jhol
[email protected]

1003 error at invoke node in .exe

Hello!
I Have a problem at an invoke node when running an .exe and I have no idea what the problem is. There's no problem in the development system.
Here's a picture of the code..
Thanks in advance
Attachments:
exe_error.JPG ‏72 KB
exe_error1.JPG ‏72 KB

To find out where the error originates, place a probe on the error cluster wire and monitor the point where the error first appears, it will be the object in front of the probe.
R

Frontpanel opened by Invoke Node blocks other FP

Hello,
In a project I am working on I would like to open and close a frontpanel displaying a few plots from a different VI. I have managed to create the Visualisation VI and am passing references to the Indicators and the VI itself on to the next block. I can open the FP by using an Invoke Node on the VI ref, but then I can only interact with the newly opened VI. To get back I have to close it by hitting X, I would prefer it if I could just have it running in the background or minimized once I click on my "main" Vi again. I have attached the required VIs.
Solved!
Go to Solution.
Attachments:
FP_Open_plots.zip ‏63 KB

Hi,
I can't see your code as I haven't upgraded to 2014 yet (shame on me ). Here is a Main VI that opens a Graph VI in two ways:
1. Without running it, just by FP.Open. The main VI remains responsive. This is not really recommended but I think it was what you meant to do.
2. (enable disabled diagram): by running the VI using the Run VI invoke node. In this way the Graph VI is called dynamically and the Main VI doesn't wait until it's done to continue.
Good luck,
Danielle
"Wisdom comes from experience. Experience is often a result of lack of wisdom.”
― Terry Pratchett
Attachments:
Main VI.vi ‏11 KB
Graph VI.vi ‏33 KB

"Failed to load excel file" an Error Message while running TDS upgrade util

Dear All,
"Failed to load excel file" an Error Message while running TDS upgrade utility when clicking on CHECK DATA.
Please help me out on this!!!!!!!!!!!!
Thanks..........

Not all data can be exported to Excel easily. Especially if the query result is huge or there are special characters in the query results. You may try the most updated version.
Thanks,
Gordon

"Error 7 occurred at Invoke Node..." when attempting to open .vi for editing

I am attempting to open a vi for editing, and instead the vi is attempting to execute. I get the error:
"Error 7 occurred at Invoke Node in BuildTargetBuildSpecification.vi->BuildXFS.vi"
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, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
Method Name: Project: Open
When I close the Error Message dialog, Labview terminates.

Hi R.Jay,
Error 7 generally occurs when trying to create an executable when there is an extra instance of a top-level vi. You may need to remove the file as a support file (but leave it as the top level vi).
Are you trying to run an executable that has already been created? Unless you have already built an executable, it should not automatically run when opened. Also, was it built in a previous version of LabVIEW? Sometimes this error can be seen when you upgrade to a newer version without compiling.
Regards,
Lauren
Applications Engineering
National Instruments

Why do I get an error 1000 when using vi server with invoke nodes?

I use the invoke nodes with set control value and run vi. I want to use the called vi on the same machine and in parallel and I do not want to wait until it is done. If I set wait until done to true it works, if I set it to false I get the error message. Why is that and how can I solve that problem??

Hi,
Using LabVIEW 7 I was able to do what you want. I modified an existing example. The main vi will load the a second VI, and then the main VI will do "set control value" on a numberic labeled "Numeric" and you'll be able to see that it is changing the control value.
I've attached the modified VI.
Attachments:
parallel.zip ‏148 KB

Error when executing VI with "Invoke Node" in loop

Hello,
please check if this is possible what i am doing here or if there is a better way to do it.
The goal is to have a VI that i can start in TestStand which is then running in a loop until i set a global variable.
I do this currently with:
1.) Starting the VI with "Invoke Node" (see screenshot 01)
2.) This Vi is then running all the time in a loop until the global for exiting is True (screenshot 02)
3.) Then i have another VO to set the Quit-variable to true
Normally this works as it should, but sometimes i get the error-message:
Invoke Node in NameOfTheViCalledInTestStand.vi
Method Name: Run VI
VI Path: NameOfTheViThatContainsTheInvokeNode.vi
LabVIEW: Das VI befindet sich in einem für diese Operation unzulässigen Zustand.
The question is: what does this error mean and what better ways are there to do what i want to.
Perhaps for better understanding, the VI which runs in a loop executes dll-functions to enable and disable an ample-tower to make a light blinking.
And because there is no function "blink", i have to make it on off on off on off....
So the vi loops and makes on off until i say "quit" then blinking stops.
Thanks for any ideas
Attachments:
01_InvokeNode.jpg ‏8 KB
02_ViRunsInLoop.jpg ‏23 KB

I cant´t do this "Try changing the "Run" node
to "Wait Until Done" = True." because then the TestStand-Step is
hanging until the loop is finished.
I only want to start the "blinking" and the continue normally in the sequence.
To
avoid that the vi with the "Invoke Node" is started twice a have a vi
above it whick checks with the globalVariable "IsCurrentlyBlinking" if
the start is allowed.
If IsCurrentlyBlinking= True then nothing happens.
So normally it can´t happen that it starts twice. Only if the GlobalVariables are not correct.
The
variable "IsCurrentlyBlinking"is set to TRUE in the subvi before the
loop starts and after the loop is finished its set to FALSE in the
subvi.
Attachments:
03_CheckStart.jpg ‏16 KB

Error 15 at "Run VI" Invoke Node When Building a LabVIEW Executable

Similar Messages

Maybe you are looking for