Missing vi.lib in 2012 LabVIEW Run-Time files

Hello

I have a problem running under RT of VI in LabVIEW 2012.

Our system consists of several independent modules that are open and run from a VI Manager. VI paths to modules are read in a VI Manager .ini file.

We create a single executable file (RT Launcher) who takes the path of the VI Manager as an argument (attachment: RT Launcher.png).

The RT Launcher is placed in the... 2012 as the LabVIEW.exe \National Instruments\LabVIEW dossier.

The RT Launcher is called from the CLI.

"C:\Program NIUninstaller Instruments\LabVIEW 2012\RT Launcher.exe" "C:\Workspace\Labview\Manager.vi."

This will run the Manager.vi in the runtime environment and the Manager.vi will open the .ini file and run a Module VI.

By calling the Launcher.exe RT from the same folder as the LabVIEW.exe, search paths should be the same.

The system has worked well in LabVIEW 2010.

The VI Manager opens with a broken arrow and the errors indicate that void vi.lib screws are missing (attachment: errors.png Manager VI)

I know that there is code LV2010-> LV2011-> LV2012 compiled cache object and separate questions, but simply could not figure out how to get around this problem.

Can someone explain the difference and how to solve the problem?

Thank you

Hi Morten,

I just sent you an e-mail (before I saw your post) with some other information related to this.

About the reproduction looks that you have included a palette in your source distribution file (mnu), that will not work (sorry for not seeing this before).

Could you try to see if it was unintentionally included in your dependendies or whatever it is? The behavior of mnu files is also something that changed from 2010 to 2011, so if you run with the old project of 2010 there could be some bad dependencies. (We recommend always to create a new project when migrating a LabVIEW project to a newer version).

There is a little more information about the error you see everything by creating the distribution source here:

How can I include .mnu files in a built LLB?

http://digital.NI.com/public.nsf/allkb/051F1533145089A1862578B80060D93B?OpenDocument

Best regards

Anders Rohde

Technical sales engineer

National Instruments Denmark

Tags: NI Software

Similar Questions

  • LabVIEW: error building Installer 2011SP1: LabVIEW Run-Time Engine 2013 missing 3 dependencies?

    I'm having a problem of construction of an installer in 2011SP1 of LabVIEW.

    It has been a while since I tried to build an installer but it used to work properly and building executables still works fine.

    Now when I try to compile the installer, I get "generation failed."

    The possible reasons: error generating preview for my 3.1.7 Application.

    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_GetNextLogMessageError 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 is that I'm using LabVIEW 2011SP1, I don't even have installed LabVIEW 2013, not even the runtime.

    Where is the problem? Why is he still complain about LabVIEW 2013? Anyone seen this before?

    Troy,

    This behavior makes me assume that you updated certain components from the past. There are drivers of OR who use LV components (e.g., AFAIK the DAQmx of Test panels).

    Update you things? If Yes, why don't you LV 2013 RTE installed as it would be necessary for full functionality of the driver?

    Norbert

  • ??? Insert the "NI LabVIEW Run-Time Engine 7.1.1.

    OK everyone, I'm "dead in the water" when launch LabVIEW 2014 SP1 after a long night of installing updates to Developer Suite 2014 DS2 SRL 2015 DS1 SRL

    Search Forum has this old thread

    http://forums.NI.com/T5/LabVIEW/error-1334-in-LabVIEW-run-time-engine-7-1-1-Setup-when-launching/TD-...

    Since 2008

    NOTE: at least its looking for a CD ROM is not a floppy disk!

    Hooray!

    I've recovered from that.  And Yes, I'll tell you how that you can do it yourself if this happens to you:

    From the control panel select programs and features, then National Instruments software.

    Scroll to "LabVIEW Run - Time Engine 7.1.1" and select Repair

    You will need the following:

    • Device drivers OR August 2014
    • C:\ProgramData\National Instruments\Update Service\Installers\NI_20150630_0736
    • NEITHER Developer Suite 2015 Encarta software
    • Patience
  • Can I run two separate versions of the LabVIEW Run - Time Engine on a PC?

    Hello, I am curious to know if anyone knew if it is possible to install and use the two separate versions of the LabVIEW Run-Time Engine on a PC?  I have currently 2009 runtime engine installed on a machine, and I wanted to install the runtime for 2011 as well. I know that you can run two separate versions of the LabVIEW program on the same machine, but what about the Run-Time Engine?

    Thank you!

    No problem at all. I currently have the engines of execution for 8.2, 8.6, 2009, 2010 and 2011 on my computer. Multiples are no problem at all. Go ahead and load.

    Rob

  • Unable to locate labview run time engine

    Hi all

    I have a problem while trying to run a simple labview software on a Tablet PC.

    My development machine is under win 7 64 bit with labview 2010 sp1 10.0.1

    My computer is a win 7 32 bit based tablet.

    I installed labview runtime engine TEN 2011 standard 32-bit sp1 but I get the following text: «unable to locate labview run-time engine...» "

    I tried to install sp1 64-bit of the 2011 standard RTE because one of the items suggested, but windows is not allowing to install 64-bit applications...

    Should which version of the Runtime I install!

    You did not say, but I'm assuming that you are using LabVIEW 2010 sp1 32 bit to develop and build the application.

    You can include the 2010 sp1 Runtime when you build the Setup program, or you can download it (here) and install it separately.

    (The runtime version must match the development system, so time to run from 2011 will not work. Even the 2010 (non - SP1) could cause problems)

    Kobi Kalif wrote:

    I tried to install sp1 64-bit of the 2011 standard RTE because one of the items suggested, but windows is not allowing to install 64-bit applications...

    Can you tell me what position suggested to install an operating time of the wrong version of 64-bit. That makes no sense at all! Please provide a link.

    (You can only install the runtime on a 64 bit OS, 64-bit, and he will agree only if the application has been developed in 64-bit LabVIEW to the same version.)

  • VI LabVIEW Run-Time Engine adapter server configuration

    I want to connect to use the desktop execution trace toolkit to debug LabVIEW code modules using the adapter runtime TestStand.  How can I configure Server VI using LabVIEW VI in the LabVIEW Run-Time for TestStand engine adapter?

    Have you tried to create seqedit.ini (really .ini) or even in the directory of the executable that you use for the TestStand UI?

    -Doug

  • LabView Run - Time Engine 2009 installation failure

    Hello

    I have problem to install Labview Run - Time Engine 2009.

    This error occurs:

    Die Installation von NI VC2008MSMs x 86 ist auf Grund of the following Fehlers fehlgeschlagen.

    Auf den Windows-Installationsdienst konnte nicht rarely werden.

    Die kann occurrence, wenn Sie Windows im abgesicherten Modus implement oder der

    Windows-install extension installed ist nicht. Wenden Sie sich an den Support, um Hilfe zu receive.

    (The installation of the NC is VC2008MSMs x 86 has failed due to the following error.

    The Windows Installer Service could not be accessed. That may occur when you run

    Windows in safe mode or Windows Installer is not correctly installed.

    Contact your support team.)

    I tried to reinstall and reregistrate program windows installation, I tried to upgrade the installer from windows to version 4.5

    I installed Microsoft Visual C++ 2008 Redistributable-x 86.

    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, for example, can I install runtime labview 7.1.1.

    So my question is:

    How do to solve this problem, how can I make a Labview Run-Time Engine 2009 installation on this computer which gives me the error described at the beginning?

    Best regards

    Simon

    Now I have solved my problem.

    The solution was to raise and to build my code in Labview 2010.

    But the question of the installation contains yet to install LabView Run-Time Engine 2009.

    I don't think it's associated Windows Installer, because I can install everything on my computer in addition to LabView Run-Time Engine 2009.

    I can even install LabView Run - Time Engine 7.1.1 and LabView Run-Time Engine 2010.

    So, my solution was to jump using LabView 2009 and install LabView 2010.

    Best regards

    Simon

  • Impossible to uninstall LabVIEW Run - time Engine 2013

    I have a PC that had both the LabVIEW Run-Time Engine installed 2013 and 2013 LabVIEW development environment.  I uninstalled the 2013 LabVIEW development environment, and now the executable files will not work.  They say that the Run-Time of 2013 is not installed.  However, execution 2013 is listed in MAX.  It does not appear in the list of available software to uninstall, so I can't uninstall and reinstall either.  When I try to run the installer from the runtime of 2013, it is said that the runtime is already installed.  It seems that I am stuck with a corrupted installation of Run-Time?  Is there anyway to remove completely the execution so I can reinstall it properly?

    Thank you

    I thought about it.  I managed to uninstall the runtime engine by following the instructions here: http://digital.ni.com/public.nsf/allkb/F4B8D92A304E4A7B862577460072002F

  • LabVIEW run time version

    My CVI application must have the engine LabVIEW to run installed to run so I would check a program is installed at the start of the program.

    Now, the question isn't just "How can I get the version of the runtime LV?", as differently from CVI there may be more than one LVRTE in the system, so I have to either check all installed RTEs or at least find out later (which makes another question come to mind: can a module developed on a version specific LV can be run with a more recent RTÉ?) If so, why for more than one installed TEN?)

    Thanks to anyone who can help me in this matter,

    Hello Roberto,

    first of all, the LabVIEW (differently from the CVI) runtime is not retro-compatible (as explained here), so that an application requires a version of RTE corresponding exactly to the LV development environment, in order to work properly.

    If you need to programmatically check the LV TEN versions are installed on the PC, you could enumerate folders in C:\Program NIUninstaller Instruments\Shared\LabVIEW Run-Time, such as a folder for each version exists.

    Otherwise, you can access your application registry keys by checking in HKEY_LOCAL_MACHINE > SOFTWARE > National Instruments > LabVIEW Run-Time installed versions.

    I hope that the suggestions would help!

    Bye!

    Licia

  • Standalone Mac App LabVIEW - include Visa & LabvIEW Run-time

    Hi all

    I used LabVIEW for more than a decade, but only for Windows, just enter in LabVIEW for mac, please pardon the ignorant questions.

    I am developing a project very simple stand-alone deployment that must Run-time LV and NI Visa. My project uses a simple USB-Serial device that I talk with Visa. I used this link to condition the LabVIEW execution with my application. I think I need NEITHER Visa driver package as well. I don't know how to do this. Someone has experience racing drivers with stand-alone apps for LabVIEW under mac? Thanks for your help.

    Hi SK8.

    Unfortunately there is no way to add the option to install on the MAC, you said, that you can create the package to install the LabVIEW runtime engine and the application, but in order to install drivers OR Visa, he will have to be installed separately.

    Kind regards

  • Execution of VI using LabVIEW run-time

    Hi Ppl,

    Is it possible to use the LabVIEW run the VI execution engine. If yes how to invoke the runtime engine. Are there available active x servers comes the runtime?

    Thank you

    Sirot

    Hello sirot,.

    There is no kind of COM wrappers offcially announced by NI de LVRTE, I searched how the test bench put in place that and found documentation in this regard in 'TestStand 4.2.1\Components\RuntimeServers\LabVIEW\readme.txt. They said some procedures to register the run-time engine, may be it could give an idea, and I'm not sure how it could help you in your progress.

    AshwiN,

  • Error-18004; Access to the DLL of the LabVIEW Run-Time Error engine. TS 4.2.1 / LV 2010

    When I try to run a VI that is reentrant in an execution at the same time, I get this error.  The details of the error is: LabVIEW: the method or property is not supported in this version of LabVIEW.

    This is performed under the LV 2010 Simple operator Interface.  The TestStand engine is version 4.2.1 with runtime adapter 2010 LV.

    If I save to an earlier version to LV 2009 SP1, then assign the adapter TS 9.0.1 (2009 SP1), it works.

    Can anyone reproduce this error (bug?)?

    you have the latest updates for TestStand using LabVIEW 2010?

    http://digital.NI.com/public.nsf/allkb/7D728B70F167CE088625776E00582C7B?OpenDocument

  • Error occurred during deployment of TS and the LabVIEW run-time engine only

    Hi all
    I'm new to Teststand deployment.
    Now, I want to deploy a program to clean install with SP1 2012 Teststand engine, LabVIEW 2012 SP1 Runtime, VISA 5.2 DURATION.
    My file in the sequence is empty. (In fact with a label only)
    But I got "Internal error code - 12 making an installer... ", and" MSI error code: 110 ".
    Attachment is the newspaper.
    Any Suggestion? Thank you.

    Thanks to KateB.

    Now I find out why an error occurred.

    I installed LabVIEW 2012 first, then crushed with LV 2012 SP1 but no uninstall.

    I think it makes Teststand to be comfused or maybe something conflict.

    Now I install LV 2012 or LV 2012 SP1 only. It works very well.

  • How to install LabView Run-Time 2011 silently without removing daqMX?

    I'm trying to silently install LabView 2011 execution using the Agent HP Client Automation, formerly RADIA.  I tested successfully, however, the systems that installed daqMX have, I find that the silent installation program removes daqMX automatically.  Is there a command line argument or register defining who can defeat this behavior so that daqMX remains installed when the silent installation program is finished?  Thank you very much for your help!

    Hey EricJay,.

    I'm not very familiar with the Agent, HP Client Automation, but the silent installation should not automatically uninstall the DAQmx drivers. You can compare the process HP Client Automation Agent uses with a silent installation using command-line arguments, as described here. Another possibility could be any conflict check that the HP Client Automation Agent performs. As described here, we do not recommend installing DAQmx drivers until LabVIEW or LabVIEW runtime engine are installed to prevent contradictions or missing references. If HP Client Automation Agent is to detect these potential conflicts so we can uninstall the DAQmx drivers for conflict prevention. I hope this helps!

    -Ryan S.

  • Error 1335 during installation of NI LABVIEW Run time engine 2009

    Hello

    When installing Labview 2009, I get the following error.

    Error 1335: The file 'mib100.cab' required for the installation is damaged and cannot be used. This may indicate a network error, error reading from the CD-ROM, or a problem with this package.

    I tried to install the software using 2 different CD-ROMs, and hard drive. I also uninstalled software OR previous and tried to install Labview again.

    Screenshot of error during the installation of the hard disk is attached.

    Thanks in advance,

    Hyacinth D

    The installation was successful, after replacing the DVD drive.

    Thank you!

    Corinne

Maybe you are looking for

  • CPU fan broke on Satellite A215-S7444

    Hello My Satellite A215-S7444 CPU fan stopped working which causes my CPU become very hot. After 5 minutes of idle my laptop turns off which makes it almost useless to my laptop.After reading a few forums, I decided to disassemble my laptop to check

  • How to pass variables between Labview and Teststand

    It is probably a trivial question, but I'm new to TestStand. All I'm doing is updated to a variable in Labview and then pass this value in a local variable Teststand. A simple test that VI is attached. I get no error and it seems correct, but when I

  • programs to take a long time to open

    My programs are open to slow down, I just cleaned the disc?

  • How to remove Microsoft Security databases

    trying to remove microsoft security esstenials my coumpter but can't find it in the Add box and remove the screen how can I get rid of him so I can get a new anti virus

  • Print cartridges: refer to the documentation for the printer.

    First of all, what kind of error is this? It's like breaking a leg and the doctor would say "your not in good health." Information: HP photosmart C5280 All-in-one printer/scanner Connected to Windows 7 64-Bit enterprise Edition (I suggest using busin