Installing 6.1 Application Builder

I'm trying to upgrade an installation of LV6.1 to use the application builder. The computer was already built and had NI MAX 3.1 and NIDAQ 6.x.x installed. When I do a custom install to select only the Application Builder, the 6.1 Installer indicates that I have a later version of MAX and NIDAQ, and that it will replace MAX and NIDAQ with older versions. I can't "unselect" this!
I don't want to change these; I've spent 3 months developing with the 3.1 and 6.x.x and can't afford to break my code now. How can I install the 6.1 App Builder WITHOUT touching MAX and NIDAQ?! Why does the LV Installer insist on replacing things that should not matter?!
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

The selector for the Drivers part of the tree is greyed out. I am unable to 'deselect' it.
I received a response from the LabVIEW community that indicated I should be able to place the LabVIEW CD in the drive and navigate to the AppBuilder subdirectory; then run the AppBuilder.MSI script.
This solution worked perfectly; with no prompts or worries about dependancies. I was then able to build and create a distribution copy of my code.
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Similar Messages

After installing an application that was created using the Application Builder

After installing an application that I created using the Application Builder I get this error if I try to run " ANY " LabVIEW App's that I have built. "Executable Version 7.1.1 doesn't match Resource File 7.1. Check your configuration."
The way that I tried to fix this is to reload LabVIEW 7.1 and DAQmx 8.0. I am using two NI-6528 switch cards.
After I reload LabVIEW and DAQmx I can run my applications but as soon as I install one on this development machine the error begins again.
The executable that I built works fine on the development machine and any other machine that I try it on but it appears that the Run-Time engine 7.1 becomes corrupt after I run setup.exe for the newly created application.
I have built numerous Installers, setup.exe's in the past without this error. Just this latest one caused this problem to start.
I can NOT upgrade to 7.1.1. I am doing work for many different sections of this factory and I can not force them to upgrade. I've asked. Others supply code for the same machines using LabVIEW 7.1.
I am stuck creating executables and manualing moving the correct files to the target machines.
What can be done?

No. The KB article was talking about a machine with 7.1.1 installed. I have LabVIEW 7.1 installed.
The machine that I am having trouble with is my development machine. LabVIEW 7.1, DAQmx 8.0.
If I build the executable all is fine. I can still run old executables including the one I just built.
If I create the installer all is fine. I can still run old executables including the one I just built.
When I install the app on my development machine the corruption occurs. I can " NOT " run old executables including the one I just built. The subject error pops up.
I have not moved any executables to the other machines yet. I don't want to corrupt others.

Can't find Application Builder after installing AB 7.0 in a LabView 7.1 system

Hello, I just installed applivcation Builder 7.0 on my windows desktop (XP, SP2) that has already installed a Labview 7.1. But nothing happens...I just can't find it. Not on "Werkzeuge" (Tools) or anywhere else in the application.
Only in the explorerI can find Labview7.0\Applibs...
I reinstalled it 3 times now...what else can I do ?
or does the Application Builder 7.0 not work with LV 7.1 ?
any help would be appreciated
regards
fluxgate

No, it does not work. You need the 7.1 app builder. If you had purchased the 7.0 app builder separately (and not as part of the profession version), when you did the upgrade to 7.1, you should have requested the 7.1 app builder. Since 7.1 is no longer sold by NI, I'm not sure how you can get the correct app builder. You should contact NI directly or your local field engineer.

Installer built with Application Builder gives error "Cannot install, higher version already installed"

I am having an issue with an installer which I created with the Application Builder. I have a project that I have successfully deployed. Subsequently I created another project (and vi) which is based on a copy of the originals, both with new file names. In the renamed project file, I changed all file names, paths, and all resources, to reflect the new names. I also changed the installer’s destination and install folders, of course. I reset the executable’s version number (in the Build Specification properties) to 1.0 (the original was 1.3). I then successfully built an executable and the application installer. However, when I run the installer (setup.exe), it gives a dialog (after the license screen) that it “Cannot install” because a “higher version already installed”.
I’ve done exactly the same thing with other vi’s and projects of mine, and never had this issue. The installer correctly installs the newly created (and renamed) version where it is told to in the project file. Also, I’ve never had a problem deploying (installing) on my development PC either.
I have carefully checked and rechecked to make sure there is no reference to the original executable or paths. What could be causing this behavior? I want to keep the two projects completely separate, so simply changing the version to higher than 1.3 is not an acceptable solution.
Thanks to anyone in advance for any help and suggestions.
Ed

Yes, LV 8.5 does NOT give me control over the GUID. In the project file there are three such strings:
"App_applicationGUID"
"App_INI_aliasGUID"
"App_INI_GUID"
They all have different numbers and none of them match the GUID or PackageGUID in setup.ini. I don't know if they are related or not, but usually it's not a good idea to mess with (manually edit) files like these (project, ini, etc.) unless you know what you are doing. (For example, I do edit the setup.ini file to change some of the [Dialogs] parameters, but that is based on direction from NI support.)
Anyway, like I said, I've made copies of projects before and never ran into this problem. At least I have a solution, however laborious, in creating a new project file from scratch.
Let me know if anyone has more thoughts on this.
Ed

Build dll error in application builder 8.6.1

Hello,
I get always an error in the LV 8.6 application builder, when I build a dll. There is only one function in it, that has a string and an error input, and nothing else. I attach a screenshot of the VI prototype, and hier is the error description:
Error 1 occurred at Building DLL.
A component needed for Application Builder does not support the required functionality. This might have been caused by installing an older version of LabVIEW after this version was installed. Reinstall the current LabVIEW version to correct this issue.
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
After that I reinstalled LV8.6, I tried to reinstall only the 8.6 app builder, but no success.

Hello,
thank you for the reply.
I have solved the problem. I uninstalled the last installed LV version, this was 8.0. Then ran appbuilder again in 8.6, then I have got an instruction to run applibs\lvdllbuilder\lvdb.exe. Since then works.
regards
Mitulatbati

Error 7 occurred at Open VI Reference with Application Builder

Using Labview 5.1, I am building an application where all the vi's are placed in a single .LLB file. I have one top level vi (with sub-vi's), and one vi that is opened by the Open VI command. The program runs fine with labview installed. I want to make an executable file. I select the top level vi and select the vi that is opened by the Open VI command as a dynamically loaded file. I get an error when I attempt to build the file.
"Error 7 occured at Open VI Reference in Dist Build LLB Image.vi -> Dist Build App Image.vi -> Build application.vi"

Dear Sir;
There are two things that are good to try:
First, create the application in a folder that is closer to the root directory (e.g., c:\myApp). There is a limit to the length (or depth) of the path name to your application's target directory, so, if you are choosing a too long path you might get an error.
Second: The Application Builder reads certain information from the VI in order to determine how to build the executable. To avoid possible errors, either in the build process or in the built executable, make sure the VIs are LabVIEW 5.1 VIs. You can convert your VIs to LabVIEW 5.1 VIs by using the Mass Compile feature (File >> Mass Compile) in LabVIEW before you build your executable. The Mass Compile feature will allow you to select either a directory or a LabVIEW
.llb file to compile.
Regards

Application Builder for labVIEW 7 Doesn't support any report generation function

I'm Using LabVIEW 7.0 to build an application My Application is exporting data to an excel report. the vis were working great until i tried to creat an .EXE file. The application is working fine but when i try to generate the report nothing happens.
So, I decided to test the report generation functions alone (New Report.vi, Append report text.vi and Dispose Report.vi). The Problem Still there, the .EXE file takes no action when i attend to generate a report. any suggetions please.

Shady Yehia wrote:
> I'm Using LabVIEW 7.0 to build an application My Application is
> exporting data to an excel report. the vis were working great until i
> tried to creat an .EXE file. The application is working fine but when
> i try to generate the report nothing happens.
>
> So, I decided to test the report generation functions alone (New
> Report.vi, Append report text.vi and Dispose Report.vi). The Problem
> Still there, the .EXE file takes no action when i attend to generate a
> report. any suggetions please.
Another possible reason besides of possible path problems: Are you
running that application on the same computer? If not you need not only
to install the Runtime-Engine (automatic when you create an installer)
but also the Report Active X support.
To include that into the installer
you go into the Installer Settings Tab, then press the Advanced button
and make sure that you check the NI Reports Support checkbox before
creating an application build.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

I have a application build in labview 8.5 for Windows XP using NI Visa functions to interact with hardware , how to make is work in Windows 7 32 bit and Win 7 64 bit

I have a application build in Labview 8.5 which wroks fine with Windows XP , this program uses basic read /write functions of NI Visa to communicate with Hardware . This application doesnt work with Windows 7 32 bit/64 and Vista . What changes i need to do to make it work for the said operating system

srinivas wrote:
Sorry for confusion ,
My question is what changes i need to do in code or while making the installer to make the existing program work with other Windows operating system
You need to make sure the machine have the corresponding NI-VISA installed. Check in the NI software pages for the right version.
Also make sure that the com port's can be selected when you first start the application. Eg. if you refer to VISA "COM1" on the XP machine It might be "COM2" on the Win7 machine.
Br,
/Roger

Several question s about runtime Engine, application builder and labview player

I am a little confused by all the options to distribute a program.
Please help bij answering (one of) the following questions:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
3. What is the advantage of the labview player above the runtime Engine?
All questions refer to the latest software versions of NI software
Thanks in advance,
Regards,
Ferry

ferry1979 wrote:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
(In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
(Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
No. See above.
3. What is the advantage of the labview player above the runtime Engine?
The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
Message Edited by altenbach on 08-21-2005 10:05 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
runtime.png ‏24 KB

Link error during install of O9i Application server

Hi there.
I have a problem when installing Oracle 9i Application Server rel. 1.0.2.2.0 on SuSE 7.3.
During installation phase "Linking Oracle 9i Application Server rel. 1.0.2.2.0", I get: "Error invoking target install of makefile /
opt/oracle/product/9.0.1/icache/lib/ins_icache.mk"
The make.log states:
building Oracle8i Cache Management Engine
gcc -o /opt/oracle/product/9.0.1/bin/wtcme -L/opt/oracle/product/9.0.1/icache/lib/ -L/opt/oracle/product/9.0.1/lib/ /opt/oracle/pro
duct/9.0.1/icache/lib/wtemain.o /opt/oracle/product/9.0.1/icache/lib/libicache.a /opt/oracle/product/9.0.1/lib/libwtc8.a /opt/oracle
/product/9.0.1/icache/lib/libxml8.a \
-lclntsh /opt/oracle/product/9.0.1/rdbms/lib/kpuadef.o `cat /opt/oracle/product/9.0.1/lib/ldflags` -lnsgr8 -lnzjs8 -ln8
-lnl8 -lnro8 `cat /opt/oracle/product/9.0.1/lib/ldflags` -lnsgr8 -lnzjs8 -ln8 -lnl8 -lclient8 -lvsn8 -lwtc8 -lcommon8 -lgeneri
c8 -lwtc8 -lmm -lnls8 -lcore8 -lnls8 -lcore8 -lnls8 `cat /opt/oracle/product/9.0.1/lib/ldflags` -lnsgr8 -lnzjs8 -ln8 -lnl8 -ln
ro8 `cat /opt/oracle/product/9.0.1/lib/ldflags` -lnsgr8 -lnzjs8 -ln8 -lnl8 -lclient8 -lvsn8 -lwtc8 -lcommon8 -lgeneric8 -ltrac
e8 -lnls8 -lcore8 -lnls8 -lcore8 -lnls8 -lclient8 -lvsn8 -lwtc8 -lcommon8 -lgeneric8 -lnls8 -lcore8 -lnls8 -lcore8 -lnls8 `ca
t /opt/oracle/product/9.0.1/lib/sysliblist` -ldl -lm \
-lpthread -lc
gcc: /opt/oracle/product/9.0.1/rdbms/lib/kpuadef.o: No such file or directory
make: *** [opt/oracle/product/9.0.1/bin/wtcme] Error 1
I had a similar problem when installing the database server software. This was fixed by editing the LD_SELF_CONTAINED parameter in
genclntsh. This, however, does not help in this case.
Kind regards,
Roald Andresen

Hi Melchor,
Please follow SAP Note 1618816 - Permanent or Temporary License Already Exists In Systemcopy
If possible please share files saplikey.log, dev_slic
Regards,
Gaurav

For PDF Printing in Application Builder 3.0.1

Hi,
Recently upgraded to Application Builder 3.0.1.00.08
I've created a report, which i want to open as a pdf. I downloaded
bipublisher_windows_x86_101332_disk1 zip file and installed as per the
link mentioned under.
http://www.oracle.com/technology/products/database/application_express/
html/configure_printing.html
But while checking with from start menu and selected BI Publisher
server from the windows, the login screen is not appearing. where to
check.
http://mycomputername:9704/xmlpserver
is this correct. or instead of mycomputername what i've to give?? any
idea?
Thanks and Regards,
Sudha.

Kevin,
That's because report queries are rendered by a different engine than report regions. In report regions we escape correctly, and for report queries, we escape % with %25; - so we'll have to remove the semicolon.
Thanks for pointing this out,
Marc

Application Builder and Corrupt VIs

Howdy All,
I'm developing a Medium-sized application in LabVIEW 7.0 used for instrument control. This application has grown over-time, and currently contains approximately 400 VIs. The basic structure of hte appliation is one main VI that has an instrument status display on the bottom, and a sub-panel on the top, into which all dialogs are loaded for user interaction. Each major task has it's own VI that is loaded into the subpanel as appropriate.
I've read a few stories on the developer exchange about VIs becoming corrupt. I thought these were freak occurences, because by and large, it appears that LabVIEW is fairly stable. However last week I had a VERY scary experience.
I was demonstrating to a collegue the properties of an XY graph control. We changed the colour of one of the plots, then hit cancel. LabVIEW complained of an internal error involving undo.cpp and proceeded to crash. I figured the crash was caused by some strange sequence of events, didn't think much of it, and reloaded my application. After making some changes, I went to the Application Builder to build the application. However the application Builder was complaining about a "missing board" in the DEFAULT build file. I knew immediately that something was VERY wrong. (When I say default build script, I'm referring the default script that is loaded when you press the "Build application or shared library..." button in the tools menu).
(As a side note, does anyone know why the LabVIEW application builder gives such terrible error messages? I always get that "missing board" error when either: one of my support files cannot be found, or one of my dynamic VIs is not executable. Since the error doesn't pinpoint a file, I neeed to go through the files one by one - which is a pain because I have a lot. Another question, why does the application builder ALWAYs ask if you want to save changes to build script, even if you haven't made any changes?)
After loading my build script for the application (which I've used HUNDREDS of times), I got the "missing board" error. I didn't think there was a problem with any of my paths or VIs, but I went throgh each included support file and dynamic VI in the build script to make sure it was there. Though there seemed to be no problems with any of the files, LabVIEW continued to complain.
I figured the problem was specific to the computer I was working on, so I copied the source to another development machine to complete the build. I was VERY scared to find that I got the SAME error on the DEFAULT build script! Also, my actual build script refused to load properly.
This was late at the end of a long day, so I decided to turn of my machines and go home. The next morning, everything worked fine - I was able to build the application, and I haven't had a problem since. (Maybe it was a bad dream, but I have clumps of hair on my desk from the night before...)
I found this experience to be UTTERLY TERRIFYING. Once I had to revert to an archived copy of one of my main VIs, because the current version refused to open, claiming it was corrupt. Since I don't know what's going on behind the scenes in LabVIEW, I'm afraid that tiny internal LabVIEW errors might be adding up. I back-up the source very regularily, since it is such a large project, however I have *real* way of inspecting the integrity of the source.
Does anyone know (A) why this might have happened - especially when the problem reproduced itself on multiple machines (B) has anyone had similar experience with internal LabVIEW errors or corrupt source (C) what sort of internal errors might be piling up that might cause a VI to claim it is "corrupt".
All input is appreciated.
WG

Hi Robert,
For the undo.cpp error, I got a couple different line numbers but didn't write them down. If I get them again, I'll be sure to get the specifics for you.
As for the "missing board", I also got that description a little wrong - the error I'm talking about is:
"Error 7 occured at Inovke Node in Dist read linkages.vi->Dist Cmp Settings to Disk Hier.vi->Build Application.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 hte operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Unix.
NI-488: Non-existent board."
As you can see, I meant "non-existent board". This error is very easy to reproduce - m
ake a build script and include some extra files. Save and close the build script. Move or rename some of the extra files included in the build. Reload the script. You should get that not very helpful error.
Now that I think about it though, maybe that NI-488 error refers to GPIB control, which I think I have installed, but don't have a GPIB card installed... hmmm... no reason that error should be popping up *there* though...
I could have *sworn* I would also get that error when one of the dynamic VIs in the build is not executable, but I can't seem to reproduce that right now.
Tying back to the original thread - what makes a VI corrupt? I imagine if you cracked the binary file open yourself and messed around with some bits you would probably make the VI corrupt, but I'm assuming that editing a VI normally (ie through LabVIEW) should NOT cause the VIs to become corrupted. Any information on VIs becoming corrupt? Is it somehow related to the undo.cpp errors?(when trying t
o undo some last change that wasn't recorded properly, the VI is modified improperly - after you save and close, it won't reopen?)
Victrick

Application builder exe does not load excel

I have used application property node and invoke node to cerate a set of VIs that read and write data to an Excel sperad sheet. This works fine in when running in LabVIEW, however when I run myApp.exe as build from application builder, the data does not get logged to Excel. The file dialog appears to open the XL Spreadsheet but not data gets logged nor is any error reported?
What is going on? All the VI are in the same project folder? Is there some additional addon run-time the must be installed on the target machine? I am uisng LabVIEW 2012 on the development station with Win7 Pro and Office 2010 on both the devleopment station and the target system. Is there one document that describes using Application Builder? It was not clear that I needed both LabVIEW and VISA run-time engines to get my application.exe to run on the target. Is there something simialr I must do to get Office to work as well?

I was finally able to track this back through by starting from scratch and received an error code, which led me to this post:
https://forums.ni.com/t5/LabVIEW/Error-2147319779-Excel-ActiveX-and-Broken-LabVIEW-Icon/td-p/2354776
Deleting the "1.7" items solved the problem.

"file already exists in the destination" during application build

I am trying to build an executable and have gotten the following error:
The file already exists in the destination.
C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\Sentech LV 82\Shared Library - Trigger SDK\StTrgApi.dll
WHen I start the build I go to "Build Executable" then click "Build"
The VI for the project I have open is the Startup VI and I do not list any Dynamic VIs or Support FIles.
I am using Labview 8.2
I installed a user library for a USB camera from Sentech wich I am using and it works fine in Labview 8.2
When I try to do the build I get the error shown above. The file it is referencing is there along with the .lvlib file.
I tried removing the file shown in the error message to see what would happen and I continue to get the same error even though the file is not there. I even restarted LV and still got the same error.
I am new to the application builder (v7 ?) and have not been able to find any good tutorials. Does anyone have any ideas on this error or a good place to learn more about app builder.
Thanks
Keith

I am new to the application builder (v7 ?) and have not been able to find any good tutorials. Does anyone have any ideas on this error or a good place to learn more about app builder.
Thanks
Keith
Hi Keith,
you can check this Link out for a tutorial on app builder.
Regards,
Denver

Is it possible to embed DAQmx in Installer(created by Application Builder)?

The good thing of Installer (created by application Builder) is that it also integrates LabView Runtime Engine along with supports like Serial port support, Port I/O support etc. Due to which one can install the application developed by Labview on any system wheather that contains Labview or not, as the engine required by that application also gets installed.
But problem with my application is that it uses DAQmx related stuff, so I have to install DAQmx 8.0 prior to running my application installer on any system. Is it possible that the DAQmx related stuff required by my application also gets install through same installer as it installs LabView Runtime Engine, so that the distribution of my application donot require the complete installation of DAQmx.

You need to use LV 8.0. You can add NIDAQ to your installer in LV 8.0. In previous versions I do not think it is possible.
see: http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Matt
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

Installing 6.1 Application Builder

Similar Messages

Maybe you are looking for