LabView 3.1.1 App Build Error

I have a LabView 3.1.1 App that had been built and was running, and needed a minor change. I made the change and tested it, and it ran fine.
I followed the instructions on how to build an application, but after saving all the VIs in a single .llb and selecting Build Application, I get a Status window that says "Building Application" then another that says "Resource not found. Build Application failed."
Anyone remember running into this error and what the cause is and its solution?

Hi JHA,
For LabVIEW 3.1.1 you will need Application Builder 3.1.
Do you get the issue when building a very simple VI (e.g. add two numbers)? If you do, there might be an issue with the Application Builder and you might want to reinstall it.
If you don't get the error with the simple VI, you might be missing resources needed for the VI you are trying to build. Make sure that all support files are included when building (dll's, dynamically called VI's, other files).
Has anyone else seen this issue with LabVIEW 3.1.1 and solved it differently?
- Philip Courtois, Thinkbot Solutions

Similar Messages

LabVIEW 5.1.1 App Builder doesn't work on WinXP or 2k?

G'Day All,
I have a client that needs some apps written in LabVIEW 5.1.1 built into exe's, but I've found that once I install the App Builder on my Windows XP and 2000 PCs, I get "dist build app image subvi is not executable" - I've tried opening the wiring diagram to fault find, but it is understandably passworded. Has anyone come across this problem, and if so, how do I get around it?
cheers,
Christopher
Christopher G. Relf
Certified LabVIEW Developer
[email protected]
International Voicemail & Fax: +61 2 8080 8132
Australian Voicemail & Fax: (02) 8080 8132
EULA
1) This is a private email, and although the views expressed within it may not be purely my own, unless specif
ically referenced I do not suggest they are necessarily associated with anyone else including, but not limited to, my employer(s).
2) This email has NOT been scanned for virii - attached file(s), if any, are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility.
3) Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed.
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

Christopher
LabVIEW 5.1.1 is not supported under Windows XP. The first LabVIEW version that we tested and do officially support under this OS is 6.1.
On Windows 2000, you may get this error if you install the Application Builder 5.1.1 on the machine that has LabVIEW 5.1 on it. Both versions have to be the same.
I Get Errors After Installing Application Builder 5.1.1 On Top of LabVIEW 5.1
Zvezdana S.
National Instruments

DPS APP Builder Error Code 1

Hello,
I'm getting an Error Code 1 message when trying to download the test APP from the DPS APP Builder. I've tried re-building the document (a process that takes almost 8 hours in my case as our APP features 110 articles including almost 1000 images), updating it, generating new certificates and any other workaround mentioned in a previous discussion about this same subject. Nothing worked for me.
The only workaround I haven't tried is deleting the folio from ~/Library/Preferences/StageManager.BD092818F67280F4B42B04877600987F01 11B594.1/Local Store/dmp.
Apparently, there's nothing called "StageManager" in my MacBook Pro. Not in this route neither in any other route.
Any idea about how to solve this? (if possible without re-building once again the whole document) We can't wait until the error code 1 bug is fixed in future Adobe updates as we need to submit the APP to Apple next week.
Thanks for your time.

Anyone can help??
Update my latest experimental results.
I found that issue was folio package related.
Because when I use another folio package to the same app item in App Builder, this error message does not appear.
But the original package in exchange, this error information occurs.
Are there helpful to solve this problem?

App. builder error

Has any one had any problems using the MxBASE VI when trying to use the app. builder?

There are a couple of known issues. Have you seen these KBs?
NI-DAQmx Base Program Does Not Work as an Executable
Application Builder Hangs/Crashes when Trying to Build a DAQmx Base VI into an Application
I would suggest taking a look at those. If that doesn't solve your problem, just re-post
-Alan A.

App Builder error with app icons

never seen this error before…
all the icon names are unique, I've always named then 29x29.png 512x512.png etc
I'm also only building this for iPad, so also confused about the iPhone ref. Anyone seen this error before??
Cheers
Alistair

Custom slot labels are the optional navigation buttons (such as "Store," "FAQ," etc.) that enterprise publishers can add to their apps. It's not related to the standard app icons.
Are you building an app using an Enterprise account? If not, there's a bug we'll need to look at. If so, check the Customized XML Strings (?) option in the advanced settings of the App Details pane. Delete or re-create the XML file.

App Builder Error 8

Hello anybody!
I upgraded my LV 8.0 to 8.0.1 and get Problems by Application Builder.
I done "Mass Compile" of LV8.0 Directory and all of my Projects.
The Error Message is following:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 8 occurred at ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Rule_Editor.vi -> EBUIP_Item_OnDoProperties.vi -> EBUIP_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error.
NI-488: DMA hardware error detected.
What is it? Can anybody help me?
Thanks
LabVIEW Portal

Thanks for your answer, but it doesn't solve my problem. I haven't problems with the .alias file. I use default settings for .alias file.
Any ideas more?
p.s. important information: this error occures only if Subversion & Tortoise are installed.
Message Edited by Eugen Graf on 02-06-2007 04:46 AM
LabVIEW Portal
Attachments:
Error8.PNG ‏23 KB

App builder error 7

Building an app from a top level VI that uses VIs we wrote and put in an .LLB file, I get "Error 7 occurred at Librarian Get Info.vi-File not found." We have built applications before without this error. The files in the .LLB use a DLL, which is in the same directory as the source VI.

This KnowledgeBase describes the error you are receiving. If you are calling any VIs through VI Server, you must include them as Dynamic VIs in the built. Let us know if, after trying this, you still have trouble with it.
J.R. Allen

App. builder Error 1003 occurred at ..... internal.llb

Hi,
I have an RT application that uses three FPGA PXI-7831R. The application was created with LabVIEW 7.0. We upgraded to 7.1, then to 7.1.1. We followed the instructions for 7.1.1, mass compile LabVIEW and mass compile our own code.
For the FPGA I had to create projects. I built the loads for each of them, updated the Open FPGA References in the RT code and then I was easily able to build an EXE with application builder. However, that load contained errors, so I had to debug it. I changes aliases in the FPGA projects, recompiled the 3 FPGA loads and refreshed their references in the RT code. I was able to debug the code and solve all my problems. That load would run with LabVIEW environment, downloaded to the RT target.
However, with application builder, when I compile that new load, I get: Error 1003 occurred at … internal.llb… The VI is not executable. I verified the VIs and their arrows are not broken. I already had "BldApp.RemovePolyVIsandTypedefs=False" in LabVIEW.ini. I opened my RT top level VI and performed ctrl-shift-run and LabVIEW becomes not-responding, taking 99% of the CPU, in that state for 90 minutes. I repeated that with a lower level VI containing FPGA Read/Write Control and got the same behavior, ctrl-shift-run makes LabVIEW to process I don't know what until I kill it. I could repeat that on 2 more PCs. However, it is ok if I do that with a VI not containing FPGA references.
The VI stated to be non-executable contains call to FPGA Read/Write Control. I removed these calls to debug and I got the same Error 1003 on the next VI containing an FPGA Read/Write Control. Are there some known issue with application builder and accessing FPGA with LabVIEW RT 7.1.1?
Thanks!

Hi, AvernaFrca
You shouldn't have any problems when creating an EXE in LabVIEW that calls the Open FPGA VI Reference or the Read/Write Control VI. There are a few KBs online that relate to that error number, but it seems that you have read them already, because the suggested fixes are to mass compile (or do Ctrl + Shift + R) and that doesn't seem to fix it for you.
In your case, I would recommend you to make sure that your VIs are not corrupted. The easiest way will be to create another FPGA VI that you could call from a brand-new host VI. It can be something as simple as just do A + B. If that does work, then it might be a problem with your current VIs and it might be a good idea to recompile them, just to make sure. Hopefully that will take care of it. If the error is still present, then the problem might be the actual Read/Write Control VI, and we will have to fix or replace it with a new one.
I hope this helps! Let me know if you have any additional information.
GValdes

Web-based app builder error

hi!
what does it mean?
thank you

Hi, can you please help us track down this problem by sending me a private message with the following info:
The initial title you gave to the application when the error was triggered
Operating System
Browser and version of the browser
Any installed addons you know of that may interact with the page elements.
Also, can you please tell me if the error is easily reproduceble:
Edit the app, change the application title to what you originally intended and see if an error is shown next to it (you should see an exclamation marked inside an orange triangle). Cancel the changes since this is just a test.
Thanks and best regards,
Dan

Signing Failed on DPS app builder

Hi, I tried all the solutions you posted in
http://helpx.adobe.com/digital-publishing-suite/kb/download-sign-failed.html
and still the app builder error persists and says signing failed, my app is in russian and I deleted all russian letters from article titles and folio name with no luck and I'm 100% sure of the apple certificates and provisioning profiles, any sugestions ?

I'm sure I exported the .p12 key correctly , i have another app and it's published on the app store with adobe DPS so i'm familiar with the process , I also -for the sake of this argument- redid the whole process again and i even revoked the current certificate and recreated a new one from apple developer portal and exported the new key for that certificate (after deleting previous certificates from keychain)
Also it doesn't work for neither the developing key nor the distribution key which makes it very unfortunate coincidence to have two unnoticed errors one in the developing key and one in the distribution key .
Thanks for your response

Cant sign to DPS app builder in to download distribution ZIP file

I cant sign in to DPS app builder, with the very same P12 and distribution certificate I used to create the app. the app is visible in the DPS app builder. however I just cant download it. Right before download it asks me to sign in... i define paths for P12 file and distribution certificate and i type my pass for P12 file... but after a while it returns me sign ion error message - conatantly.
Btw, my folio and article in it doenst have any special chars (only a-z). Thank you.

Try the following if you are a Creative Cloud customer:
1) Make sure DPS App Builder is no longer running on your machine. Go to the DPS App Builder menu and make sure you quit, so it's really shut down.
2) Sign out of Folio Builder Panel in InDesign, then close InDesign.
3) Run InDesign and sign into Folio Builder Panel
4) From Folio Builder Panel select Create App in the flyout menu and proceed with the app creation process.
If you are getting a signing failure, rather than a sign in failure, try the three solutions at http://helpx.adobe.com/digital-publishing-suite/kb/app-builder-error-signingfailed.html.
Neil

Error 1305 when installing LabVIEW 7.1 app built with app builder

I have built an executable with installer from LabVIEW 7.1 app builder. The app installs/works fine, however 1 user reported 'Error 1305' when installing the app from a DOS subset on a WinXP machine. For example, a virtual drive is created using the DOS 'subst' command (see http://www.easydos.com/subst.html for more info), e.g. 'subst z: c:\temp'. Now when running z:\setup.exe, the error 1305 is encountered. If the same app is run from c:, e.g. 'c:\temp\setup.exe', it works fine. Is this a bug in the installer, or in the OS...?

Greetings,
This is an architectural issue with the Microsoft Windows Installer and Windows, and will occur with any MSI (not just those from the app builder). Under XP, a MSI cannot install from OR install to a location created by the "subst" command. My understanding of why is that installSequence runs in the context of the MSI engine, which is running as "system" user. But the subst command is a per-user setting (local to your account) so the MSI engine doesn't see it.
The only workaround is to run the MSI from a non-subst drive, or instead use network file shares (you can simulate what "subst" does by mounting an exported file share from the same machine).
Regards,
- WesW / NI

My executable compiled with Real Time Engine 5.1.1 in App Builder gives error when trying to run in App Builder with RTE 6.1

Hello. I built an executable using App Builder in LV 5.1.1 and now, years later, I am trying to run it in LV 6.1 but I get an error stating a requirement for Run Time Engine version 5.1.1. To be able to run this, must I install the older version of Run Time Engine? If so, where can I find the older version? Do I have to install the older version of LabVIEW to get the RTE? Will having both versions on my pc be a problem?
I assume that once I am able to run the exe, that I will be able to recompile with the newer version of the RTE using App Builder. Is this correct?
I have been away from LabVIEW for several years and am a bit rusty on these details that I once knew. Any help is appreciated.
Alex

The version of the run-time engine must match the version of LabVIEW that was used to create the executable. You can get any version of the run-time engine you want here. The only way to create a version 6.1 exe is to re-build it from the source code with diagrams. An exe has no block diagram so it cannot be converted to a newer version.

Application Builder error in LabVIEW 7.0

I am maintaining some legacy code in LabVIEW 7.0. I have recently (perhaps within the last month or so) been getting Error 1003 in Dist Copy Non-VI Files.vi (part of App Builder) when building my code. I've done some testing, including trying to build much simpler VIs, and get the same error. Curiously, this occurs on multiple (Windows XP SP3) machines, both "real" and "virtual", including on two of three installations on a single PC (so it is not hardware-dependent).
I have a strong suspicion that the problem is neither my code nor LabVIEW itself, based on the following logic: 1) This problem arose on multiple PCs at about the same time (i.e. I don't recall seeing this a few months ago, now I see it on almost all of my PCs). 2) There are two PCs where I do not see this error -- when I check the LabVIEW installation files between a PC that "works" and one that doesn't, the differences seem (to me) to be small, more related to "what did I do most recently" or "how much of MAX did I install, which drivers". (3) Using or not using OpenG in my code mades no difference, nor does turning off Anti-Virus scans.
I tried two other things. First, I have a VM that I recently build (which I think is significant) that has both LabVIEW 7.0 and LabVIEW 7.1. The build fails with LabVIEW 7.0, but succeeds with LabVIEW 7.1. In addition, I found a VM, built a year ago and "sitting idle", with LabVIEW 7.0 on it. I fired it up, did not allow Microsoft Update to update anything, and tried the build with LabVIEW 7.0 -- it worked!
My current working hypothesis is that some "patch" installed by Microsoft (.NET? ActiveX?) has clobbered something in the LabVIEW 7.0 Build Application. Unfortunately, the VIs that make up this application are password-protected, so I can't see "inside" to discover what file or other condition is responsible for the error message.
Does anyone have any ideas or suggestions? [Don't suggest "Upgrade to 7.1" -- I'm the only "maintainer" of multiple PCs and multiple applications, some of which run on systems "belonging" to other people. I am in the process of rewriting the code in "modern LabVIEW" (2011) and will port it widely, but until then, it's not practical (or "politically correct") to make the 7.0 -> 7.1 shift ... Besides, my curiousity is piqued!]
Bob Schor
Solved!
Go to Solution.

Good point. The reason for my "laser beams" is several fold. First, I follow a written protocol (I wrote it!) whenever I install or re-install LabVIEW 7.0, so I'm pretty sure that all of the installations "should be consistent" (if not identical). Second, I compared two NI folders in Program Files between a version that worked and one that didn't, and while there were differences, it seemed "not likely" to be an explanation. Third, I'm 99% sure that at least one of the systems that now cannot build (of the eight installs, all by me, that I've checked, only three worked, and one was on a PC that hadn't been turned on in over a year, hence was certainly not updated) was able to build previously (i.e. I don't recall seeing this problem until about a week ago, when I started re-building an update to my legacy application). It is possible that this problem was always present on these systems, but doesn't seem likely.
Nevertheless, before the beginning of next week, I plan to take one of my "failing" systems, uninstall LabVIEW (but not change the OS in any way), reinstall it, and see if I can build. If this still fails, I'll take the "old" system I mentioned above and start bringing it "up to speed" until I "break" the App Builder. Note that it is possible that MicroSoft is not to blame -- I have other software (such as editors, utilities like WinZip, etc.) that have also been updated, and one of them might have clobbered the Builder.
Will let you all know what I find.
Bob Schor

App Builder produces "Not Executable" error with Strictly Typed VI Refs

There is a very frustrating problem with the app builder in LV 8.0.1. Certain VIs compile and run fine in labview, but the app builder
refuses to make them into applications.
The error message is very long and ends with something like "The VI is not
executable". Standard advice for this problem is to force LV to recompile
everything you're building by either mass compiling or ctrl-shift clicking the
run arrow, but this hasn't worked for me in two separate cases (completely
different projects).
It seems that this problem is caused by wiring a strictly typed VI reference to
an invoke node with the FP.open method selected. In both cases I resolved
the issue by changing the Static VI Reference to be weakly typed (right-click
the static vi reference and make sure "Strictly Typed VI Reference"
is unchecked). After that, the project build successfully.
This is very hard for a user to track down for several reasons:
- The error message in the application builder does not give any
indication as to what the real problem is
- The app builder reports that the top-level VI is broken, even when the
strictly typed reference and invoke node may occur in a sub VI
- Nothing (that I can
find at least) in the documentation suggests that strictly typed references
won't work with the Open.FP method.
There is a page that says "some of the properties and methods do
not work when you configure this function to output a strictly typed VI
reference," but no indication is given of which methods fail
Note that in one case I was also able to make the project
build by deleting an instance of "IMAQ Create.vi" from the top-level
VI. I
have no explanation for this.
Hopefully this post will save some other users the trouble
of tracking this down and maybe even get NI to correct the issue for future
versions.
Adam Brewster

Hello Adam,
Thank you for sharing your experience and insight. Your post was well thought-out and offered a
good description of the problem as well as some possible workarounds. I believe that the issue has been filed and
is under investigation (3TU8T8V9). Feel
free to post back after the next LabVIEW release and inquire as to its status.
Thanks again,
Travis M
LabVIEW R&D
National Instruments

LabView 3.1.1 App Build Error

Similar Messages

Maybe you are looking for