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

Similar Messages

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

Application Builder problem on one server but not another

I am having an Application Builder problem. When I get into App Express and go inside the builder and try to edit a listed application, I get an “http 404 the page cannot be found. The page might have had its name changed or is temporarily unavailable” situation. I can get into SQL commands, utilities, and administrative activities. I can also run the application. Also, if I go onto a different server with App Express on it, I can get into the builder and edit applications with no trouble. Our DBA had the server in question rebooted a little over a week ago and that took care of the problem for a couple days. Any ideas? Is this an Express problem or a server problem? He had also tried restarting Express before he had the reboot done and that didn’t help.
Thank you for any help.
Cordially,
Robert J. Smith

I have messages from the Apache error log files from the dates I was getting the builder error. For future reference, I will post them below. The builder has been working fine lately.
Robert Smith
** error log messages follow **
[Mon Jul 16 07:25:12 2007] [error] [client 147.159.5.134] [ecid:
79143788610,1] File does not exist:
/app/oracle/oraappsrv10g/forms/java/java/awt/KeyboardFocusManager.class
[Mon Jul 16 07:25:12 2007] [error] [client 147.159.5.134] [ecid:
79143788611,1] File does not exist:
/app/oracle/oraappsrv10g/forms/java/java/awt/event/MouseWheelListener.class
[Mon Jul 16 07:25:13 2007] [error] [client 147.159.5.134] [ecid:
83438757083,1] File does not exist:
/app/oracle/oraappsrv10g/forms/java/oracle/forms/registry/default.dat

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

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

Project build problem - Labview ARM STM32F103

Hello,
i`m trying to make project using LabVIEW Embedded Module for ARM Microcontrollers 2010 and my STM32F103 board. Everything is fine . I made new project, added some outputs, but when i try to build it, it stucks for a while and I get error:
[17:38:59] Status: Error
Unexpected error occurred.
[Source: Cannot read project file 'C:\Users\Sh\
Documents\Untitled Project 1\STM32F103x\
Application\0.061\Project\LabVIEW.uvproj' !
Timed out waiting for a response
Detail: [UVSC_PRJ_LOAD, MSG: 0x201F, STATUS:
0x1D] Code: 29]
I`m using that target : http://forums.ni.com/ni/attachments/ni/420/2699/1/STM32F10x.zip
Any ideas what might be wrong?
Thanks.

Hi mark331
I would recommend You to go in details through forum http://forums.ni.com/ni/board/crawl_message?board.id=420&message.id=1886. There is multiple number of tips and instructions about ARM STM32F103 and LabVIEW.
I am pretty sure, that You can find an answear there.
Best regards
Barbara

Application build problems with polymorphics

In LV8, when I try to build an executable application I get an error about polymorpics.
It says to us an "instance" of it instead of the polymorphic.
Anyone know an easy way to search out all of the polymorphics and then how to convert them over to something that will "build"?
Thanks
Jim

Jim,
Is there any sort of error number or additional text that is associated with that error? Checking the "Disconnect...unused polymorphic instances" should remove any unused instances and automatically remove them from the build and is mostly for saving some space. Is this older code that you have opened in LabVIEW 8 or was it all developed in 8? If it is older you may try to Mass Compile it to make sure that all of the VIs are linked correctly. One last thing to try is addressed by this KB:
http://digital.ni.com/public.nsf/websearch/86256A47004E16D186256B1A006C76EC?OpenDocument
This is in LabVIEW 6.1 and should be taken care of in previous releases, but its something to try before you have to go through you code to try to find all of the polymorphic VIs.
Hope this helps!
Andy F.
National Instruments

Error 7 in "application builder" for LabVIEW 8.5.1

Hello,
I am getting an error while building a project for making EXE file.
below is the displayed message.
Error 7 occurred at Copy in New
VILibrary.vi->AB_Dest_LLB.lvclass:Create_Destination.vi->AB_Build.lvclassLCreate_Destinations.vi
->AB_Build.lvclasss:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_BUild.vi->AB_Build_Invoke.vi->A
B_Build_Invoke.vi.ProxyCaller
============================
NI-488: Non-existent GPIB interface.
C:\ProgramFile\NationalInstruments \LabVIEW8.5\vi.lib\Utility\libraryn.bin
thanks,

You can force LabVIEW to recompile the entire VI hierarchy in your project with CTRL+SHIFT+Run Button.
Have you imported some old VI's into the project? From a previous version?
Did you add files since creating the build parameters? You may want to delete the build parameters and create a new one.
RayR
Message Edited by JoeLabView on 07-02-2008 08:35 AM

I w'd like to know if LabVIEW 6.0 Application Builder includes the daqdrv (for data acquisition) and serpdrv (for serial communication) support files by default.

Building an application to communicate to a device by serial port

Hi velou
The LabVIEW 6i Application Builder no longer requires daqdrv. Regardless of your Application Builder and LabVIEW version, you must always install the appropriate driver files on the target machine. For example, if your application communicates with a DAQ board and a GPIB board, then you must install NI-DAQ and NI-488.2 on your target machine. If you are using the VISA VI's for serial communication, than you have to install NI-VISA . If you are using the "old" serial VI's, than you have to include serpdrv separately.
Luca P.
Regards,
Luca

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

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

Custom icon in application builder

I am trying to create an executable with custom icon using Application Builder in LabVIEW.
I converted a .png image to .ico for the icon, but when I select that .ico file as a custom icon, I get the following message:
"The selected file doesn't contain all of the needed icons. Without them, your application will show an incorrect icon in some views.
Missing icons:
32X32, 16 color
16X16, 16 color."
Any comments\suggestions on how to get custom icon would be appreciated.
Thanks.

It's possible that you don't have both 16x16 and 32x32 icons in 16 bit color. When you convert the .png to an .ico, see if there is an option to convert into necessary ico images that you need.
As a way to double check this without using application builder, load the VI : <vi.lib>\Platform\icon.llb\Read Icons for Application.vi
It will show you the different icons that are read from the .ico file.

In application builder the top level vi is always set to "run when opened"; how do I turn this off so I don't have to change it each and every time I build a .exe??

I build a lot of executables using Application Builder under LabVIEW and in every one I build, I don't want the top level vi to take off and run when I open the executable. Currently, I edit each .exe I build within Application Builder and change the option of "run when opened" from Yes to No for the top level vi. All the other subvi's are already set to No. It would seem as though there should be some way to "turn this off" if you will so the top level vi is not always set to "run when opened" by default within Application Builder. Is there such a solution that anyone knows of?? Any help would be apprec
iated... thanks...

Indeed the Application builder forces "run when opened" to true for top levels VIs. If you don't want your VI to make any real work when the application starts, you should simply put a do-nothing loop in the beginning of the VI that will loop until the user presses a boolean. It will be more intuitive for users to press a Run button on the FP than clicking on the white Run arrow in the bar.
LabVIEW, C'est LabVIEW

Problems with Application Builder and NI-DAQmx drivers in Labview 8.2 Professional

Hello everyone,
I am trying to use the application builder to create an executable so that someone without labview is capable of a remote panel connection to connect to our test laboratory. our test laboratory uses the USB Compact DAQ 9172. I did find some other forums that ran into a similar problem where a computer that didnt have labview installed on it looked for a particular driver (nilvaiu.dll). The common solution appeared to be when building the installer, include the current NI-DAQmx (8.3 in our case) option and then the clients worked fine. My question is when i use the application builder to create an installation file for this application, i get a prompt to:
Locate the "National Instruments Device Drivers - February 2006 Disk 1" distribution. LabVIEW needs to copy a component installed or updated by the distribution to continue building the installer.
What is confusing is that the installation cd's in our laboratory are from August 2006 (501165N-03). It didnt make sense to me that i would need to downgrade the drivers from a few months ago, but i've been wrong before. We just upgraded from the full development to the professional version about 2 weeks ago to utilize the application builder function. Has anyone else ran into this problem and could this be a limitation because we purchased the software with the academic discount?
thanks in advance
Chris

Chris,
My "fix" is brute force. Backup everything. Removing all the NI software takes a while. Be sure to remove leftover directories and files.
Altering the windows registry takes seconds and is not hard if you know what you are looking for. I've attached a screen shot with the NI entry selected. This is what I deleted on by machine. The thing to remember is that the registry controls all the software on your pc. Delete/alter the wrong entry and you have problems. Worst case scenario is that you could end up formating the hard drive and starting over from scratch. I'm not trying to scare you, but I want to make sure you understand the potential for harm.
One thing you might try first. NI-DAQmx 8.5 is now available for download from NI. You might try unloading 8.3 and installing 8.5.
Attachments:
regedit pic.JPG ‏102 KB

Application Builder error in LabVIEW 7.0

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

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

Application Build problem Labview 8.5.1

Similar Messages

Maybe you are looking for