Invoke Node causes error in VI

The attached VI is one of numerous VIs in an application that I "inherited". I am attempting to rebuild the application to incorporate some changes I have made. This VI has an error, which indicates that there is a bad or unwired terminal at the Invoke Node for the PrintOut method. According to the Help system, all of the unwired parameters for this node are optional, so the node appears to be wired correctly. What am I missing? Thanks.

Hello,
Thanks for attaching the VI. I believe the preview -> lost attachment issue has already been reported to the admins for this discussion forum.
As for your VI, I'm guessing this problem is happening because you are running a different version of Office than the computer on which this application was originally developed. On the PrintOut invoke node, try selecting another method in the method list. Then try selecting "PrintOut" again. This should re-link the method to the "PrintOut" method specific to the Word version on your computer, and you should be fine. By the way, the VI opens just fine (no broken run arrow) on my machine, and I'm running Office XP.
Let me know if this solves the problem. Oh yeah, here's a tip. I noticed that in this code, there is a Boolean constant wired to the "Close" method, but it's wired into a "To Variant" function to convert it to a variant. This explicit conversion is not necessary...for any ActiveX property or invoke node that takes variant inputs, you can just wire the native LabVIEW type directly into the input (without an explicit conversion) and it will work fine...this should save you some time as you write new VIs, or edit this set of VIs you inherited.
Good luck,
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Similar Messages

Build error after upgrading from 8.2.1 to 8.5 "Error 1055 occurred at Invoke Node..."

After upgrading to 8.5, I'm getting the following error when trying to build an EXE:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1055 occurred at Invoke Node in AB_Source_Library.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Object reference is invalid.
I have been building this application for both Windows and Mac OS, and I even get the same error when building the .app on an Intel Mac.
Things that I've already tried:
* Mass-compiling all my code
* Created the project from scratch
* Enabled each panel of the "diagram disable structure" one at a time and compiled again
Any ideas?

Hi Travis,
Ben’s advice if definitely the best place to start. Error 1055 is a very general LabVIEW error for “Object reference is invalid.” The cause is usually a bad install where important LabVIEW function aren’t placed in the right directory or aren’t installed at all.
Charlie M. CLD

Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi- AB_Build.lvclass:Bui

During software build to make exe file, I got the following error message:
Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
Method Name: Build:Application
The vi was working fine before the build. It just access some text files and creates some excel files. No hardware is involved. See if anybody know how to solve this problem. Thanks.

I am using LabVIEW 2014 and have been getting this error randomly, but fairly consistently on a recent build. I searched all over and could not find a solution that worked. However, just through trial and error I discovered that the problem is related to SSE2 Optimization in the Advanced properties window. I can consistently cause this error by enabling this feature and consistently compile successfully when it is disabled. Try turning this feature off and see if it solves the problem.
...UPDATE: After closing and re-opening LabVIEW this error came back, and did not seem to be affected by the SSE2 option. Not that it isn't related, but perhaps not the silver bullet I thought it was.
I also got the error to go away sometimes when I compiled the EXE while the main program VI was open, whereas it gave the error most of the time when no VIs were open...again, nothing seems to consistently solve the problem...there is definitely some kind of bug in the appllication builder, and it seems like there are a lot of people that have been struggling with this for a long time (as far back as LV 8)...hopefully NI eventually finds this bug and squashes it!..although, I doubt that anybody at NI is even looking for it...

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.

Error 1069 on Invoke Node

Hello all,
I'm trying to build an application we have. In one of the sub-vi's there's a call to invoke node to start another vi. When I run the program from the VI this works fine as it should. When I build my executable and have my .llb for the executable, the program gets to this point and I get the above error, Error 1069: The sub vi is not executable. I know there's no executable for this and the spawn vi that calls it is in the llb. Any ideas as to why it will work as a vi but not as an exe? Thanks for any help.
Gary

Aaron G wrote:
Gary,
A common reason for error 1069 is because you are attempting to launch the code from the executable environment and not a develoment environment. When it attempts to launch the VI, it may not find all of the subVIs, causing the VI to be reported as non-executable. One way around this is to open the VI that is dynamically launched, go to File>>Save With Options and choose Application Distribution. This will allow you to create an Application Distribution LLB file. If your executable launches the version of the VI that is in the Application Distribution LLB, it will work. As a word of caution, when saving files as an Application Distribution, the block diagrams are removed from the VIs, DO NOT OVERWRITE your existing VIs. You will never be able to edit them again if you do this. Alternatively, when you build the application, make sure that the VI is included as a dynamically launched VI in the list of included files.
Regards,
Aaron
Aaron, thanks for the reply. I am saving with options and doing the Application Distribution. I'm also getting error 1003 but it's still saying the possible cause may be that the vi is not executable. The vi's that the invoke fails on are not included in the llb but according to the previous version of the software (in LV 6.1) it's not needed. (I checked the old llb file and the options in application builder.) I have the spawn vi which calls the invoke in the llb. The spawn takes a path, creates a reference and then does the invoke on this path. The vi's themselves are not in the llb. Will these need to be moved in? And if so will the paths need to be changed?

Error 10000 at invoke node

There is an Error 10000 happened at invoke node in one of my subvi. Please see attached snapshot of the error message.
This program(VI) has run for one month, and yesterday this error happened first time. After I stopped the VI, and ran it again, there was no error anymore.
Can anybody tell me possible causes? Thanks.
WT
LV2013SP1
Attachments:
Invoke Node error at CallSubVI_Do.PNG ‏36 KB
Call_Subvi_Do(variant).vi ‏20 KB

weitong wrote:
Thanks. But, I didn't get what you said.
I am using "Call_Subvi_Do(variant).vi " to open and run another VI. Which one I should check the state of by using the Property node "Execution>State>Idle", "Call_Subvi_Do(variant).vi" OR the VI called by Call_Subvi_Do(variant).vi? By the way, the error is promted happening at the Invoke node in "Call_Subvi_Do(variant).vi" .
Yes on the top its happens in the sub VI but when you debugg the sub VI you may find that error occuring at the onvoke node "Run VI". Check the attached VI with added check for the state of the VI.
The best solution is the one you find it by yourself
Attachments:
Call_Subvi_Do(variant)_Anand.vi ‏21 KB

"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

Error 6 at Invoke Node in Dist Send Result File to RT.vi-- Build Applicaiton.vi

I am using cFP 2000 RT in my application. When I build exe and download the application to the cFP 2000 RT, I get "Error 6 occured in Invoke Node in Dist Send Result File To RT.vi--> Build Application.vi"
The steps followed.
1. In the LabVIEW 7.0 Main Panel, Select the execution target as RT Target.
2. Tools --> Build Application or Shared Library. In the Target Tab the destination directory is selected as \\xxx.xxx.xxx.xxx\c\ni-rt\startup automatically.
3. In the SOurce file tab, select the Top level VI.
4. Press Build to make the executable of the application. The application is built and at the end the error message is poped up. (see the attached file)
Software Configuratio
n:
1. LabVIEW 7.0
2. Field Point 4.0
3. LabVIEW RT 7.0
Help me solve this problem. Thanks in advance.
Attachments:
Error_Message_and_RT_Info.bmp ‏313 KB

This is most likely coming from the specific file it mentions in the error, Dist Send Result File To RT.vi. The error 6 means the file can't be found. One thing to try first is to add this VI as a Dynamic VI in Application Builder. Another option is to change the path that this VI is invoked from, or is not called by an Invoke Node at all.
I hope this helps, feel free to contact support if the problem continues.
Regards,
Robert Jackson
Application Engineer

Error 1003 occurred at Invoke Node

Good morning.
I work with LW8.5 and created with the following architecture:
There is main.vi on the links at the user's calls and runs the other VI.
That is, not directly, these are not included in the VI block diagram main.vi.
In the development of a happening in normal mode, all dynamically called VI,
But once I make EXE, when you try to call the dynamic VI error 1003.
Error 1003 occurred at Invoke Node in Main.vi
Possible reason (s):
LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File>> Open and verify that it is runnable.
VI Path: C: \ Shaikov \ Labwiev \ builds \ NSIAES \ Initialsettings \ Initialsettings.vi
Show you how to act?
Thank you.

Hello margasan.
In my Projects I use to pass more dynamic and VI classes.
In the attached file - an example of my project:
In the main folder is a folder UpperClass, it is the parent class and child classes and HeirClass.lvclass Heir2Class.lvclass are organized into folders respectively Plugin1 and Plugin2, and these Classes inherit from the parent one and the same WI - UpperClassTest.vi. Plus, this Plugin1 has two, independent from the others, but related classes. A block diagram for an object placed Core.vi UpperClass.
So, here, if you take EXE, making llb files and run them from start VI for each of the Plugin, then everything works OK.
But as soon as I on the block diagram of a Plugin will put any object UpperClass, or one of its nasalednikov, there arises a familiar ERROR 1003. Prompt, plc, margasan I get rid of it in this case?
Attachments:
Example.zip ‏1481 KB

Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi- AB_Engine_Build.vi- AB_Build_Invoke.vi- AB_Build_Invoke.vi.ProxyCaller

Hi there,
Hope someone can help me. I recently upgraded to LV 8.5 and am having a problem building a .exe which has a subvi in it that opens in a new dialog window. When I try to build this I get the following error:
Error 8 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
Method Name: Build:Application
I have built the .exe with the same subVi but without opening it in a dialog window and it works fine., so the problem seems to be linked to the inclusion of the dialog window.
Any advice greatly appreciated
Regards
Tadhg

UPDATe: I can get the .exe to build but now I get an error when I run teh .exe which is shown in the picture attached.
Attachments:
error screen1.JPG ‏122 KB

Error 7 occurred at Invoke Node in AB_EXE.lvclass

I get the "Error 7 occurred at Invoke Node in AB_EXE.lvclass" error when trying to build an executable in Labview 8.5.1. I can run the application without any errors but when I try to build the executable, I get the error. I have tried a mass compile of the project, tried ctrl + shift + run on the top level vi, and tried to mass compile the folder where the project is located and nothing seems to help. I have also looked at the project dependencies for conflicts and found none. I have made a new project and tried to build an executable from this same code without any luck. How can I get this to build an executable?
The exact error is:
Error 7 occurred at Invoke Node in AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.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, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
Method Name: Build:Application

Are you using the Report Generation Toolkit? A lot of error 7's during builds seem to be related to this toolkit. Any dynamically called VI's?
Take a look here and here.
Also search the forums for "error 7" and you'll find some other threads related to error 7 and the application builder.

Error 7 occurred at Invoke Node in Dist read linkages.vi- Dist Cmp Settings to Disk Hier.vi- Build Application.vi

Error 7 occurred at Invoke Node in Dist read linkages.vi->Dist Cmp Settings to Disk Hier.vi->Build Application.vi????
Hi I do not understand how to resolve this nagging problem.
I run the program in the development time and it all goes smoothly.
However when i wanted to build the program. I often run into this problem.
How to resolve it?
Clement

Hey Clement,
Which version of LabVIEW are you using? There some knowledgebases out there that address the issue. Click here for the first KB or here for the second one. Hopefully these would help.
Regards,
Chetan K
Application Engineer
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 7 application builder invoke node

I get this error when I tried to build an application. "Error 7 occured at Invoke Node in Dist read linkage.vi-> Dist Cmp Settings to Disk Hier.vi-> Dist Build App Image.vi-> Build Application.vi Possible reason, LabView: File not found.....and then NI-488 Non Existent board." Anyone knows why? I was able to build application just fine last night. But then when I tried to build it this morning, that's the error that I got. Thanks.

Check the info in this link:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=50650000000800000016730000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0&USEARCHCONTEXT_QUESTION_0=Error+7&USEARCHCONTEXT_QUESTION_S=0

Invoke Node causes error in VI

Similar Messages

Maybe you are looking for