LV8 Application builder/ installer questions

I am having trouble in building my installers within LV8. Everything is in the Project Manager and I am able to build an Executable that works. but when I build an installer and try to run the installer on a 2000 or XP machine I get the attached error. I found if I continue on the error everything gets installed ecept my application. If I manually install my application everything works. so with the RTE on a system without LV8 installed my EXE works.
I cannot figure out exactly what I am doing wrong. I am thinking it could be on the  Registry tab of the installer as I did not adde or change anything. the PDF CD I received with LV8 talks about the App Builder from 7.1 which does not help. The program I am working on building worked fine in 7.1.1. Source files look to be done correctly and I check marked the Register COM ont he source files settings page as I am using ActiveX to access Excel.  It is configured to install RTE 8.0, I have the Shortcuts set as well, but on a NON Dev machine (no LV8) the installer does not work. but on my Dev machine it seems to work fine.
Any ideas?
Message Edited by jdebuhr on 01-09-2006 09:47 AM
Jeff D.
OS: Win 7 Ultimate
LabVIEW Version: 2011,2010,2009 installed
Certified LabVIEW Architect
Attachments:
LV8_installer_error.JPG ‏18 KB

I think I got it working.. I deleted the old files int he destination for the build and tried again. I left the ActiveX Server unchecked and verified the Register COM was checked. created a new installer and built it and is seems to work.
Jeff D.
OS: Win 7 Ultimate
LabVIEW Version: 2011,2010,2009 installed
Certified LabVIEW Architect

Similar Messages

  • USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

    Hello all,
    I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
    What has happened  is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
    On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
    I've installed on different computers (without previous labview installs) with the installer. They all worked.
    The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
    They say the COM ports aren't even showing up when they run the installed application.
    So, I'm not sure where to start. Is this a driver issue?  Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
    I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
    Thank you in advance,
    cayenne

    The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
    Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • LV8 Application Builder Folder Structure

    I have a folder structure in my development environment.
    When I build an application, using the application builder, I want to get the same folder structure.
    Example:
    I have folders ..Application\Drivers\DMM\Agilent 34401 and ..Application\Drivers\DMM\Fluke 45.
    There are subfolders containing VI:s in each folder (..Application\Drivers\DMM\Agilent 34401\Subs\sub.vi)
    In the application builder I add ..Application\Drivers to "Dynamic VIs and Support Files".
    I create a new "Destination".
    Now all vi:s from ..Application\Drivers goes to this folder, not to subfolders.
    Is it possible to get a folder structure?
    Staffan Ekstrom
    Sony Ericsson Mobile Communications AB
    Lund, Sweden

    Hi Staffan,
    When you build an application all of the VI:s will be integrated in an .exe file. The reason for this is that the user of your program not shall be able to do changes in the source code.
    When adding files to the "Dynamic VIs and Support Files" these files are for example help files that you want the program to find no matter where you install your program on the computer. Before adding files to this you need to build the relative path in the program using strip path.vi and build path.vi.
    Dynamic VI:s are not the same as sub VI:s.
    The short answer to your question is no, there is not possible to get a file and folder structure when building an application.
    Regards,
    Andreas E
    Applications Engineer
    National Instruments

  • "Find Resources" does not work after Application Builder Installer

    I use Lv Full 6.1 / Appl.Builder 6.1
    VISA:"Find Resources" acts properly as long as a built application is installed on a PC that has LV installed.
    as soon as only the runtime eng. is installed no resources are found.
    Who helps?

    Thank you Dennis for your reply. I tried to install the VISA runtime engine via the "Run executable after installation" but it appears to run the Visa-runtime-engine-installer before ending the application installation. So I had to run that installer manually. Nevertheless you pushed me in the right direction.
    THANKS

  • Application Builder - Installer - Missing Files

    Hello,
    I have a very large project and I want to create an installer. I have prebuilded the exe and all the necessary files and added them to the new project as files.
    Somehow, when I want to create a new installer, I can not see my exe files (added to LVProject as files) in the Source Files Tab.
    I have tried to remove and add these file again to the project, but nothing happened.
    I have a feeling about that when I double click on the Installer icon in the LVProject - Build Specification to open Installer settings the filelist do not refresh. Is it possible to fore refresh that files?
    This issue is very annoying...
    Please give some help, thanks.
    +++ In God we believe, in Trance we Trust +++
    [Hungary]

    To build an installer from with a project you must add the Build Specification, not the executable itself. Therefore you need to create the Installer in the same Project as the Build Specification. You cannot manually add executable files to the Installer, just Build Specifications that define your built executable.
    See the Installer help: http://zone.ni.com/reference/en-XX/help/371361J-01/lvdialog/files_install_page/
    Thoric (CLA, CLED, CTD and LabVIEW Champion)

  • Automatic creation of desktop icon using application builder installer

    Can app builder create and installer where a desktop icon is automatically placed on the desktop?

    Hi ATS-MN
    With LabVIEW 8 you can create a shortcut on the desktop.  In the new Installer Builder, there is a category for shortcuts and you can specify the executable and the desktop folder here.  In previous version of LabVIEW, you were not able to have an installer create desktop shortcuts.
    Hope this helps!
    Megan B.
    National Instruments.

  • Including a Pre-Built LLB in Application Builder 8.X

    I have just recently updated some old code to 8.5.1. This code contains many dynamic calls to VIs located in pre-built LLBs (LLBs that were saved prior to application builder). This application is also compatible with a priority plug-in architecture. So when creating an application or installer in app builder 8.X, how does one include a LLB file? I do not wish to build it. I just want to include it the same way you may include a text file or someother type of source file. LLB files do not show up as individual files in the Project Manager.

    AstroGlen wrote: 
     I would like to create an installer that uninstalls the previous version of software (which was written in 7.1.1). I am assuming it is necessary to make edits to the "registry" category in the installer properties. I am also assuming that I would need to enter the product code for my application. This is the code found in the 7.1.1 application builder \ installer settings \ Properties button. But i do not know the particulars of what needs to be done.
    I think when you install an application created/built using a higher version of LV, it ll automatically overwrite any previous version(s) of that application installed in the target PC. We may not need it to be uninstalled manually. Did you try this?
    - Partha
    LabVIEW - Wires that catch bugs!

  • How to add visa usb support to the application builder?

    Is it possible to add VISA USB drivers to the application installer?
    www.xinstruments.com
    Custom Software for Industrial Automation
    www.hdrconverter.com
    Picture processing made easy

    I'm afraid you can't do that. The LabVIEW 7.0 application builder only supports adding the VISA serial port driver to the application builder installer.
    You will have to install the VISA support for USB separately by using the VISA 3.0 runtime installer.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Application builder priority

    When I run the application builder, to build my labview program into an exe, it pretty much takes up 100% of the usage of my computer. Since it takes about 10 minutes to compile that's down time for me. Is there any setting, within labview, that I can make that would reduce the priority a bit for the application builder so that it can run in the background while still allowing me to work effectively on my computer?

    AstroGlen wrote: 
     I would like to create an installer that uninstalls the previous version of software (which was written in 7.1.1). I am assuming it is necessary to make edits to the "registry" category in the installer properties. I am also assuming that I would need to enter the product code for my application. This is the code found in the 7.1.1 application builder \ installer settings \ Properties button. But i do not know the particulars of what needs to be done.
    I think when you install an application created/built using a higher version of LV, it ll automatically overwrite any previous version(s) of that application installed in the target PC. We may not need it to be uninstalled manually. Did you try this?
    - Partha
    LabVIEW - Wires that catch bugs!

  • Application Build Error

    When I try to build my application I get the following error: Error 26096 occurred at BuildApplication.vi>>DistCallCreateInstaller.vi>>WinInstallCreate.vi>>WinInstallAddMergeModules.vi>>MSIDKLoadMergeModules.vi C:\Program Files\National Instruments\LabVIEW 6.1\applibs\distkit\redist\Modules\ActiveXContainer.Msm
    Possible Reasons:
    NMDK_AMM_UNSPECIFIED_MERGE_ERROR

    Hi
    This behaviour can happen when installing Visual Studio .Net or ORCA because they install a newer mergemod.dll which isn't compatible with the older version that LV 6.1 uses in the Application Builder installer.
    This steps should help:
    1. Open a command prompt.
    2. Change to the "\Program Files\Common Files\Microsoft Shared\MSI Tools" directory.
    3. Execute the following command: "regsvr32 /u mergemod.dll". This should report that the unregister was successful.
    4. Change to the "\Program Files\National Instruments\shared\Installer" directory.
    5. Execute the following command: "regsvr32 mergemod.dll". This should report that the register was successful.
    Hope this helps
    Luca
    Regards,
    Luca

  • Build Installer LV8.0 - is this real??

    Hi all
    I recently received LV8.0. After playing around and test some new features, I wanted to start to bring all testrigs that run under LV to LV8.0. Therefore I chose one of them, made a LV-project, modified the source code, created a application build script and an installer build script. I run the application build script without any problems. OK - everything's fine up to now. But as I wanted to create an installer, it obviously just creates a lot of "nonsense".
    I checked some additional installers (Datasocket, LV8.0 runtime engine, MAX 4.0, Fieldpoint, Scope and VISA) to make just one Installer, which would be very nice to handle. When checking NI Datasocket, I saw in the distribution title on the right side (see attachment) LabVIEW 8.0 Real-Time Module. Why???? There is no need to include the rt-module, as I don't use it.
    I thought "ok, maybe a wrong string displayed - let's create the installer" and run the build script. While running it asked me for the device driver cd's (ok - could be logical) and out of a sudden it also asked me for the cd of the LV realtime module. Well - I inserted it an continued the build.
    In the end I got a directory structure (Volume/bin/lotsOf"pXX") with a size around 650 MB - for a simple application of approximatly 10MB.
    When I browse some of these "pXX" directories I discover subdirectories like "p14/LV711RTE", "p15/LVBrokerAux71" and lots of different msi-files (for instance "NIRegistrationWizard.msi" - but why?).
    Is there anyone out there who can help me quickly?
    Thomas
    Using LV8.0
    Don't be afraid to rate a good answer...
    Attachments:
    Installer.JPG ‏167 KB

    Thomas,
    Thanks, I too have been waiting for us to have the ability to build installers that include all the drivers and related software you need. There was a lot of work that went into it by a team of people here at NI. Their work is being used in LabVIEW, CVI and TestStand now for generating such installers. I'll pass along your complements to the people involved.
    So you unchecked DataSocket yet your DataSocket communications are still working? I think that might be due to DataSocket being included through one of the other installers. When you check an item we'll include all the dependencies that you need. Most of the time those dependencies don't show up in the list of additional installers, because they are lower level drivers and software you don't interact with directly and don't need to know about. Some of the items that are dependencies for other installers do appear in the list such as DataSocket, LabVIEW Run-Time Engine and MAX. FieldPoint for instance is dependent on MAX and will include it if you are including FieldPoint. If you check MAX too, the Installer Builder will only include one copy of MAX. I'm not sure which of the other items is dependent on DataSocket but it could be getting included that way. Another possibility is some older LabVIEW Run-Time Engines are being included in your installer because of MAX and they include an older version of DataSocket as part of their installer not as a dependency so it could get included that way, but that would be an older version of DataSocket and not what you are using on your development machine. Since you know you are using DataSocket I recommend checking it, so you know the version you are using will get included.
    When you uninstalled LabVIEW Real-Time, the core portion of LabVIEW Real-Time was removed, however any dependencies it had that are also a dependency of another NI Installer would not be removed. As I mentioned earlier LabVIEW 8.0 installed DataSocket and the Real-Time Installer upgraded it. The installers have the necessary logic to know that just because RT installed a newer DataSocket we cannot remove it with RT because LabVIEW depends on it as well. When you ran the RT installer the progress bar probably showed installing part X of Y, and when you uninstalled it there was also a progress bar that showed removing part X of Z. Where Z is a smaller number than Y because some dependencies of other products were updated and they can't be removed until all the installers that need them are removed.
    So the next question is "I want to rebuild this installer without having to put the CD in. How can I do that?" The ideal answer would be for us to have a check box on the dialog when you are prompted for the distribution that says something about copying the necessary files to your hard drive and you could choose to uncheck it. We didn't get around to putting that in for LabVIEW 8.0 but if you happen to use CVI you'll notice they have such a check box and as I said we use the same installer building technology so it wouldn't be unreasonable to see that in the future for LabVIEW . But what can you do right now?
    One options would be to always copy your CDs over to the hard drive before you install them and leave the installers on your hard drive, that way the last place they were installed from was somewhere on you hard drive that can be found without user interaction. We don't do that by default since copying the LabVIEW CD(s)plus the driver CDs would really use up your free space. This is messy though because you have to uninstall everything and reinstall it.
    Another option is to copy the distribution you are being prompted for (the entire disc) to your hard drive and then in the Installer Builder select NI DataSocket and change the Installer location path to the location you copied it to (the top level folder that has a nidist.id file in it). The press OK on the dialog, now the Installer Builder will look in that location for NI DataSocket, until a newer version is installed. We have had some problems with this mechanism not getting all the dependencies from the new location, so it isn't a 100% solution, but I just tried it for DataSocket and it worked.
    The first option will catch 100% of the dependencies, where as the second option unfortunately won't.
    Kennon

  • Application builder questions

    Hi,
    I have an application that I want to make a stand-alone executable. I have installed application builder and almost got it the way I want.
    I first create an application, which works fine. But I have some questions regarding the installer.
    1. I want the installer to be as small as possible.
    2. I want the application.exe file included in the same directory as the setup.exe file.
    3. Which additional installers do I have to include? My application communicates with a module by using Modbus libraries (VISA). Do I need LV realtime and VISA runtime or others?
    BTW. I use LV 8.0
    -Christian

    Hi Christian
    I also had some questions concerning the application builder.
    Just have a look at the thread I started - maybe you find some informations helpful to you.
    http://forums.ni.com/ni/board/message?board.id=170&message.id=164285&view=by_date_ascending&page=1
    Thomas
    Using LV8.0
    Don't be afraid to rate a good answer...

  • 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

  • Scripted Build of Host and RT application and installer

    Looking to make a script that allows me to create the host application from a project template. But I need it to change some of the values in the project such as file paths, files included in the installer and names of the build exe and rtexe.  I cant find the way that I can  programtally control that thing based on user input.  
    This is something I am doing so our developer team can be more consistant about how we compile updates and how they are distribuited to the customer.  
    Solved!
    Go to Solution.

    As for(imstuck) has said, all of what you want to do is possible, but it is spread out over two APIs - the VI server API (property and method nodes) and the application builder API, which is not on the palettes, but can be found in <vi.lib>\AppBuilder\AB_API.
    For working with projects, you can get project references through the Application class, then move on to project items, etc.  You can use the class browser (Ctl-Shift-B) to find things.
    AppBuilder has several APIs, depending upon what your final target is (source code, executable, packed library, etc.).  Use the appropriate one.
    I would strongly recommend you do not directly touch the project file.  It can contain binary information and has a lot of interdependencies.  You may be successful, but your solution will probably be brittle, since the project format can and does change with the LabVIEW version.
    If you have any more specific questions, let us know.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • Projects, application builder LV7/LV8

    I realize that this is a general question so I'm hoping someone can just point me in the right direction.
    I have been using LV8, but recently had to work on a cRIO application that was written in LV7. I was able to make the necessary changes and solve the problem but there were a few things that left me confused.
    The LV7 application was as follows:
    an FPGA program
    a RT program
    some windows .exe program that, when run, would download all the appropriate programs into the cRIO and run it.
    In order to make changes to any of the programs, and have those changes "stick", I had to run the Application builder. Fortunately the previous developer left a profile that I could load, and everything worked, but before I found out about this, I struggled with getting the application builder to correctly assemble all the necessary files.
    My question is, does there exist a tutorial on using the application builder? Does it include writing an application that will find the RT VI, the FPGA VI, and put them in correctly?
    I am familiar with LV8 and I understand how to have the VIs loaded automatically (stored on the cRIO). I'm just not familiar with LV7.
    Just looking for pointers and tips on using the application builder I guess.
    Thanks
    Jeff

    Jeff,
    Here are a few links that should help you out.
    Creating Executables with the LabVIEW Application Builder - This is a general overview of the Application Builder (version 6.0 and 7.0)
    http://zone.ni.com/devzone/conceptd.nsf/webmain/4ef810ee05bef63c86256bf30062ec31
    Deploying and Launching a Real-Time Application - This is more specific to deploying a real time application
    http://zone.ni.com/devzone/conceptd.nsf/webmain/9ac4955881bd7b4d86256d0b0061dd1c
    Hope this helps,
    Justin D.
    National Instruments

Maybe you are looking for

  • Field separator in TEXT_CONVERT_TO_XLS_SAP

    Hi all what is the purpose of field separator in FM TEXT_CONVERT_TO_XLS_SAP.what are the possible values to be given for that field separator??????? what values do i have to give for tab limited points will be rewarded

  • Cancel customer down payment

    Dear Experts, Can you help me with the below issue, I have created a downpayment request through VF01 mistakenly , Now I wanted to cancel it, could you please let me know what I need to do 1.This DP request was created as a noted item now, 2.I cannot

  • Convertion of Smart form to pdf and sending mail to vendor for PO

    Hello all, I have modified a standard PO Smartform and running it through ME23N. In this i have to convert it to a pdf file and then send it through mail to the vendor. I have found out FMs'CONVERT_OTF'and 'SO_NEW_DOCUMENT_ATT_SEND_API1' to convert i

  • Web gallery control not visible

    HI <br /> <br />Viewing through the downloadable resources for the Flash Web Gallery templates I saw that there is the possibility of having Play/Stop/Forward/Backward/...-Controls in the lower right corner of the Flash Gallery. How can I make them v

  • Mailbox very tiny - how to enlarge?

    I installed Thunderbird on my 27inch iMac. I find the lettertype in the program itself much to tiny. Changing te font size through the normal menu's only enlarges the font size in de emails but nog the headers, the titels of the email etc. Can anybod