Build Application

Hello, I have a vi attached from which I am building an application to install on anther computer without a licence. I am using Labview 7.0 and have installed Run-time 7.0 on the target computer.
The only problem is that when I try and run the built application on the target computer it doesn't work like the original vi and fails to report errors or save data, or communicate via the serial port which I have built into the vi as it should.
Is there something I am missing when making a build application from a vi. I use the very basic settings in build application and simply save a build to a certain location and hit build. I do not play with any of the settings in build application.
Nevica
Solved!
Go to Solution.
Attachments:
BARA3.vi ‏699 KB

I understood from your post that you're building an EXE file, right?
Why don't you build an installer, all needed drivers, dependencies (call it laike you want) will be encapsulated into that installer.
You can then install your code like any other software.
Way easier than trying to find out what you have to install besides your exe

Similar Messages

Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi- Dist Build LLB Image.vi- Dist Build App Image.vi- Build Application.vi

When trying to build an application using labview 7.1 and windows XP, I get the error
Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi->Dist Build LLB Image.vi->Dist Build App Image.vi->Build Application.vi
I've tried the crtl-shift-run as well as a mass compile and I still get the error.
Any ideas?
Thanks,
Mike

Hopefully this thread, or this KB article might help.
It seems like this could come from a lot of things, but there's suggestions in those which might lead you in the right direction
Message Edited by Day on 09-22-2006 02:07 PM

Why does Build Application vi work in development environment but not in executable; error 1025

Hello,
I have an application ("A") that I am trying to build using another application ("BuildA").
I can create an application for A manually from its project using the Build Specification, and it works fine (A.exe).
Also, when I run BuildA.vi in the development environment it calls the "Build.vi" correctly and again builds application A.exe just fine.
Then, when I make BuildA an application (manually) and run BuildA.exe, I would expect it to also create A.exe just like BuildA.vi did in the development environment.
However, it fails with the error:
Code: 1025
Open VI Reference in NI_App_Builder_API.lvlib:Build (path).vi->BuildA.vi<APPEND>
VI Path: <b>C:\TEMP\AppBuild\BuildA\vi.lib\AppBuilder\BuildTarget.vi</b>
I noticed this thread , which looks like a similar problem, but no conclusion was reached.
Why does BuildA.vi work fine in the LabVIEW environment, but the application BuildA.exe does not work? All paths are hard-coded, so it shouldn't be a path issue.
Thanks,
-john
Solved!
Go to Solution.
Attachments:
AppBuild.zip ‏175 KB

Interesting code. I'm curious how you came to decide 324ms in your while loop, and 58 in the other, and then 5136ms at the end. In any case I suspect this has to do with this line of text in the help of the Build.vi.
If you plan to run a build specification on the LabVIEW Run-Time Engine, do not include the Build VI in any of the VIs for the build specification.
I don't fully know what this means but it might be why it isn't working.
The Build.vi opens all Context (application instances) and then looks for the one named "NI.LV.MxLvProvider". This I assume is a application instance NI uses to build applications. It then uses this and opens some other VIs in this instance for the building. The error you are getting is "Application Reference is invalid" meaning it couldn't find the NI.LV.MxLvProvider instance it needs to build. Again I believe this maybe because you are in a run-time environment and that instance doesn't exist there.
At the end of the day I'm guessing since Application Builder is not free, NI probably doesn't include it in the Run-Time engine, which is free. So you can't build the way you want. You could have and EXE running in the run-time open an instance in the development, then run your VI from there if you must make this an EXE. It maybe easier to just edit the BuildA.vi to have a "Run When Opened" so that you double click the VI and it runs which behaves like an EXE sorta.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Error when starting DPS App Builder - Application not found

WTF folks.
This morning I open my document (CS5) and it says I have to update my folio tools (needless to say i hate it to be forced to do an update before I can start working).
Well, I do an update, both tools (Folio Builder and Producer Tools).
Now there seem to be some changes, I cant refresh my folio via menu anymore. When choosing the new "build app"-option I get an error :
"An error occured while starting DPS App Builder. The DPS App-Builder Application was not found" (translated).
German original version: "Beim Starten von DPS App Builder ist ein Fehler aufgetreten. Die DPS App Builder-Anwendung wurde nicht gefunden."
Any Solutions? Where to get the mysterious "App-Builder Application?"
edit: refresh is now only possible inside the folio it seems.

App Builder is nothing but a new name to Viewer Builder. Download it from DPS Dashbaord.

How to pass custom cookie from report builder application to SSRS Custom Security Extension?

We want to implement SSRS in SaaS model. We implemented Custom Security extension in order to authenticate users from other application. When user enters username/password, i would like to authenticate the user in other application and it will return some data which can be used for autherization. I am expecting the same set of data will be accessible during all autherization calls.
Currently we are implementing this in Report Builder application. I couldn't able to persist the information in cookie. Report builder removes all the cookies exceprt one cookie which is used by report server.Is there any way to share the information in all reportbuilder autherization calls in same session?

if you have your own data extension, you can using
HttpContext.Current.Application.Add("yourkey",
yourdata);
to save your data, but the issue I met it the key, I cannot find a key depended on report builder. If I use username, if the user open 2 report builder, both of them will get the same key and same data, but at this case the data should be different.
I hope it will help you.

Build application erroration Error 7

Could anyone kindly help me here, I have met "Error 7 occurred at Invoke Node in Dist Build App from LLB.vi->Dist Build App Image.vi->Build Application.vi" while I am using Labview 7.1 to build my exe installer for my customer. I encountered this error message twice during that process. The first time it when I launch build DLL and the second time is at build. After I press continue button, builder stops with no warning and error.
Thanks in advance
Willy

Hi Willy,
can you tell me if all of your VIs are made with the same LabVIEW Version 7.1 or is it possible that some were built in a previous version?
The Application Builder reads certain information from the VI in order to determine how to build the executable. Since there can be significant differences between two versions of LabVIEW, the build process may fail with an error similar to the one you mentioned.
You can convert your VIs to the most recent version by using the Mass Compile featurel. The Mass Compile feature will allow you to select either a directory or a LabVIEW .llb file to compile.
Hope that helps,
Stefan Henke
NIG

Error during build application

Software - Labview 7.1 PDA and Labview DSC 7.1
OS - WIndows XP.
When I try to build application in Labview 7.1 I get following error
"Error 7 occured at Build Application. vi >> Disk Cmp setting to disk hier.vi >> Dist report Read Link Error.vi."
Can anyone had idea why this error had come.
Regards
Uttam

Hi,
Try mass compiling your VI once before building the EXE
Tools»Advanced»Mass Compile
this link will explain how to mass compile.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/aa97c01071d7cf678625695100582f40?O...
Hope this helps
Regards
Dev

Build Application Error

I am consistently getting an Error 26071 when I try to build my application to make an .EXE. I am usling LV6.1, and Application Builder for it. The app. works just fine from within LV itself. There are no errors.
Specifically, the error message is "Error 26071 occurred at Build Application.vi >> Dist Call Create Installer.vi >> Win Install Create.vi >> Win Install Add Files.vi >> MSI DK Add Shortcut.vi", with possible reasons stated as "Windows GetCommError: The hex value if the code us x65D7".
This code used to build just fine before I added some code using the Winevent.llb library, retrieved from NI. I had done a mass recompile on it and my code, just in case there was LV version compatibility issues. I also copied the specific vi's from Winevent into my library and did another mass compile, to no avail. I am using VISA serial port vi's (the GetCommError made me think this might be related).
Any ideas on what I'm doing wrong or what I'm missing?
Jeff

Check out this knowledge base here and let me know if that helps solve your issue.
Tyler H.
National Instruments

Problem in build application

I build application (exe ) for my main VI but there is main problem if run my main VI in another PC without labview there is problem see figure for explain may problem
Attachments:
Mohammad 1.doc ‏552 KB
moh.doc ‏212 KB

Creation of an installer will only help you when the "hpe363xa,
nidmm ,niswitch" drivers are also included.
Beside an installer you could also install the drivers manually in the PC containing only the LV run-time.
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Using external llb when building applications

I would like to be able to update the SubVI's that an executable uses, but am having problems editing them after installation of the build application.
I am using the option "Small target file with external file for SubVI's" in the application builder, but I don't seem to be able to open the VI's present in the external library ("data.llb") after installation. I get the error message "ressoruce not found", when trying to open the file in LabVIEW. Does anyone know what might be the problem.

Caveman wrote:
> I would like to be able to update the SubVI's that an executable uses,
> but am having problems editing them after installation of the build
> application.
>
> I am using the option "Small target file with external file for
> SubVI's" in the application builder, but I don't seem to be able to
> open the VI's present in the external library ("data.llb") after
> installation. I get the error message "ressoruce not found", when
> trying to open the file in LabVIEW. Does anyone know what might be the
> problem.
Those VIs get just as much stripped of their front panel and diagram
unless you specifiy not to do that in the VI settings in Application
Builder. Without front panel you can not load a VI in the LabVIEW
editor. It is only good for calling
by reference.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Error 1003 when loading subpanel VI in build application (VI not executable)

Error 1003 loading subpanel VI in build application (VI not executable). I referenced all supanel VI callers in my build app. What am I missing?

Thanks for your reply!! I tried a few things I found online including the article you posted...this unfortunately did not solve my problem. Through some trial and error process I found the issue was with my build properties in the advanced section shown below.
I had to check LabVIEW8.x file layout to allow the subpanel VI to load into my main app. I didn't think to check this cuz my code was developed in version 2010. I'm guesssing some of the callers where originally created in older versions and needed the the LabVIEW8 file layout, even though all my source code is compiled in version 10. If you think I might be wrong on this assumption let me know.
P

Error when building application with Excel included

Hi All !
I've read several post on problems with Report Generation Toolkit when building applications that uses Excel or Word interactivity.
I've included both _Excel Dynamic VIs.vi and _Word Dynamic VIs.vi in my project and added them to the dynamic vis and support files.
When building I get the error :
The VI is broken. Open the VI in LabVIEW and fix the errors.
C:\Programmer\National Instruments\LabVIEW 8.2\vi.lib\addons\_office\_exclsub.llb\_Excel Dynamic VIs.vi
When opening that VI there is no broken arrow and all the vi's included in this is not broken either.
I've tried mass compiling and so on but so far luck.
Regards Morten Kahr
Regards Kahr
Certified LabVIEW Architect
CIM A/S

If you do a search on this forum you will find this to be a common and vexing problem. I myself had this same exact problem about a year ago, and it took me the better part of a day to track it down. As you will find by reading the various threads on this problem, there seems to be no specific cause for this, and it remains a mystery, and the solutions are no better than chanting voodoo, and probably just as effective.
One thing you can try is to force a recompile of your VI hierarchy. Open you top-level VI. If it's set up to run when opened, stop it. Hold down the Control key and click the run button. This will force a recompile of the application. Sometimes this works, sometimes it doesn't. Like I said, voodoo.
Another thing to look for is to check if you are using any diagram disable structures or case structures with a constant wired, as in trying to use the case structure to comment out code.
Are you using classes and passing by reference? There was a mention of this here.

Open a different vi than the startup vi from a build application in LV2009

When building an application (exe file), I have to select a vi as "statup vi" in the build specification. This vi opens its front panel and executes when I execute the application.
But I can still open the front panel of other vis by using a command line argument:
myapp.exe "myvi.vi
The startup vi still opens and runs, and the vi "myvi.vi" opens its front panel as well. That was before LV2009.
Since I upgraded from LV8.5 to LV2009, my shortcuts do not seem to work anymore. I also tried using a longer path with the new LV2009 exe structure:
myapp.exe "subdirectory\myvi.vi" since the vi is in a subdirectory. It does not work either.
1-How can I open a vi when launching a build application, like it was possible before LV2009
2-How can I (Why can I not) use the File/Open... menu item of a front panel window to open a vi that resides in side the build executable?
Thanks for any help.

Thanks Norbert for (incredibly) fast reply.
Well: in the advanced page of the build specification, we still see
the option "pass all command line arguments to application". If
disabled, only the arguments after "--" (two hyphen) are passed to the application
itself (according to the help for this dialog window). So I assume that the arguments before the two hyphens are interpreted by the runtime engine. In previous versions of LV putting a vi path (inside or outside of the exe) would open its front panel - even though doing a quick search I could not find documentation about this feature...
Is there any documentation about which arguments are
accepted by the runtime engine when the mentioned option is disabled?
Can we not give a vi that should open (anymore)?
Baptiste

Building application with microsoft agent

Can someone clarify if there is anything different that needs to be done while building a stand-alone application that includes VIs that use the MS agent voice VIs (for example MSagentTTS.llb) along with CGI VIs? I have been able to build applications with only CGI VIs but failed while adding MS agent VI functionality. Any help is greatly appreciated.
-Sheela

"Belur" wrote in message
news:[email protected]..
> Can someone clarify if there is anything different that needs to be
> done while building a stand-alone application that includes VIs that
> use the MS agent voice VIs (for example MSagentTTS.llb) along with CGI
> VIs? I have been able to build applications with only CGI VIs but
> failed while adding MS agent VI functionality. Any help is greatly
> appreciated.
>
You'll need to install the Microsoft Agent parts on the target computer.
They are:
MSAgent.exe - the core components
actcnc.exe - MS Speech Recognition Engine
tv_enua.exe - MS Text To Speech engine
Merlin.exe - or any of the available different voices
Theses are available for downl
oad from
http://www.microsoft.com/msagent/downloads.htm

Error in XML form builder application

Hi SDN,
I have created a form builder application. I am able to create items from the application. But when i try to edit or delete the item...From the edit option if I try to save or preview or cancel or reset ....it is throwing the following error message
Runtime Error
An exception occured while processing the request.
Additional information: Exception during PageProcessorComponent.doContent()
Exception ID = a0d623c1-d35e-2b10-8ab7-f6c10479e59b
How to rectify the following issue....
Regards,
Ganesh N

Hi,
I have also encountered this problem the first time I did XML form builder.
A simple restart of my portal solved the problem.
Fabien.

Standards Recommendations for build applications

Hello, I'd like to know if there is some "Standards & Guidelines" document to build applications using HTMLDB. I know there are How-tos, etc, is there any document that explain or describes techniques or standards to build better applications?
Thanks!
Daniela

I found some interesting stuff here, besides the user's guide.
http://www.oracle.com/technology/products/database/htmldb/pdf/B14377_01.pdf
You can find the tutorials and how-tos here:
http://www.oracle.com/technology/products/database/htmldb/index.html
Bye,
Flavio

Build Application

Similar Messages

Maybe you are looking for