Silent Un-Installation of LabView Run-Time 8.2.1

Hi,
Does any one of you know the silent Un-Installation command for Labview Run-time 8.2.1 application??
Many thanks in advance.
Kind Regards,
Chetan G S

If you download or have the files for the LabVIEW Run-Time Engine 8.2.1 available, change directory to that location within the Windows command prompt. Then, issue the command:
C:\location>lv82runtime.msi /h
This will launch a dialog explaining the different command line options available with msiexec. Thus, the following should be sufficient:
C:\location>msiexec /quiet /uninstall lv82runtime.msi
Peter K.
National Instruments

Similar Messages

Error on installation of LabVIEW Run-Time Engine 8.5.1: "This application has requested the Runtime to terminate it in an unusual way"

Hi,
a colleague in India cannot install the LabVIEW Run-Time Engine 8.5.1 on Windows XP. On attempting to install, an error box is shown, which says:
(window title)
Microsoft Visual C++ Runtime library:
(message box text)
Runtime error!
Program: C:\National Instruments Downloads\LabVIEW 8.5.1\Runtime Engine\setup.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
http://img529.imageshack.us/my.php?image=runtimeerrorvt7.jpg
I didn't find any relevant clues for this in NI forums. A search at Google brought me to http://support.microsoft.com/kb/884538/en-us, offering a HotFix to solve the problem. Unfortunately, the installation of this HotFix does not solve the problem.
Do you know this behavior and do you have any ideas how the problem can be solved?
Thanks in advance.
Best regards
Manuel
Message Edited by Manuel Häderle on 10-07-2008 10:41 AM
Solved!
Go to Solution.

Hi there
log in as administrator and kill all processes not needed and try again. I've seen cases where one of these free download tweak applications (like "Memory Defragmentation" and stuff like that) caused that error.
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Data Socket Server installation on Labview run-time PC

How do I install data socket server on a PC with Labview run-time licence only? Is it part of the installer?

Yes, this will install entire DataSocket software. This includes: DataSocket Server, Manager, and Help.
Zvezdana S.

LabView Run-Time Engine 2009 installation failure

Hi,
I have problem to install Labview Run-Time Engine 2009.
This error occur:
Die Installation von NI VC2008MSMs x86 ist auf Grund des folgenden Fehlers fehlgeschlagen.
Auf den Windows-Installationsdienst konnte nicht zugegriffen werden.
Die kann vorkommen, wenn Sie Windows im abgesicherten Modus ausführen oder der
Windows-Installer nicht korrekt installiert ist. Wenden Sie sich an den Support, um Hilfe zu erhalten.
(The installation of NI is VC2008MSMs x86 failed due to the following error.
The Windows Installer Service could not be accessed. That can occur when you run
Windows in Safe mode or Windows Installer is not installed correctly.
Contact your support personnel for assistance.)
I've tried to reinstall and reregistrate windows installer, I've even tried to upgrade windows installer to version 4.5
I've installed Microsoft Visual C++ 2008 Redistributable x86.
Im runing Windows XP Service Pack 3
(Microsoft Windows Version 5.1 (Build 2600.xpsp_sp3_gdr.100427-1636_ Service Pack 3))
I have no problem installing other programs, I can for example install labview runtime engine 7.1.1.
So my question is:
How to solve this problem, how can I make an installation of Labview Run-Time Engine 2009 on this computer that gives me the error described at the begining?
Best regards
Simon
Solved!
Go to Solution.

Hi,
I have already looked at that forum issue.
So I have already tried to delete all keys in regedit.
The problem is, if I continue with my installation, about 10 other new issues will appear.
And my installation will not complete, it will fail.
The installer does not install, it will tell me that the installation failed, and it will only install a few things.
Not all the things that I need to run my program.
See attached pictures ibn zip file to see some errors I receive, I only picked a few of them out.
So when I then tries to start my program I will recive the error in picture program error. (Run-time engine error)
So it's not only that the installer tells me that the installation doesn't go through, it doesn't.
Best regards Simon
Attachments:
Pictures.zip ‏414 KB

LabVIEW Run-time Engine 7.1.1 installation failure on Windows 7 SP 1 32-bit

I am attempting an installation of LabVIEW Run-time Engine 7.1.1 on my Windows 7 SP1 32-bit OS computer and the installation hangs. This happens near the beginning. Is there a compatibility issue? The window does not have any error messages. It says: "Updating System, The features you selected are currently being installed." The progress indicator blinks periodically, but does not move forward. Please help. Thanks!

I recently tried to install the LabVIEW 7.0 runtime engine on my Windows 7 (64 bit) machine to try out an old software. Ended up removing it quickly again, since any LabVIEW version I started up after that, including LabVIEW 2013 showed an installation dialog on startup about (updating installation information, please wait!).
Basically there are so many possible problems why it could fail. Apparently the runtime engine installer had played with some other NI component that he had no idea would ever exist when it was created and caused that component to always think it needed to update itself to finalize its installation. In your case it could be anything from a missing Visual C runtime version framework that the installer simply expects to be present but doesn't since Microsoft has in the meantime released about 5 versions of Visual C and doesn't install all runtime versions anymore on newest Windows. Or it could be a conflict with your hyper-duper .Net Framework 4.5.x.y that the installer does not be prepared for. Maybe that or something else was not present on your 64 Bit machine where you could install the runtime engine.
Basically the reasons for the install to fail are legion, and trying to figure it out is always more hassle than moving on and let old software be old software.

Distribute application without labview run-time engine

I read a lot of post saying if the target machine has the same run-time engine installed, then I don't need to distribute the application with labview run-time engine. Somehow this rules doesn't work for me. I have a PC installed labview 2010 development system and has run-time engine 2011 SP1. I also download the same version of run-time engine and installed it in a target PC. When I distribute my labview application, if I select to include the run-time engine in build properties, the application will be able to install and run properly in the target machine; If I don't include the run-time engine, then I wouldn't be able to run the application.
Does anyone help me on this? I don't want to always build the application with the run-time engine since it's quite big
Solved!
Go to Solution.

Could you take a look at my NI software list and let me know what labview run-time engine is really in use?
And in build properties, it actually list addition installer include labview run time engine SP1. If I includes this version of run-time engine and run the installer in target machine, it will still install the run-time engines just like there is no run-time engine installed in the target machine before.
Attachments:
NI software.jpg ‏98 KB
Installer.jpg ‏216 KB

LabVIEW Run-Time Installer

Hi,
Does anyone know if it is possible to run the LabVIEW Run-Time Installer
in silent mode?
Best regards
Magnus Nilsen

"Magnus Nilsen" wrote in message
news:[email protected]..
>
> Hi,
>
> Does anyone know if it is possible to run the LabVIEW Run-Time Installer
> in silent mode?
>
> Best regards
> Magnus Nilsen
It is simple!
Place in folder
C:\Program Files\National Instruments\shared\LabVIEW Run-Time\5.1\
lvrt.dll and ole_lv5container.dll
Do not install RT 5.1.1 because of bug in
Edit->Preferences: Tab [Front Panel]->Check box 1,2,3 or 4 -> Crash!!!

LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

I'm having a problem building an installer in LabVIEW 2011SP1.
It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
Now when I try to build the installer I get "The build was unsuccessful."
Possible reasons: Error generating preview for My Application 3.1.7.
Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
*** Error: An internal error occurred for which the cause is unknown. (Error code -41)
*** Error Details:
Error in MDF API function: _MDFCommon_GetNextLogMessage
Error in MDF::GetInstance - MDF static instance is not initialized!
*** End Error Report
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.

I do have the LabVIEW 2013 discs but didn't install it.
I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
So now I need to distribute 2 runtimes with my application?!?!
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

Installer Error of LabView Run Time Engine 6.0.2 "premature"

I cannot Install the LabView Run Time Engine on a Computer which runs on Windows 2000.
The Installation breaks on start with the Error Message: "Installation ended premature, because of an Error!"
Does anyone know what to do is ?
Thanks for Help

It's rather difficult to guess why since the error does not give any more information, but there are a few things you can try. First, if you are installing from a CD, try downloading the installer to your desktop first and then run it. CD-ROMs can sometimes run slower that the installer and this can cause problems. Also, check to see what other NI software may have been installed on this machine and determine if any of it could conflict with the 6.0.2 Run-Time Engine. Just possibilities but hopefully they can get you going!
J.R. Allen

LabView Run-Time Installation Failure

Hi
I am trying to install the LabVIEW Run-Time Engine 20112 under a Windows XP Professional 32-bit SP3 Versin 2002, but every time I open the executable file, the comand prompt returns the message "Program too big to fit in memory". The machine has 2Gb of RAM memory, with only 670Mb in use. The Hard disk has 17Gb of free space. I have also installed on the computer the LabVIEW Run-Time Engine 8.6.
Could you support me in the installation ?
Tanks
Download Link:
http://joule.ni.com/nidu/cds/view/p/id/2534/lang/en
Executable file name:
LVRTE2011f3std.exe

Recargable wrote:
Hello!
I tried installing the last version of the Windows Installer and the problem persisted.
First I was installing from a mounted ISO image as if it was a DVD inserted for the virtual Windows XP, so I tried installing from a copy of the ISO image in the virtual hard disk, which failed too. Then I tried installing the Windows Installer. Copy the installation files out of the ISO image didn't go well either. Finally, I copied the installation files to a usb flash memory, I installed the Virtual Machine Additions in the virtual Windows XP (because is necessary for reading usb flash memories) and I could perform the installation from the flash memory.
I can't yet understand why the OS recognises the executable files correctly in this last case and not in the others. They are the same files!!
Thanks!!
Totally strange. I have no ideas on that one, but glad you got it to work.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Integrating an NI-USB 8451 driver and Labview Run-Time Files in an installation package of a .vi application

Hello,
I've built a .vi which uses the NI-USB 8451 device (please see http://sine.ni.com/nips/cds/view/p/lang/en/nid/202368), and I would like to create an installation package to be used on a costumer's PC, which has no Labview installed on or a driver for this device.
I would like to have this installation as a completely stand-alone setup, so that the user could take this file and run it, and have the driver to the 8451, the run-time files for the Labview application installed by themselves, and have the .exe file working on a completely "clean" PC.
How can I integrate it all in one package ?
Thanks,
Michael.

Nice hearing from you again, Ipshita
I do not call any dll's currently, but am using the driver of the USB device, NI-USB 845x, version 1.0.1
Now, I would very like to make the use of my application, by another user, with no Labview or this driver on his PC, as simple as possible.
I just thought that maybe I could create an .EXE file with some Labview created dll's, which this executable would use, and spare the need of the 845x Driver or Labview Run-Time library prior installation. I could be wrong.
What should I do ?
P.S.
Meanwhile, I've been playing with the Application Builder and tried to create an installation with the Driver and the Labview Run-Time.
It had started the compile, but stopped with the following pop-up window: "Locate the 'NI-845x Software 1.0.1' distribution. Labview needs to copy a component installed or updated by the distribution..."
(Attaching the pop-up window below)
What is it looking for and where can I find it ?
Thanks,
Michael.
Attachments:
Installation_pop-up.JPG ‏20 KB

Pdfcreator invokes LabVIEW run-time engine installer!

Okay, so I'm a desktop tech, know little about LabView, but can at least install it. We also use pdfcreator on our desktops. For some reason, however, whenever pdfcreator is used (for ANYTHING, not just LabView stuff), a windows installer fires up, "please wait while windows configures NI LabVIEW Run-Time Engine 7.0." The installer proceeds, then gets stuck while trying to find the msi. Well I don't HAVE the proper MSI apparently, because my version is 7.1.1! When I put in the 7.1.1 Run-Time CD (the only one I have) and point it to the msi it seems to be looking for, it still fails (apparently due to different versions).
So first, why is pdfcreator invoking this installer in the first place (they seem to have nothing to do with each other!)
Second, why is the installer looking for the Run-Time for 7.0, instead of 7.1.1?
Help!
Thanks,
Wiltony

Well, I fixed it. I eventually used the NI Software Add/Remove item, and chose "repair" for NI LabVIEW run-time 7.0, which called for the appropriate 7.1.1 device driver discs (strange). After it completed, everything worked fine.
Wiltony

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Executable not working - Looking for LabVIEW Run-Time Engine

This has been one of those days.
I'm trying to create my .exe file to place onto another computer. I've done this before with success. But that was then and this is now.
I believe I have all the files I need in my LLB, and I believe I did my application distribution correctly and I believe I built the DLL correctly. But when I took the resulting .exe file and placed it on another computer and attempted to run it, it gave me the error message: "Unable to locate LabVIEW Run-Time Engine. Program requires a version 7.1 (or compatible) LabVIEW Run-Time engine. You should have already realized this, you moron."
Anyone have any idea where I went wrong or what step I might have missed? This has been a crazy, non-stop, massive brain fart of a day and I can't seem to remember what I'm missing here.
Amateur programmer for over 10 years!

Hi.
Whenever you want to use executables or .dll's created with LabVIEW you must make sure that the LabVIEW runtime engine of the SAME version as the LabVIEW version used to create the files, is installed in the target computer.
There are basically 2 ways to get the run-time engine installed on a computer:
1. (the one I prefer): Download the correct version of the LabVIEW run-time engine installer from www.ni.com/downloads, or more specifically from
http://digital.ni.com/softlib.nsf/websearch/369618104E25B08E86256F54006A4E2F?opendocument&node=132050_US
for the latest one. Once you have the installer for the run-time engine, just install it in the target computer. I prefer this option because the run-time engine is installed independently, so if you then uninstall your program, the run-time engine remains.
2. Create an installer for your program that includes the run-time engine. To include the run-time engine, when you are creating your application, go to the "installer settings" tab, click on "Advanced" and make sure there is a checkmark on "include LabVIEW run-time engine". This way when you install your program in the target computer, the run-time engine will also be installed.
Just as a note, any computer with LabVIEW on it, will also have the run-time engine.
Good luck.
Alejandro

Unable to locate the LabVIEW Run-Time engine

Using LabVIEW 2011, I have built an executable and installer including the LabVIEW Run-Time engine. I built the app on a 32-bit system. I'm deploying it to a Windows7 64-bit system. When I ran the installer, rebooted, then tried to run the app, I got an error messsage stating "Unable to locate LabVIEW Run-Time Engine", stating that the LVRTE 2011 was needed to run the app, and asking if I want to download from NI. I have tried downloading the RTE and re-installing it, but when I try, I get an error message from the installer stating that there is a newer version of the RTE already installed, and the installer exits! I have tried un-installing the application, but have had no luck removing the RTE. Now I'm stuck. The re-installed executable application says it can't find the RTE, and the RTE installer says there's a later version already installed!
I can't go forward or backwards!
Prior to running the installer for this app, I had a working LVRTE for 2011, and was running some other executable LabVIEW programs on the target box. However, since this new application had additional components not included in the original install of the RTE, I built the new installer which included the additional components. Once I ran that installer, my problems began.
In my frustration, I've tried downloading from NI both the 32 and 64-bit versions of the RTE, and installing them. I realize that the app was built on a 32-bit system, so the 32-bit RTE SHOULD have run it fine, but didn't.
At this point I have removed the 64-bit RTE using the NIUninstaller. I believe I need to completely remove all 32-bit RTE components and start over, but I have not been able to. The 32-bit RTE does not show up in any un-install utilities I've found.
What could be causing this problem, and how do I get past it??
Thank you.

One thing I did discover in my struggles is that the RunTime engine on the target box needs to be based on the environment of the development box. So if you built the app on a 32-bit machine, you would need to install the 32-bit RTE, even on your 64-bit target box.
The RTE Uninstaller might not show up in the Windows Add/Remove Programs utility. In my case the 64-bit RTE uninstaller showed up, but the 32-bit did not. The NiUninstaller (C:\Program Files\National Instruments\Shared\NIUninstaller) did list both RTEs for uninstalling, but still didn't get me past the problem.
I was finally only able to get past the problem by doing a system restore to a point in time prior to my changing of the RTE.
Good luck.
Dan

Silent Un-Installation of LabView Run-Time 8.2.1

Similar Messages

Maybe you are looking for