Runtime engine installatiion aborted

HI,
I am trying to install LV runtime engine 7.1 on a user's machine and
see the error "Installation aborted, A higher version of this product
is already installed". I checked the registry, C:\Program Files and
Control Panle --> Add remove programs for any traces of already
installed versions but couldn't find any. To the best of my knowledge,
I can say that this machine does not have any other versions of LV. I
attached a picture with the error messages. I am using windows 2000 and
was logged in as administrator, when this problem occured.
My question is does anyone know if the runtime engine installation
checks any particular registry settings for information about
previously installed versions and hence does not allow the user to
proceed with the installation.
Deepak

The Run-Time Engine installer shouldn't check to see if any previous or future versions have been installed. The reason is that multiple versions of the RTE can be installed on a given computer. This is actually necessary in many cases, since applications built with a certain version of LabVIEW require that version of the RTE to run.
I haven't heard of this specific error occurring. I would recommend downloading the following site and downloading a utility called msiblast.exe. This should detect any hidden installers for NI software on your machine. Remove any that you find. You might also check out this Microsoft knowledge base on the msicuu.exe utility that helps clean up installers. This utility could help clean up configuration settings for any Windows installers as well as registry information that might be left behind.
Let me know if either of these utilities helps out.
Jarrod S.
National Instruments

Similar Messages

Cannot Install LV Runtime Engine 7.1

HI,
Some of our users are having unusual installatiion problems while
installing the LV runtime Engine 7.1.1 on win2k. Our users have
installed another application recently and in that process the LV
runtime engine was removed from their computer. So, they tried to
install the runtime engine(downloaded it from NI website) again but couldn't becuase they keep getting
the message that they are not logged in as administrator. We logged in
as admnistrator and tried installing the runtime engine again,
but the error keeps occuring and is not allowing us to install. I
searched the NI discussion forums and the Knowledge base to find
answers but did not see any that match our problem. From some of the
posts I suspect it has got something to do with Microsoft hotfixes and
windows upgrades etc.
If anyone else had seen this kind of behavior and has found a fix,
please share it with us. Any help will be greatly appreciated.
Thanks Ahead
Deepak K

Hello!
This is an unusual problem. I would first go through the add/remove
programs through control panel. Loate the "National Instruments
Software" item and select "change". See if any LabVIEW
components are there and slect to remove them. This will completely remove the
LabVIEW components. Then attempt a reinstall of the runtime engine.
If this still causes problems, you may have deleted the old LabVIEW runtime
engine in an unusual way which is interfering with later installs. If this
is the case, there are some other methods that we might be able to use to
uninstall fragments of NI software. Removing the software does not fix
the problem post back and let us know!
-thanks-
Travis M
LabVIEW R&D
National Instruments

Unable to install LV Runtime Engine 7.1.1 with LabVIEW Professional 8.5.1

I installed LabVIEW Professional Sys. for Windows (XP) 8.5 and then the 8.5.1 update. Somewhere in the original installation, LV Run-time Engine 7.1 was installed. But I need LV RTE 7.1.1. So I attempted to install RTE 7.1.1. Problem: The LV RTE installer aborts with the following message:
"Installation aborted. Newer version already installed."
Why do I need 7.1.1? I must run some commercial LV executables that were compiled with LV 7.1.1 and will not run under 7.1.

Well, I have to correct myself. MAX indicated that LV RTE 7.1 (not 7.1.1) was installed. My complied LV app indicated that 7.1.1 was not installed. I checked Windows Add New Programs and selected "National Instruments Software" I found that LV RTE 7.1.1 was, in fact, installed. So I selected LabVIEW Runtime Engine 7.1.1 and clicked Repair. After rebooting, My app works correctly. Again, MAX incorrectly displays LV RTE 7.1 (not 7.1.1). My app works, so I don't care.

Run VI method in runtime engine 2011

Is this method still valid in the runtime engine 2011?
Following this post for LV8.6
http://zone.ni.com/reference/en-XX/help/371361E-01/lvprop/vi_run_vi/
After I build my VI with the execution builder, the run VI method doesn't work anymore with the runtime 2011..?

Steve,
Ooops, indeed, I forgot to wire the error handler on this method. I get some error now when aborting the running vi (I think).
See attachment.
Attachments:
Simple OI - Top-Level VI.vi ‏48 KB

Hiding the runtime engine

I have seen postings about this issue before but still...
I'm trying to hide the LabView Runtime Engine (RTE). Basically I would like to have the whole app in one directory.
When I put the lvrt.dll and additional files in the same dir (as suggested in this forum), starting the EXE calls the Windows installer and the RTE is extracted to the usual path (c:\program Files\National Instruments\shared...).
When I abort the Installer it pops up again 3 times. After aborting 3 times the app launches and runs correctly without having installed the RTE on the system.
Is there an option to prevent the RTE installer to kick in?
(Currently running LV 7.0)
If someone can help I'll buy you a beer at your next trip to Germany!
-DB

Just having lvrt.dll and the resource files (rsc) isn't enough: copy the following files & folders into the folder containing the exe:
..\National Instruments\shared\nicontdt.dll
..\National Instruments\shared\nicont.dll
..\National Instruments\shared\LabVIEW Run-Time\ver\* (including all sub-directories)
There are a few things that, depending on whether used by your app, may not need to be included. For example:
..\National Instruments\Shared\LabVIEW Run-Time\ver\Errors
Converts and displays LabVIEW errors to the user. If you don't have this directory, errors may be displayed in a non-sensical format, or even not at all. Note: if you have custom error files (like xml onesyou've created, then put them in here).
..\National Instruments\Shared\LabVIEW Run-Time\ver\models
These are the control/indicator models - have alook through the directory, and remove those that you don't need.
..\National Instruments\Shared\LabVIEW Run-Time\ver\PlugInControls
Remove anything out of here that you don't need (eg: image control/indicators, etc)
..\National Instruments\Shared\LabVIEW Run-Time\ver\script
This is where interfaces to Matlab, HiQ and the like are kept - delete them if you don't need them
..\National Instruments\Shared\LabVIEW Run-Time\ver\lvjpeg.dll
..\National Instruments\Shared\LabVIEW Run-Time\ver\lvpng.dll
If you're not doing anything with jpegs or pngs, then you don't need these either.
That said, if you're using 7.1, then there's a whole bunch of other files in the ..\National Instruments\Shared\LabVIEW Run-Time\ver\ folder - just have a look at the names and experiment a little
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

LV 6.0 runtime engine not found with labview 6.1

I recently upgraded to LabView 6.1.
Now when I try to run an exe built under 6.02, I get an error that the 6.0 (or compatable) runtime engine could not be found.
I have the developers version of labview 6.1 installed, and the labview runtime engine 6.1 installed.
Do I need to install 6.0 runtime too? (in that case do I need 5.1 ruintime instaled too for exe's built a log time ago)?
Shouldnt the 6.1 RTE be able to run older exe's?
I could find no solution searching this web site.
Thanks
Larry Junek, Certified LabVIEW Developer

Did you install 6.1 wheer 6.0 was?
You may have lost the 6.0 RTE you did not realize you where using.
Yes you need the version of RTE that matches the app.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Runtime engine 8.6.1 on Labview 11

Hello,
I have upgraded labview 10 to Lv 11. A program that used to work on Lv 10 is giving problems now. It asks for runtime engine 8.6 ( usually gets stucked preparing the installation ). Once i cancel this process, it loads all the vi's, and it seems to work, but I can't be sure until all the devices are connected, and it can't be done until september. My question is, do i really need to install runtime engine 8.6 to make it work properly, or it can work without it?
And if I downgrade to Labview 10, will i solve this issue??
Thanks in advance!!

This is actually strange behavior because the runtime engine 8.6.1, if it is installed on the computer, should be accesible both from LV2011 and from LV2010.
What do you mean by "downgrade to LabVIEW 2010? You may have multiple version of LabVIEW on the same computer. Did you uninstall LV2010 first? If you did, then it may happened that you uninstalled the runtime engine 8.6 at the same time.
Do you really need or don't need the engine depends of your application. In any case, it should not be a problem to download the runtime engine from ni.com and install it. http://joule.ni.com/nidu/cds/view/p/id/1244/lang/en
Sergey Kolbunov
CLA, CTD

How do I determine if a VI is running in the runtime engine or LabView Development Environment?

Is there a function or VI that I can call that will tell me if the program is running in the LabVIEW Runtime Engine or if it is running in the LabVIEW developement Environment? I am using LabView 8.5.
I have a menu item, File/Exit, and I would like to call the Exit LabVIEW vi if running in the runtime engine when that item is selected. However, in development, I don't want to shut down LabVIEW when I select that menu item.
Maybe there is a more appropriate way to exit the program. However, I am looking for something elegant. I'm sure I could find some other way to accomplish the same thing, but I'm looking for a clean way to do it.
Thanks

Here is a small VI with this exact function.
Attachments:
Is EXE.vi ‏9 KB

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

Installing LabView 8.2 runtime engine on Windows 7 64-bit

We have a product built on LabView 8.2
For a couple of years, we have been distributing this product on Windows 7 64-bit systems with no trouble at all.
Today, we received a customer complaint indicating that the LabView 8.2 runtime engine cannot be installed on Windows 7 64-bit.
Our verification team has confirmed this to be true.
Interestingly, we have several Windows 7 64-bit computers with the LabView 8.2 runtime engine already installed.
How is this possible?
Has something changed in Windows that no longer allows the LabView 8.2 runtime engine?
We are confused by the fact that this appears to be a new problem and the runtime engine did, at some point, install correctly on multiple Windows 7 64-bti computers.
Any thoughts would be extremely appreciated.
Attachments:
lv_install_error.jpg ‏22 KB

No, i dont think the 8.2 installer is corrupt, but it uses the Windows Installer service, which according the image has some problems. Maybe it recently updated? It's incompatible with that old installer so you need to downgrade it? It's corrupted and needs some fix?
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

How do CVI7.0 runtime engine and TestStand3.0 runtime engine work in a test system?

I developed code modules from CVI 7.0, and test sequence from TestStand 3.0. Now I want to deploy all to a test system. Should I create distribution kits for CVI and TestStand, and install to a target PC? Do each kit include the RTE? How do the runtime engine work in a system?

hp7550,
I saw your post earlier entitled "what is a run-time engine?". It looks like this post is addressing the same issue.
To answer your questions, it is not necessary to create a distribution kit for your CVI code modules. You can simply install the CVI Run-time Engine, which you can find if you go to www.ni.com and click on the Drivers and Updates link on the left-hand side.
Then you will need to deploy your TestStand system using Tools >> Deploy TestStand System in the Sequence Editor. That tool will go out and gather all the CVI code modules your sequence calls - unless you are calling a DLL or something dynamically inside of a code module; in which case, you need to add that dynamically called DLL (or code module) to your TestStand workspace.
To install the TestStand Run-time Engine, make sure the Install TestStand Engine option is checked on the Installer Options tab of the deployment utility. You can customize what gets installed with the engine by clicking on the Engine Options.
For more information on deployment, see Chapter 14 of the TestStand Reference manual (Help >> Search the TestStand Bookshelf...).
To answer your last question a run-time engine simply gives you access to the compiled code that corresponds to the functions you used from the CVI or TestStand libraries during development.
I hope that helps.
Best Regards,
Matt P.
Applications Engineer
National Instruments

How to Detect LV runtime engine prior to showing Remote panel in browser?

I work on a web server that delivers remote panels embedded in browser windows. On new machines, the labview runtime engine needs to be downloaded and installed.
Currently, when a new user 'hits' the remote panel, the user is prompted and then downloads the component. However, the user experiences some errors that can be confusing. The first time, the remote panel is not embedded properly and the user must go 'BACK' then reload the page.
We would like to check and detect whether the LVRT engine is installed prior to posting a webpage that contains a remote panel.
What is the best way to detect whether the LVRT engine is installed on a remote computer?
Jim West

Jim West wrote:
My brain is swimming... I haven't had enough coffee this morning... There is a chicken and egg issue. As soon as I post the page, the client knows it needs to install the Labview runtime engine. However, my Labview process has already attempted to place the remote panel in the page. I get an error. I'll admit that I haven't delved into my software since there are two spawned processes involved. One process responds to the request and another lingers in memory running the remote panel until the user finishes.
From my perspective my lingering process should be sufficient to get the remote panel displayed when the RTE in finished installing but here is the catch. Installing the RTE requires a reboot, therefore the server process would need to linger in memory a long time and then would need to recoginize that a user from the same computer and login is looking for the page. Not really the way to go. I can't have a process on the server lingering waiting for a user to reboot his computer and then do something when they start running again. That process needs to die right away if the RTE is not available.
Jim
Would it be possible for this lingering process to check to see if the web server read has timed out? The default is 60 seconds, and you can change it by going to Tools>>Options>>Web Server: Configuration.
Trey B
Applications Engineering
National Instruments

Runtime engine files 8.2

Hi,
Since most users of my written program are users with "restricted right" acounts under Windows XP I copied the Runtime engine files of LV7.11 manualy by copying the
"Program Files\National Instruments\LabVIEW 7.1\Shared\LabVIEW Run-Time\7.1" files to the harddisk and run a build executable from that directory. Since this application looks in its own directory for support-files this worked fine for LV7.1.
Last week I converted my program to the LV8.2 version. When I tried to copy the RTE8.2 file in the same way as I did before, the program would start-up. It asks for a NIINI32.DLL file. When I include this file it does not return any errors, but the program doesn't start. Can anyone tell me whether their is a different way to run a exe-file build by LV-application builder by copying files manual in stead of running the RTE-installer?
Thanks in advance,

I know that NI did the run time engine to minimize space when installing multiple application. But i'm agree with you, we should have another way to build executable without the runtime engine. Some people dont know what it the runtime engine and uninstall it. afther that they just cant use the program anymore. The other reason, it that a VI use just some Kbyte and the run time engine that include almost everything, need some Mbyte.
If somebody know, please tell us......
Benoit Séguin
Software Designer

Instrument I/O assistant in runtime engine

Hello,
I currently use the Instrument I/O assistant in some of my VIs to communicate with an Agilent network analyser using SCPI commands. This works fine, and I am able to do everything I want to do (on my desktop which has LabVIEW installed).
I would like to be able to run my VIs on a laptop which does not have LabVIEW installed, using the free runtime engine. I have successfully been able to do this with several VIs that do not contain the Instrument I/O assistant.
However, I can't get any VIs that contain the assistant to work on the laptop. I have verified that the connection between the laptop and the network analyser is OK in MAX, and all the device numbering and addressing is the same on the laptop as it is on the desktop. I have even been able to get individual blocks such as "GPIB Write" to work on the laptop.
Any ideas would be greatly appreciated.
Cheers,
Dan

What version of LabVIEW are you using? For quite a while, you have had the option of creating an installer. This is the recomended way to distribute an exe. Prior to 8.x, you could include the LabVIEW run-time. Since 8.x, you have had the option of creating an installer that included hardware drivers such as GPIB, DAQmx, NI-VISA, etc. You could also download the VISA run-time. The full version of VISA should also be included on the CD you got with the GPIB board. Some of the GPIB CDs did not automatically install VISA but you can always stick the CD in and manually select it for installation.

LabVIEW Runtime engine on Windows Embedded Standard 7 P 32/64 bit?

Did anyone ever try to install and run LabVIEW Runtime engine (2011 or later) on Windows Embedded Standard 7 P 32/64 bit?
I am trying to figure out if this will work, for example on a Beckhoff CX5120 embedded PC. I will need to have some simple TCP/IP communication in order to exchange information with another PC, but nothing else, i.e. drivers, etc...
I hope someone tried to do this already. I just don't have the right hardware right now to check it out.
Solved!
Go to Solution.

As NI sells touch panels with WES7 installed here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/210551 it's pretty safe to assume they've used the RTE on WES7.
But yes, it's been done.

Runtime engine installatiion aborted

Similar Messages

Maybe you are looking for