Application Builder: Additional Installers Source Location

I am having trouble creating an installer for my application. I can build the installer when I only inculde the NI LabVIEW Run-Time Engine, but I also need NI-FieldPoint for LabVIEW Real-Time and NI-VISA Runtime. When I try to include these I run into problems.
I think the problem is that I installed some of these from the discs, but now my company has an installer on the network that I have used as well, so now I don't have the discs. Is there a way to change the Installer Source Location in the Installer Properties? When I try to build the installer I am asked if I have the discs, but I do not. I want to be able to get the installers from my company's network or maybe I can download them from ni.com and have them on my computer, but I need to know how to change the Installer Source Location.
I reinstalled NI-VISA Runtime from my company's network and the Installer Source Location changed to the network location (which is what I thought I wanted), but it still asks for CDs and if I click throught I get the following errors:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
*** Error: An internal error occurred for which the cause is unknown. (Error code -41)
*** End Error Report
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'NI-VISA Runtime 4.5' from: \\aerolabview\LabVIEW\LabVIEW 2009\DriverDVD\Products\NI-VISA_Runtime\ to: C:\PPG\installer\PPG\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** End Error Report
Done building deployment

Hi Bob,
My most recent attempt gave me this error immediately after clicking Yes on the Distribution Needed window. I was never prompter for anything after clicking Yes:
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
*** Abort requested.
Done building deployment
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'FieldPoint 6.0.1' from: C:\Documents and Settings\Administrator\Desktop\FIELDPOINT_601_20080201_final\ to: C:\PPG\installer\PPG\
Copying distribution 'NI-VISA Runtime 4.5' from: \\aerolabview\LabVIEW\LabVIEW 2009\DriverDVD\Products\NI-VISA_Runtime\ to: C:\PPG\installer\PPG\
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.
*** End Error Report
Done building deployment
When I build the application, I get a lvapp.lib.tmp file in the temp directory, but I get no new temp files when I try to build the installer.
I would also like to point out that if if I uncheck FieldPoint 6.0.1 from the Additional Installers, and select either FieldPoint 6.0 or FieldPoint 6.0.3 (which are other optiions that show up in the list), I still get the same error as above that references 6.0.1
-Chris

Similar Messages

Application builder (using OpenG source)

I just made a LV program and executable thing in LV8.2.0.
Only one function (for converting cluster->ini) from OpenG was used to make the program easily.
When I copy the program folder, so many OpenG (maybe related to the converting routine) codes were created in subVI folder.
My question is,
1. In distributing source code, Is there some DLL or convenient format file for OpenG not to copy many Vis?
2. In making executable program by NI-application builder, how to treat the OpenG library if I have only one Vi ?
And as other question,
3. In NI buidler, the external libraries (run-time/DAQ/VISA) may be rather big.
How can I make the whole program( application+libraries installer) as small as possible?

labmaster wrote:
1. In distributing source code, Is there some DLL or convenient format file for OpenG not to copy many Vis?
2. In making executable program by NI-application builder, how to treat the OpenG library if I have only one Vi ?
And as other question,
3. In NI buidler, the external libraries (run-time/DAQ/VISA) may be rather big.
How can I make the whole program( application+libraries installer) as small as possible?
3: The DAQmx installer has several versions the smallest being 40 MB? and the largest 150 or something.
I think the VISA installer has the same options.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

During an application build I received an error 7 for a missing source NI vi 1d linear evaluation.vi

During an application build, I got "Error 7 occurred at c:\Program Files\National Instruments\LabVIEW 6\vi.lib\Analysis\8numerc.llb\1D Linear Evaluation.vi - source does not exist".
This existed in Labview 5.1.1. Was it deleted in 6.0?

No, this VI is in the following location "Functions >> Analyze >> Mathematics >> Array Operations>>1D Linear Evaluation.vi"
Perhapse this in a package (Advanced Analysis) that is not included in your version of LabVIEW. You may need to upgrade to get these VIs, or you can copy them over from your Labview 5.1.1 installation.
-Jim

Installing NI-RIO with Additional Installers in Applicaion Builder

Is it possible to install NI-RIO device drivers in a stand-alone
installer created from the application builder in Labview 8.2? I can't
seem to find NI-RIO as an option in the Additional Installers page when
building an installer. My target systems is a PC running Windows XP
SP2 with a PCI-7833R.
What are the steps to installing a built Labview 8.2 application that
uses a PCI-7833R with the application builder? Do I have to run the
NI-RIO installer separately from my application installer? Can I
install NI-RIO from the command line with the option of a silent
install like NI-DAQ (see this link)?

I installed NI-RIO v2.1 with the /q option from a command prompt like this:
setup.exe /q /AcceptLicenses yes
It took a while but it worked. NI-RIO v2.1 spans 2 CDs. The silent install never asked for CD 2 of 2.
My build application that accesses the PCI-7833R card works fine installing NI-RIO with the /q option.
Heres a list of NI software that was installed:
NI CompactRIO 2.1.0
NI LabVIEW Run-Time Engine 7.1.1
NI LabWindows/CVI 8.0.1 Run-Time Engine
NI Measurement & Automation Explorer 4.1
NI PXI Platform Services for Windows 2.1.0
NI-RIO FCF 2.2.0
NI-Serial 3.1
NI-VISA 4.0
NI-VISA Runtime 4.0
NI-VISA Server 4.0
The following can be included as additional installers with the Labview 8.2 application builder:
NI LabVIEW Run-Time Engine 7.1.1
NI LabWindows/CVI 8.0.1 Run-Time Engine
NI Measurement & Automation Explorer 4.1
NI-Serial 3.1
NI-VISA Runtime 4.0
NI-VISA Server 4.0
By including the above list of additional installers, can I create an
installer (and application) that uses the PCI-7833R card not having a
separately install NI-RIO first? I haven't tried yet but I will and
report back my findings.
The following NI software would be missing (i.e. not available as an additional installer from the application builder):
NI CompactRIO 2.1.0 (not using any cRIO)
NI PXI Platform Services for Windows 2.1.0 (not using any PXI stuff)
NI-RIO FCF 2.2.0 (this sounds like something I will need NI-RIO FPGA Communications Framework)
NI-VISA 4.0 (this might be something thats needed too)
Message Edited by dwisti on 10-24-2006 02:55 PM

I am using UPK developer 12.1.0 single user. My sofware has crashed and needs reinstallation. Please suggest how can I take back up of my source files. I am unable to open the application and i can not locate the library backup folder on my local machine.

I am using UPK developer 12.1.0 single user. My sofware has crashed and needs reinstallation. Please suggest how can I take back up of my source files. I am unable to open the application and i can not locate the library backup folder on my local machine.
Also, does reinstallation takes the back up automatically or the files will be lost. Please help.

Here are a bunch of scripts to get folder size under all circumstances. Take your pick.
https://gallery.technet.microsoft.com/scriptcenter/site/search?query=get%20folder%20size&f%5B0%5D.Value=get%20folder%20size&f%5B0%5D.Type=SearchText&ac=2
¯\_(ツ)_/¯

Application builder adds additional select instr.lib folders

Hi,
When I build my application, the Application Builder decides that it should include additional directories instead of the default files (data directory, .aliases, .exe, and .ini files). The additional directories include files that are named the same in various instr.lib's but are in different libraries, i.e. Close.vi or Initialize.vi. In my project explorer are there no unresolved dependancies. Does anyone know why this may be happening?
I just marked out the company name in blue if you were wondering.
Solved!
Go to Solution.

What version of LabVIEW are you using? If you are using 2009 or above, there is an option to use the 8.X format for the executable. It is one of the advanced options in the build specification. You do NOT want to do that. In the 8.X format, the VIs are saved in the executable as a flat directory. This means that any VI that was named the same, regardless of library association, would conflict. This would cause those libraries to be saved outside of the executable.
If you are using the newer format, the executable keeps a directory hierarchy, just like a zip file. So you won't have the name conflicts in that instance.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Display Bug in LV 8.20 Application Builder

There seems to be a minor bug in the displaying of the "VI Settings" in the application builder for LabVIEW 8.20.
The problem is in an executable build spec, in the "Source File Settings" category.
Select a sub VI in the tree, then uncheck the select box for the "Remove Panel" property. Now select any other VI in the tree, then go back to the one you unchecked the "Remove Panel" box. You should see that the box is now checked.
If you don't do anything else and just select "OK, then go back into the build spec, you'll see that the property was correctly saved as unchecked. So it looks like it's just a display problem.
I've made sure the VI I try this with does not use any property nodes and it is not marked as a dynamic VI. I can reproduce this on two machines running Windows XP Pro SP2 and LabVIEW 8.20.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

In addition to Ed's
comment, I would like to say that this unexpected behaviour is not
always appearing. I have just seen following while editing this text :
I have unchecked the Remove Panel box for all the UI VIs (all are
located in the same directory). When scrolling through the different UI
VIs in the Soure File Settings, the box was unchecked for all the VIs.
Without closing the Source File Settings window, I switched to
Developer Zone and switched back to the Source File Settings. For some
UI VIs, the Remove Panel box was checked. I closed the window and
opened it again, the box was unchecked again for all the UI VIs.
But I have also encountered the case that when scrolling through the
VIs to try to uncheck this setting for all of them, it suddenly appears
checked again for a VI for which it was unchecked or unchecked for a
before checked VI.
You finally end with a very unclear situation and it may be that the
Remove Panel is really checked for some VIs. At least, in some cases,
the built EXE could not run because of missing front panels. I can't
remember the exact error messages when running the EXE but they
mentionned the name of the VI and something about missing ressources. I
opened the .lvproj file and noticed that the "Remove Panel" property of
these VIs was set to TRUE. After modifying these settings and
rebuilding the EXE, it ran as expected.
In development, I
normally uncheck "Allow user to resize window" of the UI VIs because
this setting can unfortunately not be changed when configuring the
executable. In the "Source File Settings" I uncheck all options of "Use
VI Setting" for these UI VIs and I only check "Auto-Center" (all VIs)
and "Window is Modal" (some VIs).
There is another problem with the application builder that I would like
to mention. For (at least) following settings, the development settings
of a VI will not be overwritten by the Source File Settings when
building the executable :
- Window has title bar
- Show Menu bar
- Show Toolbar
- Show Scroll Bars
This is also very annoying because you will need to change these
settings in the development environement in order to get the expected
appearance in the executable.
LV8.2 English / WXP SP2

Folder of application builder(*.exe) with run-time DLL

My application consists of main.vi, subvi folder, and example folder.
In addition, I have to add the run-time libraries for add-on tool kit (advanced signal processing, lvwa.dll) which should be located in the root folder.
(For exe application, can I set the location of DLLs to not the root folder but "DLL folder"?)
In my several trials, I can't maintain the hierachy of "example folder".
Instead of my intension, the NI application builder copied the files in the folder to the support directory.
Can I locate the "example folder" to the root folder by using NI application builder?
In summary, I want to get the folder structure by application builder.
main.exe, DLL folder, Example Folder.
메시지가 08-08-2008 01:30 AM에 labmaster에 의해 편집되었음

Hey Labmaster,
What version of LabVIEW are you using?
I am not too clear as to what you are trying to do. You can create folders and add anything from your project when creating an installer under the Source Files section in its properties.
It might be easier if you'd attach a screen shot of what you are doing or trying to do.
Aashish M
Applications Engineer
National Instruments
http://www.ni.com/support/

Application Build problem Labview 8.5.1

Having a problem creating an Installer with 8.5.1. When being built a menu appears asking for
"NI Labview 8.2.1" distribution. Needs to copy a component installed or updated by the distribution to continue building the installer.
Despite trying all of the Disks I have, First quarter DVD, and all of the second quarter CD's it does not recognise any of them. When the CD's or DVD is inserted it shows a nidist.id file which I select (because it says that's what it requires) but them it gives a message stating that
"You cannot choose this folder name; a file of that name exists"
I have tried this build on 2 different machines and get the same response, anyone got any ideas on this or is it a no brainer in 8.5.1?
One last thing if this lot cannot be got to work, the additional files required are:-
Ni Labview Runtime Engine 8.5.1
NI Measurement & Automation Explorer 4.5
NI PXI Config Support for Windows
NI DAQmx 8.7 (unsure if this is included in MAX?)
NI Visa Runtime 4.4
Does anyone know if I just downloaded these from NI website and installed on the computer that will run the final .EXE file it will work?
Labview Version 8.5
Labview Version 8.6
Labview Version 2013

Hello Jack1,
I have been looking into your posts. There are two immediate actions you could try to help. I have identified that you are having issues with the computer recognizing that you have inserted the CD it has requested. Also, you are having trouble with repeatedly being asked to change back and forth through disks, at every attempt to build the installer. As you may need to try this more than once, it may be helpful to you to create a folder for each CD or DVD, and copy and paste the contents of the individiual disks. This software will be recognized, even if copied on to your hard disk.
When you click 'Build', to begin building your installer with your necessary additional resources, you will be asked to insert the last set of CDs or DVDs you have used. However, at the prompt you can click on the 'Folder' icon and browse the folder where you have saved the individual disk contents. The error you were receiving in your first post, "You cannot choose this folder name; a file of that name exists", implies that you were most like click on the *.id file and selecting ok. I have avoided this on my machine by opening the folder with the disk contents, not selecting any files, and the click the 'Current Folder' button. After you have selected it, ensure that you have ticked the box next to 'Cache components from this distribution.' Whether you use the CD, or folders containing the disk contents, this options creates a local copy of the requested files to a cache directory, therefore no requiring the user to input disks, or point to file locations in the future. If you have a repeated patter of building applications and installers, this will quicked your process, and eventually allow to delete the disk contents you have copied to your hard disk.
The disks from your previous installations are requested primarily because of your selection to include NI-DAQmx as an Additional Resource. As this is the main driver, shared components are recognized by the Application Builder. I, therefore, can recommend that you try building the installer with the above steps on your laptop, which your mentioned is a fresh installation.
When you have had a moment to try this, please post back to see if I can answer any further questions on this topic, or know that it has worked.
Regards,
Message Edited by gt3000 on 11-03-2008 03:26 PM
George T.
Applications Engineering Specialist
National Instruments UK and Ireland

Require additional installers?

Hey,
I am looking for advice on the following, I am attempting to build a stand alone application, i am unsure as to how to go about achieving this as its the first time i have attempted it. I have built an application with my main vi as the start up vi and all the dependencies are attached so there are no vis to choose from for the source files for the always included window.
My next step was to build an installer, i assume the source files to attach to this is the one i selected for the start up in building the stand alone application. Now within my vi i use NI-IMAQdx 4.0 aquisition software i was wondering what additional installers i require or will my code execute? Do i need to add drivers etc.
Regards,
Damien

Hi guys,
I have added the NI-IMAQ 4.7.0, NI-IMAQdx 4.0.0, the chroma driver, NI-Serial and the NI-VISA Configuration support 5.2, NI-VISA Runtime 5.2 and NI-VISA Server 5.2. Do i install Vision Run-Time Engine 2012 also?
I have a serial number for the labview professional development licence and it contained the vision acquisition module along with the vision builder and toolkits etc. I also have a different serial number this is the vision development module run time licence which is the vision acquisition product. So this is the one i activate on the deployed computers? Thanks for the help i am just a bit cautious as to what i can activate.
Thanks
Damien

LV 8 app builder - advanced installers confusion

When I check the box to include NI-DAQmx 8.0 in the Advanced Installers section of Installer Properties I get a weird error. It says it's unable to locate the installer source for "NI DIAdem 10.0" distribution". I also have the Run-Time Engine 8.0 box checked, but I only get the error when I have the NI-DAQmx 8.0 box checked. Nothing else is checked. I'd really like to be able to include the DAQ drivers in the build.
Also it expects the source for the NI-DAQmx 8.0 to be on the E:\ drive. Is there a way to change that so I don't have to load the CD every time I want to do a build? I tried changing the Installer source location, but it keeps reverting back to E:\.
George

GS,
I'll start by answering your second question first. I think the easiest way to point the application builder to somewhere other than your E:\ is to copy the entire contents of the DAQ driver cd to your hard drive, and then point the application builder to that location on your hard drive.
Now on to the first question. I'm not sure why you're being prompted for the DIAdem 10.0 Distribution when building the application. Have you included any DIAdem express vis in your vis? Are there any vis that need DIAdem in your programming? I believe that you been speaking with Brad about DIAdem issues and if you'd like to communicate this issue to him, please feel free to do so.
Best Regards,
Chris C
Applications Engineering
National Instruments
Chris Cilino
National Instruments
LabVIEW Product Marketing Manager
Certified LabVIEW Architect

What is the best practice for package source locations?

I have several remote servers (about 16) that are being utilized as file servers that have many binaries on them to be used by users and remote site admins for content. Can I have SCCM just use these pre-existing locations as package sources, or is this
not considered best practice?
Or
Should I create just one package source within close proximity to the Site Server, or on the Site Server itself?
Thanks

The primary site server is responsible for grabbing the source data and turning it into packages for Distribution points. so while you can use ANY UNC to be a source location for content, you should be aware of where that content exists in regards
to your primary site server. If your source content is in Montana but your primary server is in California ... there's going to be a WAN hit ... even if the DP it's destined for is also in Montana.
Second, I strongly recommend locking down your source UNC path so that only the servers and SCCM admins can access it. This will prevent side-loading of content as well as any "accidental changing" of folder structure that could cause
your applications/packages to go crazy.
Put the two together and I typically recommend you create a DSL (distributed source library) share and slowly migrate all your content into it as you create your packages/applications. You can then safely create batch installers, manage content versions,
and other things without fear of someone running something out of context.

DLL created with LV 7.1 Application Builder doesn,t work when analysis subVIs are present

I'm looking for a solution of the following problem.
The DLL created by the "sum1.vi" source works properly, while the DLL create by "sum2.vi" always gives a zero result.
The "sum2.vi" source contains an additional "Hanning Window" VI (not wired), that seems to be the cause of the problem.
If I delete the Hanning VI and re-build the DLL, the same works fine
Is there a solution or is it not possible to make Labview DLLs when containing analysis VIs as filters, windows, FFTs, and so on?
Thank you for your answers.
N. Roberto
Attachments:
sum1.vi ‏12 KB
sum2.vi ‏14 KB

Roberto N. wrote:
Thank you Jordan, I'm using Labview 7.1.
Anyway I've resolved the problem by adding the "lvanlys.dll" file (present in "..\Labview 7.1\resource\lvanlys.dll" path) as support file in the building process. Now the DLL containing the analysis functions works correctly.
Natalino Roberto
Ok, you probably got lucky since the lvanlys.dll seems to implement that function directly. However most Advanced Analysis functions are just redirected by lvanlys.dll to the Intel Math Kerneal Library that gets installed with LabVIEW 7.1 and higher. The only way to get that properly installed with your LabVIEW executable or DLL is to create a LabVIEW installer in your Application Builder and make sure to select under "Installer Settings->Advanced" the "LabVIEW Run-Time Engine" and the "Analyze VIs Support". Then use that installer to install your DLL on another computer.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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!

Application builder missing files

Hi all,
I'm new to LabView and I'm trying to deploy an application as an executable. I'm running LabView 2009 on Win XP Pro. I have the application builder and ran the application builder tutorial. The tutorial worked fine, but doing the same steps on my project that calls sub-VIs from several different libraries didn't work. I'm not trying to build an installer yet, just a stand alone executable running on a machine with the LabView run time framework already installed. I'm not calling anything by reference, all sub-VIs are called explicitly.
The VI I'm trying to deploy works fine running in LabView. Application builder successfully generates an executable. When the executable is run, it pops up a dialog looking for a bunch of sub-VIs. I attached a copy of the executable prompting me for a sub-VI contained in vi.lib
First, is there a user's manual or something like that for Application Builder? LabView Help describes how to create a stand alone executable but doesn't describe all the settings in detail. I probably just have one of the settings wrong.
Any other thoughts or suggestions on what to try next?
Thanks in advance for your help.
Solved!
Go to Solution.
Attachments:
app builder error.JPG ‏21 KB

LV2011SP1
I have been developing in the directory
C:\Program Files\National Instruments\LabVIEW 2011\user.lib
The source code is located in a subfolder in the "user.lib" folder
The builds go into the destination subfolder "user.lib\builds"
The executable built returns an error when it is run. It can't find one of the subvis.
The subvi in question is listed under the dependencies for the main vi in the project.
I copied the devlopmentto a new location, namely
C:\Users\Me\Documents\LVcode\builderErrorTestFolder
The executable built within this new project ran without error on the development machine, but the executable built with the installer in this project will not run on a non-development machine. In the case of the executable installed on a non-development machine, the error is a "can't find vis" error, but it is limited to NI_AALPROLvlib files and NI_AALBaseLvlib files
What could be the problem?
Attachments:
cantFindFile.jpg ‏161 KB
willNotFindNI_AALPROLvlibPwrSpectrm.png ‏150 KB

Application Builder: Additional Installers Source Location

Similar Messages

Maybe you are looking for