Building exe with installer

I am using Ni DAQmx and Labview 2009 professinal. I tried to build an exe and distribute it to my team. Initially they had issues
opening the file and instead opening the login screen it opened a main GUI screen with the errors as shown in output.jpg. I did some
search on this forum and I thought I will build the installer with LV runtime engine, DAQmx 8.5, MAX import ini file and send the msi
extension to my team. But on the process of building this I get the following error as shown in ni_install.jpg. When I select DAQmx
8.9.5 the build becomes unsuccesfull. Please need some help to resolve this.
Thanks
Attachments:
ni_install.jpg ‏99 KB
output.jpg ‏159 KB

My problem is building the installer before giving it to my team. When I right click "Build specification" and create installer I get
application properties.
Product info: Provided my installer destination and other info
Source Files: I provided my exe into destination view - program files folder
Additional installer: I choose DAQmx, labview runtime engine 2009, MAX
And I filled all the info on the property setting window. With all this it comes up looking for NiDAQmx and defaults to drive CD drive.
Should I use my DAQmx CD at this point and then build the installer. Is it ok to build the .exe and then create the installer.
Thanks

Similar Messages

Pre Build EXE and Installer Set Version

So this topic comes up relatively often so I thought I'd make a new thread showing an example of how to make it work. The problem is developers want a way to set the version of builds programmatically. Luckily NI added some VIs for doing this. Too bad you can't invoke them from the Pre-Build action of a build, because that information is read before the pre-build. Here is an idea exchange discussing it.
But I figured I could come with some kind of work around and I have two, and neither is perfect. Attached is a simple project. It contains a VI that runs reading the EXE version that it is running from once it is in an EXE. The project has three build specifications, an EXE, and two installers. The developer can set the Major, Minor, and Fix of the EXE, but the build version is set programmatically in the Pre-Build action. The version of the installers will also be set to the version of the EXE.
Attempt to build the EXE and a dialog will appear asking to enter the build version that should be used. This could be determined some other way but this was the easiest for the demo. If the EXE, and the Installers are already the correct version, where the build is the same as the one specified, and the installers are the same version as the EXE, then the build goes on like normal. But if the build you enter is not the same as the current, it will abort the current build, change the versions, and then tell the operator to attempt to build again. This time no prompt is seen and the build will work like normal with the version you set earlier.
The downside to this method is you have to tell the developer to build again, I figured I could do that programmatically so I tried. There is a constant on the BD of Prebuild Action VI.vi, and if it is set to True it will try to invoke a new build on its own. The problem with this method is the build the user invoked is aborted and the user sees the error. But the second build might have worked fine, but there isn't any feedback.
In any case this is a sorta working way of setting EXE and Installer build versions from a pre-build VI.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.
Attachments:
Test EXE Version.zip ‏80 KB

Bob_Schor wrote:
I took your idea and "simplified" it a little
Some may want the simplified version I understand. But for me I wanted a more robust VI, one that would work if a project had multiple build specifications of applications, or multiple installers. Some developers may have two applications one that is normal, and another with debugging turned on and I wanted the versioning to work consistently there by grabbing the newest version and using it. And in all my cases, if there is an installer it should be the same version as the EXE.
As for the getting around the error I think if I had enought time I could dig into the NI VIs to get rid of the error and show the progress of the new build. The whole build process is a bunch of VIs, that augment the right click menus in the project so the source is there it is just taking time to understand it.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Problem of building .exe with VI template as subVI

I'm having trouble to successfully build an .exe with VI template as a subvi. Please see the image for the error when executing the built file.
In my toplevel VI, I use two subpanels (side by side comparison), each subpanel loads the same subVI (saved as template in order to show the front panel). The code executes beautifully in development mode, but once it is built into executable (the subvi is added as dynamically loaded vi), only one subpanel loads the subvi, the other one is just blank, and an error message is displayed.
I understand there are other options here, but I would like to see if there are solutions before considering an alternative route. Any help will be greatly appreciated.
System
setup: WinXP Pro SP1 with LV7.
Thank you,
-Joe
Attachments:
lvError.gif ‏7 KB

Hi Joe,
We've seen this error when using express VI's inside of template VI's which are loaded using VI server. Are you doing that? If yes, then take all the express VIs that are inside the template VI and turn them into static subVIs.
I don't know if it will help in your case, but let's try it.
Regards,
Luca
Regards,
Luca

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/

Is it possible to build exe with vis that have striped block diagrams?

We can tell that an entity has stolen our code and are using them in their .exe file.
We used to distribute our program as a light exe layer that dynamically loads some source code distribution vis (block diagram striped) off disk and runs them.
What we don't know is whether they actually got our in house source code, or if they are somehow taking the distributed vi's and compiling them into their exe.
So the question is: Is it possible to take vis compiled for a 'source distribution' with the block diagrams removed (but front panels not removed) and compile them into an executable?

It's actually quite possible to use a source distribution VI for a new app. You need to select the "Do not disconnect type definitions or remove unreferenced
members" option in the "Additional Exclusions" page.
I've attached an example on how this can be done. Untitled Project 1 would be your project, which has a build target of your app, along with the source distribution for a VI with the block diagram stripped. Untitled Project 2 would be your competitor's project, which is a VI that uses your subVI directly and builds a separate application. As you can see, I can successfully build an application using your code.
Attachments:
source dist ex.zip ‏76 KB

Application-Builder-Exe with Web-Server crashes

Windows XP Service Pack 2
EXE file created with Application Builder
Web-server active - as picture 1 time per second
Access from browser in local network:
3 times has occured application crash:
Yesterday:
10:26:34
Application fault VI-app.exe, Version 1.0.0.0, module fault: lvrt.dll, Version 8.6.0.4001, Address 0x007424c3.
10:30:21
Memory fault 1129110434.
13:50:59
Application fault VI-app.exe, Version 1.0.0.0, module fault: lvrt.dll, Version 8.6.0.4001, Address 0x007424c3.
Now:
First access with browser at 08:03, second acess at 08:24
08:26:07
Application fault VI-app.exe, Version 1.0.0.0, module fault: lvrt.dll, Version 8.6.0.4001, Address 0x007424c3.
08:30:49
Memory fault 1129110434

Hey Hellboy,
Please have a look at this thread -> http://forums.ni.com/ni/board/message?board.id=170&requireLogin=False&thread.id=194442
You might find some hints due to the facts its discussing the same error.
Christian

Problem building exe with dynamic vi

Hi all, i'm using LV 8.2 evaluation version to build an executable file for my test platform. This platform calls for individual test vis dynamically.
I can export the platform vi into exe alright but it always fail to run the test vis dynamically when called by the platform. I know the platform is working alright as it's able to successfully traverse through all my operating states, but when it comes to the state which contains a subVI which calls these test vis dynamically, nothing happens and it just proceed with the next state. The even wierder thing is that the program then enters my default state (which isn't even on the list of states for that particular operating mode!)
Based on this result i can say that the platform is working fine as it was able to call various subvis and traverse through the defined states (except for the default state case). Thus i guess it must be something which i did wrongly during the build process which caused it not to run my dynamic test vis. I spent the whole day trying various build options but it still doesn't run my dynamic vis.
Any ideas?
PS: Does the build process automatically import the MAX settings?

No, it's not a cracked version just to make myself clear.
Dennis, i don't think it's a problem with the path as the exe does not have any problem loading other text configuration files. Yes, i've included them under the dynamic vi and support files option.
Attachments:
Build option for LV8.2 eval.JPG ‏31 KB

Install problem JDeveloper 12c (12.1.2.0.0) (Build 6668) with Generic Installer on windows

Hi,
I am trying to install JDeveloper 12c (12.1.2.0.0) (Build 6668) with Generic Installer on windows .
C:\Program Files\Java\jdk1.7.0_25\bin>java -jar C:\jdev_suite_121200.jar
I get the following error :
Extracting files................................................................
Unsupported platform (unable to determine the startup directory location).
The Oracle Universal Installer failed. Exiting.
When I try with windows install ( right click jdev_suite_121200_win32.exe and "run as administrator") , I get the following error:
ERROR Launch:No such file or directory
In the discussion (https://forums.oracle.com/thread/2573396?start=0&tstart=0) , it is said to be solved by "running as administrator" but it didn't work for me ...
Thanks ...

Hi,
Can you please tell whether you are using 32-bit or 64-bit windows.
If it is 64-bit then you must run as administrator. In Windows 7x64, just right click on the jDeveloper exe and choose "run as administrator..."
Remove the existing Oracle folder and restart the system.
Try to install in new drive.
Oracle Fusion Middleware Installation Guide for Oracle JDeveloper - 11g Release 2 (11.1.2.4.0) Hope this link will give you more idea in installation.
Thanks
Pramila
Message was edited by: d6866663-7e0d-4497-89df-99f670c41872

Create uninstaller exe with application builder

Hi!
Im using LabVIEW 8.5. I have created an application with the app. builder, it works fine, also an installer.
But I need an UNINSTALLER, like Uninstall.exe to be created also.
I have found a NI doc, which says:
"The Create Uninstaller option was removed from the
Advanced Installer Settings dialog box because the Application
Builder always creates an uninstaller"
But where can I find it?
im able to uninstall my app, using the Windows add/remove softwares option, but i need an exe.
Can you help me?
Thanks:
Waszil

Since the installer is based on Microsoft technology and the Microsoft standard is to only have the Add/Remove option, you cannot create an uninstall.exe with LabVIEW. I'm not even sure why would would need to if everything works with Add/Remove Programs and that is what everyone is used to now. In any case, there are probably some commercial installer packages available that still support the old technology.

Labview 8.5 installer build *.exe wrong date code

In Labview 8.5 application installer build *.exe has a date code of 7/17/2007 even though it was built today. It will not update even after deleting it. Is this a known bug? SS

Hi SS,
The Date Modified property of setup.exe shows the date the MetaInstaller was built. This was true in earlier versions of LabVIEW as well. It was reported to R&D (# 3T87DAP4) but was determined to be expected behavior. The actual date and time the installer was built can be determined by looking at the properties of \bin\dp\install.msi. Feedback is always appreciated, so please feel free to create a product suggestion if you think this should be changed.
Jennifer R.
National Instruments
Applications Engineer

Provisioning Profile - problems with installation our app build on devices

We have problems with installation our app build on few devices. There are all in Provisioning Profile, but we don't know why we can't install the build on some devices. Any ideas?

Apple products needing Apple love/support (athough using Adobe to compile to Apple-code may be an obvious concern since nothing beats native-code)
The app still however requires code-signing in the correct manner - personally, the more the merrier.

Hey, I had met a problem with installation. Can any one help me?

Hi everyone, I'm an user of Windows 7(64 bit),
I had just download "Master Collection CS5.5"
Everything are fine but Adobe Acrobat Professional can't install on my computer.
There are the details..:
Exit Code: 6
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 4 error(s), 1 warning(s)
WARNING: DW066: OS requirements not met for {AC76BA86-1033-F400-7760-000000000005}
----------- Payload: {AC76BA86-1033-F400-7760-000000000005} Acrobat Professional 10.0.0.0 -----------
ERROR: Error 1324.The path R嶰up廨er un document num廨is?sur un multifonction.sequ or the volume is invalid. Please enter it again.
ERROR: Install MSI payload failed with error: 1603 - 安裝時發生嚴重錯誤。
MSI Error message: Error 1324.The path R嶰up廨er un document num廨is?sur un multifonction.sequ or the volume is invalid. Please enter it again.
ERROR: DW050: The following payload errors were found during install:
ERROR: DW050: - Acrobat Professional: Install failed
Thanks

Re: Hey, I had met a problem with installation. Can any one help me?
This worked for an English version and the concept should work with all Adobe programs - new or old (hopefully in any language). My guess is that you have/had an older version of Acrobat/Reader on your computer hard drive that needs to be *completely* removed first. Uninstall the new (and any old) Acrobat; then try using the "kb2..." guideline link below before reinstalling the new Acrobat. I am including the lengthy instructions in order to help others with more extensive installation problems. Good luck!
I live on a fixed income and use CS for a hobby. I had problem installing Adobe Creative Suite (CS1) to Windows 7 64-bit Pro on my new computer. Also installed Adobe Photoshop LR3. What I learned: All Adobe products (Flash, Acrobat/Reader, Photoshop, Creative Suites, etc.) leave a VERY pervasive footprint on your hard drive. Logic finally worked for me.... think of building a house; there is an order you have to do things in. First, you have to clean the area before laying the foundation; then you have to build the framework before you put the roof on. You cannot install an older program over ANY newer program; and you will sometimes have a problem installing a newer program containing Flash, Reader, etc. unless you "erase" the older versions of Flash, Reader beforehand. If installing older programs, do a Custom/Manual install; do not install older versions of Flash, Reader, etc. packaged with your Adobe software.
SOLUTION (not easy, but it works):
I first tried this; it did not solve my problem (but, if applicable, may help others). http://windows.microsoft.com/en-us/windows7/Make-older-programs-run-in-this-version-of-Win dows
Before doing anything, make document and any database/presets/cache back-ups beforehand (keep notes on their designated location*); manually create a System Restore point. (Be prepared to reinstall Windows if necessary - I didn't have to.)
Completely and meticulously eradicate (clean) your hard drive of ALL Adobe programs [uninstall, remove remaining folders, and remove only the registry entries that have the Adobe name attached (unless you are an expert and fully understand the other entries)]. Use this as a guideline http://kb2.adobe.com/cps/400/kb400769.html
Do a Custom/Manual reinstall of all your Adobe products *in order of release dates* (OLDEST first).... do not include Reader, Flash, etc. If your CD will not automatically run at this point, click "Open folder to view files" (use Computer/Windows Explorer, if necessary). Click "Adobe Creative Suite (or your desired program) ==> Setup.exe" (IMPORTANT: Make sure that Reader, Flash, etc. are unchecked.)
After each of your desired Adobe programs are installed, test to insure they boot up. Then download the latest Reader, Flash, etc. apps and install them (I did this in order of release date - oldest first). Do test boot(s) again.
Copy/Paste your document and any database/presets/cache back-ups into the appropriate folders (*this will vary depending on your programs and your filing system).
It has been four weeks and all my Adobe programs work flawlessly - system is stable, no problems!

Call library node in builded exe - path problem

Hi!
I have builded an EXE with the App. Builder. In my application I use the Call Library Node, and call functions from a DLL.
I give the path of the dll with the "Current VI path", than strip the path, and add the DLL-s name. So in the CallLibNode I check the "specify path on diagram" option.
It works when I run my application on a PC that has the LV 8.5 installed.
But when I install my app on a PC that does not have it, just my setup installs the Runtime Engine onto it, it does not work, and I get errors.
Which is the proper way to give the DLL-s path, if I want my app run on any PC that does not have LV installed?
Thanks:
Waszil

Does the executable run correctly on the development machine? If not I would imagine it is a problem with how you are referencing the dll.
Have you installed all necessary support libraries you may be using throughout the program on the target machine? Are you able to confirm that the error messages are referencing to the dll not being found?
It sounds like you are referencing the dll correctly. When compiled, the dll is put into the 'data' directory within the root directory, so make sure that is there on the target pc
Message Edited by yenknip on 08-04-2008 10:42 AM
- Cheers, Ed

Build specification of installer hides already spec. destination

I have an installer build specification with the following problem with the "source files" dialog:
I select the exe build spec to be installed into a certain dest. dir (e.g. under program files). After doing so i close the dialog with ok. The next time i open the dialog this information seems to be gone, in the dest. view no folder has subfolders or other files below it. But if i repeat my steps from the first time, trying to install the exe into the same dir under program files, i get this error message:"The following files already exist in the destination directory:...". But i can't see them!
Any ideas?
This is Labview 2009 on Vista.
Holger

Perhaps they were written (somehow) as hidden files.
This way, if you browse to that location, you will not see them.
But if you try to save something with the same name, the computer will know the files are there.
Cory K

Making exe without installer

I bought Application Builder and have LabView 8 Full Development System and am trying to make EXE's from my VI's. My question is can I make an .exe that runs without Labview on a machine and without installing it into the registry? Where I work I don't have Admin rights on the computers and want to build .exe's to run standalone. I know that you can make .exe's that run with LabView on the machine and you can make an "installer," but that changes the registry and installs it into the Progam Files folder. I just want a standalone .exe, is it possible with Labview 8?

smercurio_fc wrote:
With any .exe you build with the Application Builder you need the run-time engine on the target machine, regardless of LabVIEW version.
In addition, you need the right version of the runtime engine. (You can install as many versions of the runtime engine as you need)
Actually, there were some workarounds in the past that allowed running a LabVIEW executable without installing the runtime engine. I am not sure if these things still work. See for example the following old post: http://forums.ni.com/ni/board/message?board.id=170&message.id=55834#M55834
Message Edited by altenbach on 02-26-2007 02:13 PM
LabVIEW Champion . Do more with less code and in less time .

Building exe with installer

Similar Messages

Maybe you are looking for