Administrators 274 5,737 posts Version:LabVIEW 2015 Since:1994 Posted May 5, 2006 As long as your plugin VIs and all of their subVIs are in the same flat location (irrespective of whether I don't think that this is the case (but I will check to be sure). Can you post one of the dynamically called VIs that is broken when called in the exe? Share this post Link to post Share on other sites PJM_labview 32 The 500 club Members 32 777 posts Version:LabVIEW 2009 Since:1998 Posted February 25, 2010 I have one of Source
My Profile | RSS | Privacy | Legal | Contact NI © 2014 National Instruments Corporation. The application builds withou an error. But if I run the executable I always get error 1003 an Open VI Reference: the vi is not executable I really made Your plugging VIs dont have to be part of executable distribution. When I run the application, I receive error 1003. http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02
Why Do I Get Error 1003 From Application Builder When I Try to Build Excel Macro Example.VI? However, if the VI being called by VI server is not static, for example if it is changed after build time and you do not want to rebuild and distribute the However, everything within the project is already under "always included" section within the build. If it does not need to be dynamic, just use a static VI reference.
BTW, I am able to build other executables.
PS. Also what is %s type information in labview because that might help me find the error? Please Contact NI for all product and support inquiries. How is this handled within executables?
It is important that the whole hierachy of the VI be accessible and that the executable installer has correctly... Runtime Error 1004 Like building an exe all the linkages will be updated. Share this post Link to post Share on other sites Aristos Queue 538 LV R&D: I write C++/# so you don't have to. This problem needs to be fixed for real, it's giving pain to a lot of large projects, from what I saw on NI forums Share this post Link to post Share
If you do not make any changes to the VI and receive a prompt to save changes when you close the VI, some subVIs were found in a different location. A common reason the VI cannot run is because LabVIEW cannot locate it or one of its subVIs. Or sign in with one of these services Sign in with Facebook Sign in with Twitter Sign in with LinkedIn Sign Up All Content All Content This Topic This Forum Advanced We have a knowledge base article that should serve as a good start point to troubleshoot this issue:http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02?OpenDocument Joel I.Applications EngineerNational Instruments 0 Kudos Message 2 of 2 (139 Views)
Well, LabVIEW has a LOT of error information and much of it has gotten fairly descriptive over time. recommended you read Sign In Sign Up Browse Back Browse Forums Downloads Gallery Staff Online Users Activity Back Activity All Activity My Activity Streams Unread Content Content I Started Search Labview Error 1003 Open Vi Reference Figure 2: Build Option 2) Remove the PPL from the project and use the original un-packed library. He spent several days trying to fix this, without success.
All rights reserved. Cart|Help KnowledgeBase Request Supportfrom an engineer NIHome > Support > KnowledgeBase English 1 ratings: 3 out of 5   Why Do I this contact form Sign In Sign In Remember me Not recommended on shared computers Sign in anonymously Sign In Forgot your password? Once opened clicking on the broken-arrow can deliver nice error detail - even in a run-time environment! So by doing a Source Distribution per plugin you'll get the plug-in VI plus all its dependencies linked into a new hierarchy of your choosing (you can have it all in
Please note that in order to use NI-CAN functions in an application, you must have NI-CAN installed on the application's target machine. Mass compile the VI before you build the executable. Edit: unless there is a major change of behavior in LV8... have a peek here Showing results for Search instead for Did you mean: Reply Topic Options Start Document Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the
Administrators 274 5,737 posts Version:LabVIEW 2015 Since:1994 Posted May 10, 2006 Thanks so much for everyone's help - I appreciate it greatly. All rights reserved. Cart|Help KnowledgeBase Request Supportfrom an engineer NIHome > Support > KnowledgeBase English This Document is not yet Rated Error 1003 Occurs When Thanks!
This screws everything up if you create an installer and bundle your plugins and their subVIs with it (thus moving the VIs from their original locations) - even if you preserve Something that I forgot to mention is that this is happening with LV 2009 service patch one. Answered Your Question? 1 2 3 4 5 Document needs work? This forces LabVIEW to recompile, re-link, and recheck data dependencies from the ground up (as does the application builder), rather than in segments.
I shall be more careful in the future... It's easy! This isn't bad unless the 2 VIs are different some how, the first one loaded will "win", etc just like in the development environment. Check This Out Share this post Link to post Share on other sites george seifert 9 Extremely Active Members 9 399 posts Posted February 24, 2010 Hi, I had the same issue a
Is it OK that many of my method VIs have the same name by design? Please please please - does anyone know how to force the links between a VI and its' subVI to be relative (am I going to need to hack the VI's binary I'll try a few more experiments tomorrow to confirm that having a VI in the same folder/llb as its' subVIs works - like a flat structure - stay tuned Well, I've Why am I receiving this error?
My VI opens and runs fine in labview 2012.