What is "LabVIEW Run Time Engine"?

I'm trying to find the differences between two computers that I'm troubleshooting.  One of them is my development system which has the whole Development Suite installed, and the other is a test station which has LabVIEW 8.0 Evaluation Version installed.  When I was looking through the list of programs in my development system (in Add/Remove Programs), I found a program named "LabVIEW Run Time Engine" and the size is 0.11 MB that is not in my test station.  I thought all the NI components are installed under "National Instruments Software" including the Run Time Engine...
Does anyone knows what this is?
See-Ming

The Run Time Engine is a library of routines that a compiled Labview program needs to run on a system that doesn't have the development environment.  It is similar to Visual Basic's vbrun.dll, which compiled VB programs need to run.
As far as I know, the run time engine gets installed whenever you install any Labview development environment.  This engine is usually only necessary when running a Labview program compiled to an exe format.  Both the exe and the run time engine can be installed on another computer so that the program can run without having to buy another development package for that computer.
The runtime engine is called LVRT.DLL.  Search for it.  For version 7.1, the run time engine is in C:\Program Files\National Instruments\shared\LabVIEW Run-Time\7.1\lvrt.dll
- tbob
Inventor of the WORM Global

Similar Messages

  • 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/369618​104E25B08E86256F54006A4E2F?opendocument&node=13205​0_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

  • Unable to locate labview run time engine (lab view 8.5)

    Hello I have a problem whit the labview 8.5 installer. I have created I project with included a .vi file (a simple panel wich control a serial port, with parameters (baud rate, stop bits, ...)), then I have created an application for this file (.exe) and then the installer (I have included the labview run time engine 8.5). When I run the setup.exe  I have the following error message:
    Unable to locate labview run time engine, the application require a labview run time engine 8.5 or compatible...
    What I'm missing??
    Thanks
    Maurizio

    are there one other reasons why it would not work.  I have asimilar problem.
    I intsalled version 8 of run time engine and acrtivated software.  Now I am trying to run compiled application provided to me by third party.
    When I click on application it says
    Unable to locate LV run time engine
    Test server requires a version 6.0 or compatible LV engine.
    How do I know if the engine I installed and activated is running and is it supposed to be able to execute a program which is expectin rev 6 of the rund engine?

  • Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

    With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
    -install using the plugin
    -install using LVRTE.exe
    -install after rebooting the server
    But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
    Is there any compatibility issues with the new Run-Time Engine 6.1 ??
    Thanks for your help
    Cyrille

    Cyrille,
    What is the error that you get when trying to install the run-time engine?
    Are you installing it from the LabVIEW CD, or did you download it from the web site?
    To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
    Also, try running the installer from the command prompt window, and use the following syntax:
    setup.exe/l*v
    This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
    Thanks
    Zvezdana S.
    National Instruments

  • NI LabVIEW Run-Time Engine + TCP/IP

    Hello, Anybody knows how to activate TCP/IP service on PC with standard NI LabView Run-Time Engine installed. If I trying communicate with server from my PC (LVRTE) its works correctly.   However, when I am trying interchange client and server applications it appears with error 1.  Probably I need to add some settings to *.ini files on PC with LVRTE? --- Alex  

    <Alex> wrote:
    Client/Server applications are communicate via standard TCP/IP VIs. I have tried to add 3 line as you wrote to server.ini, but it's didn't help
    As I indicated, the lines are only applicable to using the VI Server. You had not indicated whether you were using the VI Server or just the TCP/IP VIs. At this point we need a better explanation of what you're doing. Specifically:
    What does this: "If I trying communicate with server from my PC (LVRTE) its works correctly." mean? What is the "server"? What's it running? What do you mean by your "PC (LVRTE)"?
    What does this: "However, when I am trying interchange client and server applications it appears with error 1" mean? What is the "interchange client" and the "server applications". Reading this implies you have more than one application running on the "server", whatever that is.
    Seeing some code wouldn't hurt either.

  • NI-LabVIEW run-time engine interop 2010 failed to install

    Hi,
    While installing Labview 2010 (32 bit) I got an error message:
    NI-LabVIEW run-time engine interop 2010 installation has failed with the following error:
    Error 1935. .... (see the .ppt for screenshot if interested)... HRESULT 0x8002802F
    I googled HRESULT 0x8002802F and found a page that said that this error is usually b/c of a missing/corrupt entry in the registry: file %windir%\system32\mscoree.dll, and that "repairing the highest version of the .NET Framework on the system will correct any problems resulting from this error."
    I have verified that mscoree.dll is not present, and I don't have the .NET Framework installed on my system. SO, I have the following questions:
    1) do you concur with the advice given on the page referenced re: the reason for the error;
    2) If so, should I install .NET Framework, and what do I then need to do in LabVIEW to tell it that the .dll is now present?
    3) If your opinion is other, what do you advise?
    Cheers
    Attachments:
    Labview Installation error.ppt ‏227 KB

    Hi Luke, 
    After doing some research, there are two possible solutions.  
    1) According to a KB, it could be your antivirus. You may want to try to turn off any spyware blocking software such as Ad-Aware, Norton, etc and try the installation again. 
    2) Another customer had the same error, and they got it working by installing .NET 3.5 from Microsoft's website and then installing LabVIEW again.
    Hope one of those options work for you!

  • MAX giving error - Unable to locate Labview run-time engine

    I have LV 7.1 and 8.5.1 installed on a WinXP pc. No problems until now.
    I installed some support software for a LabJack  interface, which required LV version 6.1 run-time, so I let it install that.
    I now get the error whenever I run MAX:
    "Unable to locate the Labview run-time engine. LVBrokerAux71 requires a version 7.1 (or compatible) Labview run-time engine...."
    After closing the error boxes, MAX seems to work fine. Both versions of Labview also work. I uninstalled run-time engine 6.1 and re-installed version 8.5.1, but that made no difference. I tried to install run-time version 7.1 from the msi file but it would not let me because a later version of the run-time is installed.
    What is LV Broker? Why does it not accept version 8.5.1 run-time engine? Is it possible to have 2 versions of the run-time engine installed, and if so, how?

    Dear CDancer
    Thank you for contacting NI. First of all, you can have as many versions of LabVIEW run time engines you want loaded on your computer without a problem. LV Broker is installed by all drivers that uses LabVIEW testpanels like DAQmx does. In your case it seems that the LV Broker installation is corrupted or has failed. This can be rectified by overwriting the files in the specified directory listed below:
    C:\Program Files\National Instruments\Shared\LabVIEW Broker
    Your directory should look like the screenshot I have attached; labelled LV Broker Directory View
    I have attached a ZIP File that will replace the LV Broker directory. Please try replacing your files with these if different to the screenshot and let me know how you get on. Many thanks.
    Many thanks for using the NI forums and I look forward to your reply.
    Kind regards
    David
    Applications Engineer
    National Instruments UK
    Attachments:
    LV Broker Directory View.JPG ‏57 KB
    LV Broker.zip ‏413 KB

  • Error 1334 (in LabVIEW Run-Time Engine 7.1.1 setup) when launching VB6's IDE

    What's going on here?  I have LabVIEW 7.0 and Visual Basic 6 installed on this Win-XP computer.  When I open VB6, I always get what looks like a Windows Installer error:
    First, it asked me for the location of "lvruntimeeng.msi", which I located for it.  The next progress-window says:
    NI LabVIEW Run-Time Engine 7.11
    Please wait while Windows configures NI LabVIEW Run-Time Engine 7.11
    Finally it fails with this error-message window:
    NI LabVIEW Run-Time Engine 7.11
    Error 1334.  The file 'NIMDFManifestFileId.53736431_DBEC_4582_B072_2F1F0A2C4EA6' cannot be installed because the file cannot be found in cabinet file 'lbruntimeeng_mft'.  This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
    [OK]
    The two windows repeat twice each time I launch VB6's IDE, and that causes a long delay.  What can I do to prevent this error?
    Message Edited by citizenDAK on 04-23-2008 01:34 PM

    Yes it occurrs every time I launch VB6.
    For a long time now, at least many months.  It's not every day that I need to open good old VB6.  I was hoping it'd just 'go away' but it hasn't.
    I don't know what changes lead up to it.  LOTS of things have been updated, security-patched, etc...  (It is XP.)  I've even un-installed the runtime, then re-installed it when I kept getting the same prompt.  Don't have any idea why, I was hoping you could tell me from the specific file named in the error.  (Google didn't find it for me, and neither did searching ni.com)
    p.s.,  Sorry I left out a decimal and copy/pasted it several times...  should've said "NI LabVIEW Run-Time Engine 7.1.1"

  • Can I run two separate versions of the LabVIEW Run-Time Engine on one PC?

    Hello, I am curious if anyone knew if it is possibly to install and use two separate versions of the LabVIEW Run-Time Engine on one PC?  I currently have the 2009 Run-Time Engine installed on one machine and wanted to install the 2011 Run-Time Engine as well. I know that you can run two separate versions of the LabVIEW program on one machine, but what about the Run-Time Engine?
    Thanks!
    Solved!
    Go to Solution.

    I'm guessing this is a bug that NI needs to fix.  I see no reason you shouldn't be able to install the run-time engine of an older version.  I'd be interesed in if it allows you to install the older development environment, which also includes the older run-time engine.  There are some command line switches for NI installers as mentioned here:
    http://digital.ni.com/public.nsf/allkb/C361087EE9F20810862577850073128E
    I wonder if there is a force install option.
    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.

  • 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

  • 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 Engine

    Hi ,I have used Application Builder to make EXE file from my source files but I have noticed it is not possible to use this EXE file in another PC without LabVIEW because LabVIEW run-time engine is needed so I tryed Installer
    but I have few questions and I would really appreciate if u help me
    1- What kind of source files should be added to the installer?  I would like to install an EXE file and Data folder  so do I need to first use the application builder to make the application then add all the application files(EXE and Data folder) one by one to the installer or Do I need to add my LV files to the installer and LV make exe and data folder again for me?
    2- I am using LV2010 and I would like to add run time engine for 2010 so I checked the box for LV2010 run time engine but many options are included to this engine like NI TDM,NI SSL etc ... and after making the installer I noticed the size of my file was so big (109MB) while I want to make a small size installer for email   .Is there any chance to reduce the size of installer by unchecking some of the options?
    Many thanks

    You build an executable first, then you build an installer for the executable. When building the installer, simply add the executable and LabVIEW will figure out what else is needed in the typical case.
    If you want a small installer, don't include the run time engine. Instruct your customers to donwload and install the free runtime engine from here.
    Make sure they install the "standard", not "minimum" version. Also make sure they install the 32 bit version if your LabVIEW 32 bit, even if they install it under a 64 bit OS.
    LabVIEW Champion . Do more with less code and in less time .

  • Installing LabVIEW Run-Time Engine 8.5.1

    I want to run saved VI's from one computer with LabVIEW 8.5 Professional Development (8.5) on another computer using the Run-Time Software.
    After installing LabVIEW Run-Time Engine 8.5 (LabVIEW85RuntimeEngineFull.exe from http://joule.ni.com/nidu/cds/view/p/id/861/lang/en), do I need to do anything else before running a saved VI created in LabVIEW 8.5 from another computer? I install the program, but the only options under programs-national instruments are:
    -data socket
    -License Manager
    When I installed LabVIEW DSC Run-Time System 7.1 on the same computer there was an shortcut under "programs-national instruments-" to LabVIEW DSC Run-Time System 7.1, which is what I need but for the Run-Time Engine 8.5 instead.

    Joseph is correct. The run-time engine is only for "stand-alone" executables created with the Application Builder (included in the Professional version or higher, or can be purchased separately if you have the Base package). To run a vi in the development environment, you need one of the LabView packages.
    Message Edited by Edjsch on 05-12-2008 01:48 PM
    Message Edited by Edjsch on 05-12-2008 01:48 PM

  • Uninstalling LabVIEW Run-Time Engine 6.1

    Hi, I get an error message during uninstalling NI LabVIEW
    Run-Time Engine 6.1:
    Error 2727 NETSCAPEPLAGINSDIR
    How can I fix this problem?

    Armen,
    Here is my guess as to what happened:
    1. You had Netscape installed on your machine.
    2. You installed the LabVIEW Run-time Engine which installed the remote panel plugin into Netscape.
    3. You uninstalled Netscape.
    4. You are trying to uninstall the LabVIEW Run-time Engine.
    If this is correct, then try installing Netscape again, uninstall the LabVIEW Run-time Engine, and finally uninstall Netscape again. If this does not work, then please submit a phone request at http://www.ni.com/ask to get help with MSIBlast.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

Maybe you are looking for