Uninstalling LabVIEW after an application (EXE) build

Hello,
I couldn't find any instructions for this. I have a LV project and build specification application.exe ready made. Now I want to uninstall labview and delete all VIs but keep all necessary components which are needed to run the application.exe. How do I know which are needed and which not when I start the uninstalling procedure? I use at least DAQmx and Vision Builder AI components. I can see items under Dependencies that VIs under a target require but it doesn't tell me what I need to uninstall.
Best Regards,
Jick

I don't want to sound rude, but it takes you under 1 min to create an installer. Removing LabVIEW will take minutes, if not an hour, since the uninstaller remove module after module after module.... and so on.
In your project window, right-click on Build Specifications and select Installer.
In the Installer window, fill in desired information and where you want your build to be created.
Then add your source files (your .exe file) and where you want it to be installed.
Then add the run-time engine under Additional Installers.
Then remove your whole Labview if you want. And as mentioned in a previous post, run your installer after. You then install your .exe file together with the run-time engine. Note that if you use DAQ you should add the driver too, together with the run-time engine.
Regards,
Even
Certified LabVIEW Associate Developer
Automated Test Developer
Topro AS
Norway

Similar Messages

Uninstall Labview after Silently installation

I installed Labview 7.1 using the silently installation and I need to do an uninstall like this (Using a .BAT file), for the Silently installation I used the Spec files attached.
In order to have a complete custom installation I also had to run separate the device drivers setup with its own spec file.
I already tried to uninstall using this same spec files changing for each feature to = Absent (This is suppose to remove if installed) but it doesn't completely uninstall. The Data Socket and the NI Spy remain.
Thank you in advance
Attachments:
LVspec.txt ‏1 KB

Hello EJPEREZ,
After further investigation, it appears that DataSocket is still present on the system because the LabVIEW Runtime Engine is still installed. To verify this, open the control panel, double-click on add/remove programs, select National Instruments Software, click on change and you will see a list of National Instruments Software that is installed on the computer. You can use this method to find out which NI Software product is leaving NI Spy on your computer as well.
Uninstalling the LabVIEW Runtime Engine will remove DataSocket from your computer. The way to do this from the command line is to use msiexec and the LabVIEW Runtime Engine MSI file. The command will look something like "path:\>msiexec /quiet /uninstall lvruntimeeng.msi" depending on your preferences and file locations. MSIexec is a Microsoft Windows utility and you can get more information about it on there website (http://www.microsoft.com). If you need more information about the commmand line parameters for msiexec, just type in "msiexec" in the command line and hit the "enter" key. The LabVIEW Runtime Engine msi can be found on your installation cd in the "components\lvruntimeeng\" folder.
Make sure you run this command AFTER you do the core uninstallation using the "setup.exe LVspect.txt /q" operation. Then you can use msiexec to uninstall the program that is leaving NI Spy on your computer.
I hope this helps,
E.Lee
Applications Engineer
National Instruments
Eric
DE For Life!

Labview 2010 error during exe build active x control

During the build of an exe of a labview vi, I get the following crash ( see attached jpeg). It has something to do with the activex control that is used in the vi. The activex control is registered with windows and functions properly. Any ideas?
Attachments:
TCAS DISPLAY ERROR.JPG ‏209 KB
TCAS Virtual Display 32 bit.vi ‏19 KB

Here's a Knowledge Base article that walks through a few things that you could try to prevent these Access Violation Errors.
Could you try building this executable on a different computer to see if it's related to that specific machine or installation of LabVIEW? If you find that it does work, it would be a good idea to do a reinstall of LabVIEW on the computer throwing this error.
When you said that you couldn't post the ActiveX control DLL, would the forum not let you post this? If that's the case, you can put your files into a .zip file and include an obvious filename (example: TCAS Error.zip ). Then upload the file to our FTP site at: ftp://ftp.ni.com/incoming and we can take a look at it that way.
I find the windows ftp the easiest ftp client to use. Just open windows explorer by pressing windows key+e then type the address into the bar at the top. Then just drag and drop your files in to the window.
Regards,
Austin S.
National Instruments
Academic Field Engineer

I can not create an Installer, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...

I can not create an Installer on LabView, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...
Solved!
Go to Solution.

Hi Shada this can happen if you are including additional installers to your installer for example DAQmx. When you are doing this the installer has to include other files like MAX (Measuremente and Automation Explorer). Probably when you installed Vision Builder it updated MAX, so when your installer is trying to Include MAX, its asking for the source where it was installed in your computer in this case Vision Builder.
Here you can cache the information so its not asked again, or you can download a newer version fo DAQmx, so it will update MAX and change de dependecy.
You can find more details about this issue in this KB:
KnowledgeBase 3S88PJMY: Why Do I Get A "Missing Distribution" Error When Trying to Build an Installe...
And for keeping a copy here is more info:
How Do I Stop the Missing Distribution Notification Each Time I Build An Installer?
Best Regards
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

Reverse program of application (EXE)

Hello,
I would like to know about the program security in LabVIEW. In project explorer, we can make the program automatically run by create a standalone program using create application (EXE). How about if i have the application program taken by someone, then he want to edit the block diagram or front panel of the program. Is it possible to do that or can LabVIEW reverse the application (EXE) back to normal VI or with password protected? Or it really cannot simply reverse the process.
Thanks
mfaz
CAIRO
Solved!
Go to Solution.

Raven's post is correct, if you make sure to remove the BD's from the VIs in the exe-build (this is the default setting)
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!

The report generation toolkit didn't work after the vi was build to an application.exe

I write a VI using LabVIEW Report Generation Toolkit , it really works in the LabVIEW7.1 and 6.0 enviroment. but after the VI was build in to an application.exe, the LabVIEW Report Generation Toolkit didn't work even the application runs.
thanks for your help.

You might want to follow the procedure here:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/86256a47004e16d186256a84004cb883?OpenDocument
(If the URL doesn't work, you can search for NI document ID: 2B87TVI8)
Dan

LabVIEW 64-bit - Can I build a 32-bit exe

LabVIEW 64-bit - Can I build a 32-bit exe

Hi Gary
Not at the moment - see here
You'll need to open your VI up in the 32 bit version and compile from there.
Kind Regards
Chris | Applications Engineer NIUK

After upgeade to win10 build 9926, my desktop application get wrong monitor count.

I have an application that needs to query monitor counts.
I follow the below link :
http://stackoverflow.com/questions/20261523/detect-number-of-display-monitor
It query one DeviceID. That is right.
But in yesterday, I upgrade my notebook to win10 build 9926.
It becomes to query two DeviceIDs, and second device is :
DeviceID DISPLAY\CMN1127\1&8713BCA&0&UID0
That is wrong, because I don't extend any monitor.
I also get the same result at another notebook that after upgrade to win10 build 9926.
Is it a bug in win10 build 9926?

On Tue, 27 Jan 2015 08:20:30 +0000, hatasum wrote:
I have an application that needs to query monitor counts.
I follow the below link :
http://stackoverflow.com/questions/20261523/detect-number-of-display-monitor
It query one DeviceID. That is right.
But in yesterday, I upgrade my notebook to win10 build 9926.
It becomes to query two DeviceIDs, and second device is : DeviceID DISPLAY\CMN1127\1&8713BCA&0&UID0
That is wrong, because I don't extend any monitor.
I also get the same result at another notebook that after upgrade to win10 build 9926.
Is it a bug in win10 build 9926?
Is this an application that you developed? If so, then these aren't the
correct forums to ask development related questions in. These are IT Pro
forums, not Developer forums.
You should check the support forums on MSDN.
Paul Adare - FIM CM MVP
You know you're a Unix guy when your dreams start with #!/bin/sh.

Labview 8.5 application builder .exe does not run.The same source code runs ok.

Hi,
I have an application built in labview 8.5 application builder using windows XP. I have one instrument connected in gpib and one connected to a serial port. The source code runs ok but when I build an executable of teh same code and try to run it, it doesnt run the instrument connected to the serial port. It does communicate with the gpib port. Any ideas why this would be happening?
Steven

Additional to Britoa's reply: Did you add the serial commuication (drivers) when you built the application?

To invoke an application exe built using Labview from python.

I am trying to invoke an application exe built using Labview from python.
I am able to invoke labview vi, send and receive data. But if I change the vi to exe, it doesn’t work.

This is more of Python. I can suggest you another way, if you can do those changes to your existing code.
This is what I do: If I have to communicate between 2 different platforms I use "File" as a communication medium (Simple method). So if you want to pass data to the LabVIEW code from python, write the data to the file from Python and read the data in LabVIEW and vice versa. I generally use *.ini files for this purpose.
The best solution is the one you find it by yourself

Using labview version 8 can application.exe be created for linux platform?

hi
Good morning..
I have been creating GUI for windows platform using Labview version 8.
Is it possible to create application.exe for linux platform...are there any settings that could be changed to make it work on linux platform ? or it will directly work when installer is installed in linux platform...
waiting in anticipation...
Thanx ....
Regards
yogan

You must setup a machine with Linux and install LabVIEW for Linux on this machine.
If you haven't used any Windows technics you can copy the VIs from the Windows machine to the Linux machine, open LabVIEW on the Linux machine and create the application.
There is no setting on any platform of LabVIEW to generate applications and/or installers for other platforms.
Message Edited by waldemar.hersacher on 08-05-2008 08:22 AM
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Can a Labview application EXE run on a PC with 128MB RAM

Hi,
What is the minimum requirement of the LabVIEW application exe to run on a PC. Is it necessary to have 256 MB RAM PC.
Regards,
Sowmya

See Release notes. They can be found in the support section of the website or on the install CD/DVD.
Message Edited by andre.buurman@carya on 10-30-2007 10:42 AM
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

LabVIEW 5.1.1 App Builder doesn't work on WinXP or 2k?

G'Day All,
I have a client that needs some apps written in LabVIEW 5.1.1 built into exe's, but I've found that once I install the App Builder on my Windows XP and 2000 PCs, I get "dist build app image subvi is not executable" - I've tried opening the wiring diagram to fault find, but it is understandably passworded. Has anyone come across this problem, and if so, how do I get around it?
cheers,
Christopher
Christopher G. Relf
Certified LabVIEW Developer
[email protected]
International Voicemail & Fax: +61 2 8080 8132
Australian Voicemail & Fax: (02) 8080 8132
EULA
1) This is a private email, and although the views expressed within it may not be purely my own, unless specif
ically referenced I do not suggest they are necessarily associated with anyone else including, but not limited to, my employer(s).
2) This email has NOT been scanned for virii - attached file(s), if any, are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility.
3) Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed.
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

Christopher
LabVIEW 5.1.1 is not supported under Windows XP. The first LabVIEW version that we tested and do officially support under this OS is 6.1.
On Windows 2000, you may get this error if you install the Application Builder 5.1.1 on the machine that has LabVIEW 5.1 on it. Both versions have to be the same.
I Get Errors After Installing Application Builder 5.1.1 On Top of LabVIEW 5.1
Zvezdana S.
National Instruments

How can I uninstall Labview run time engine from the machine?

I understand that Labview has not given any provision to show customized 'License Agreement screen'. Isn't it? This is the main cause of my problem. Since I want to show our own license agreement (LA) screen, I made the one using Labview. To show this license agreement screen, I first install a small application which has only this LA screen with Labview run time engine. The customer can see License Agreement Screen with Labview Run Time Engine on his machine. If My customer accepts the LA, I will install the main application further by calling another setup.EXE file.
If my customer selects 'Do Not Agree' to the LA, I will quit the installation process. Here I also want to 'uninstall' Labview Run Time Engine
from his machine since he doesn't accept License. I would like to know how to uninstall Labview run time engine from his machine?
Another way which I could think is to run the LA screen from the CD with Labview run time engine on the CD. I will start installing the main S/W to the customer's machine with LABview Run Time Engine only after he accepts License agreement. I would like to know how to run the Labview application from CD without installing run time engine on the target machine?
Can anyone suggest solution to my problem?
Thanks,
Chander

J-Tek,
I would suggest re-installing the Run-time Engine and then uninstalling it after a reboot. Also, you can download a program called Msicuu.exe (for NT, 2000, XP or Msicu.exe for 9x) to help clean up the registry for uninstalled programs.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Can't Uninstall Labview Run-Time engine 6.0

I've uninstalled Labview 6.0 however, Run-time engine is still listed under the Add/Remove wizard in windows. I've manually unistalled it successfully but, it reappears, even after reboot.
How do I uninstall it for good?
thanx,

J-Tek,
I would suggest re-installing the Run-time Engine and then uninstalling it after a reboot. Also, you can download a program called Msicuu.exe (for NT, 2000, XP or Msicu.exe for 9x) to help clean up the registry for uninstalled programs.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Uninstalling LabVIEW after an application (EXE) build

Similar Messages

Maybe you are looking for