Again, reporting this information also helps with tracking down the problem. Sign In Now Sign in to follow this Followers 0 Go To Topic Listing LabVIEW General All Activity Home Software & Hardware Discussions LabVIEW General vi path for asynchronuos call in Ensure that all VIs used in the distribution have unique names If two VIs of the same name located in two different places are called, the Application Builder may give this The only thing the error says is to make sure the VI isn't broken and that it runs. have a peek here
They said the issue was that during the build process it looks at all the VIs that are dependencies and determines if the code is broken. Certified Professional InstructorCertified LabVIEW ArchitectLabVIEW Champion"... Use the following Knowledge Base to troubleshoot this error and let me know how you get on:http://digital.ni.com/public.nsf/websearch/705C2ECA081F3C7986256C0F00559B02?OpenDocumentKind regards SarahApplications Engineer | National Instruments | UK & Ireland Advanced Category of App One of the work around that has worked for me in the past (when dealing with this issue ), was to isolate the lvclass with problems in a separate virtual folder http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02
All rights reserved. | United States MY ACCOUNT   INNOVATIONS SHOP SUPPORT COMMUNITY Home Community Home : Most Active Software Boards : LabVIEW : Error 1003 when loading subpanel VI in I don't think that this is the case (but I will check to be sure). Error 1003 can occur if any subVI is not executable. Any help would be appreciated.
PJM Share this post Link to post Share on other sites jgcode 319 LabVIEW Renegade Moderators 319 2,397 posts Location:Australia Version:LabVIEW 2009 Posted February 25, 2010 ...was to isolate the You can then check those dependencies one by one for issues to work out which subVI (etc.) is causing the error. Check the "Enable debugging" option in the "Advanced Category" of the application executable properties2. test case call by reference.zip 714 KB 0 Kudos Message 20 of 22 (215 Views) Reply 0 Kudos « Previous 1 2 3 Next » All Forum Topics Previous Topic Next
Between this error (1502) and error 6 (file I/O=Path too long), building an executable is getting really difficult. I have better things to do with my time than to deal with people like you. Open the VI in LabVIEW using File » Open and verify that it is runnable. When building the SubVI for its own, the build is successful.
This is what many of the labview examples do, so take a look in the example finder (specifically the section on controlling applications programmatically, which is code for "VI server"). then was able tobuild the application successfully.Is it possible that the development version of LabVIEW 8.0 is smartenough to ignore broken code in a 'disable diagram', but theApplication Builder is not? If Have you upgraded to the 8.0.1 patch? Mass compile the VI before you build the executable.
Hope that it can help. 8 Replies 10 Views Switch to linear view Disable enhanced parsing Permalink to this page Thread Navigation nanotube 2006-01-12 18:41:19 UTC nanotube 2006-01-12 21:11:16 UTC Darren https://lavag.org/topic/11989-argh-exe-builder-says-my-vi-is-broken-but-its-not/ Copy the source distribution to the target or right-click the build specification and select Deploy. Whenever I run the host VI, I get one of the following errors: Error 1124: The VI is not loadable. Use the following information as a reference:Error 1003 occurred at ABAPI Dist Chg and Save VIs.vi -> ABAPI DistBuild LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi ->EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi
Mike... navigate here For now he has to enable the debugging flag to be able to build an exe. 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 Jump to content LabVIEW Any chance that's your bug?
more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed How to debug... Any ideas? http://cygnussoft.com/labview-error/labview-error-1000-run-vi.html Note: You have to go through all the previous steps when the top-level (or any subVI) contains a timed loop.
B Member 10-05-2011 11:19 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report to a Moderator Hello, I have found the He use a lot of classes and he keep getting error 1502 (Cannot save a bad VI without its block diagram.) [Note: Everything run fine in the IDE, nothing broken]. Sign in here.
One of the VIs must be missing. The KB linked below gives some more information on this error. 'Error 1003 Occurs When Trying to Create an Executable' - http://digital.ni.com/public.nsf/websearch/705C2ECA081F3C7986256C0F00559B02?OpenDocument Its a known issue with LabVIEW 8.0 that using the Diagram For now he has to enable the debugging flag to be able to build an exe. Let's see, nothing too fancy in the top-level VI, no classes or Mathscript.
It's easy! I am having similar problems building an exe from a project that uses many GOOP4 classes. Putting an indicator on that VI won't help because it can't execute. this contact form George I have a very similar thing happen to my customer.
When editing VIs in this specific instance, you get some strange behaviours (e.g. What OS? It'sstrange that I didn't have this error when I execute the programdirectly from Labview (without building it)... Sorry for the confusion.
I used "explain error" function to learn this is an undefined error. Since no source for the error is shown then I'm at a loss.