Run time engine present

Hi all,
Does any one know how to find what version of Run time engine is installed in the PC?
Your help is greatly appreciated.
Regards,
Muthuraman S
Regards,
Muthuraman

Muthuraman wrote:
[...] Is there any possibility the exe is getting run in LabVIEW8.6 run time engine which is giving this issue?[...]
No.
I take it that the error dialog is created by Windows. 
I guess that the target pc has some settings which are not compatible to the exe. I'd first check if the UI used in the exe uses special fonts which are probably not installed on the target. Other possible things are missing dlls or other components which have wrong versions....
You can check the general functionality of your target if you build a simple exe which just uses a single VI with e.g. the standard state machine (found in the template browser).
hope this helps,
Norbert 
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Similar Messages

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

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

  • Labview Executable with VISA functions in Run Time Engine

    Hi Everybody
    I designed a gui to communicate using VISA GPIB. I created an executable for the gui. I also installed LabView Run Time Engine on the desired machine. I recieved couple of errors, for which I copied the files visa32.dll, NIVISV32.dll and serpdrv to the folder with the executable.
    I recieved the following error, ' Initialization of NIVISV32.dll failed. The process interminating abnormally.'
    Are there any drivers I should install in addition to the Run Time Engine? If so, where can I find these drivers?
    Thank you
    Jackie

    I installed NI-VISA with similar version as my development installation, and LV runtime engine. Labview still crashed.
    I noticed certain library functions in full labview that is not present in the NI-VISA + LV run time directory, such as _visa.llb etc.
    Do I need to copy these additional library functions too? Will Run Time Engine read these library functions?

  • You may not need to install the Run Time Engine...

    I know this has been mentioned before, but after a long search of the archives, I couldn't find the right person to give credit to - sorry!
    If you have a simple exe, you may not need to install the runtime engine on the target machine at all - all you need to do is include some of the engine's files with the exe for it to work. Try it out: copy the following files & folders into the folder containing your exe:
    ..\National Instruments\shared\nicontdt.dll
    ..\National Instruments\shared\nicont.dll
    ..\National Instruments\shared\LabVIEW Run-Time\your_version\everything (including all sub-directories)
    so, using 6.1 as an example, you exe's directory would like something like:
    ..\AppDirectory\MyApp.exe
    ..\AppDirectory\MyApp.ini
    ..\AppDirectory\My_Apps_DLLs,if_any
    ..\AppDirectory\nicontdt.dll
    ..\AppDirectory\nicont.dll
    ..\AppDirectory\lvapp.rsc
    ..\AppDirectory\lvjpeg.dll
    ..\AppDirectory\lvpng.dll
    ..\AppDirectory\lvrt.dll
    ..\AppDirectory\mesa.dll
    ..\AppDirectory\serpdrv
    ..\AppDirectory\models\heaps_of_stuff_in_here
    ..\AppDirectory\errors\more_stuff_in_here
    ..\AppDirectory\script\and_some_bits_in_here_too
    Take all of this data to a machine without LabVIEW or the runtime installed, and try to run the exe - all going well, it will execute without any problems. This exe distribution method can be really useful, especially when distributing autorun presentations on CD-ROMs.
    * DISCLAIMER: as far as I am aware, this method is NOT authorised or supported by NI - use it at your own risk!
    cheers,
    Christopher
    PS: I'd like your feedback: please give this posting a rating
    Christopher G. Relf
    [email protected]
    Int'l Voicemail & Fax: +61 2 8080 8132
    Aust 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 specifically 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.

    Yes, this method is not supported. However, this method is good if you wish to write your own installer for a LabVIEW Application. (Note: The method above does not install DataSocket, NI-Reports, or any of the 3D Graph controls.)
    I would still suggest running the LabVIEW Run-time Engine installer so that more than one application can use it.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • Getting LabVIEW load error code 59 using LabVIEW 2010 with a Run Time Engine.

    I use a vi compiled with a run time engine to run separate vi’s in my application directory. Once a file association is made with this exe file any Vi in my application directory is available to be loaded as needed. This is a process that has been very successful for me over the years and would prefer to continue using this process. Most of my applications are running in LabVIEW 8.6 and have moved them to 2009. First indications are in 2009 this process is still working. However, I plan to go on to 2010 before upgrading my test stations.
    In 2010 I get the error 59: “The source file’s compiled code has been separated, and this version of LabVIEW does not have access to separated compiled code.”
    The same dialog box also presents, (Hex 0x626)  “Cannot open a VI with separated compiled code in a Run Time Engine that has no access to the VIObjCache.”
    What can I do in the build that will get around this error?
    Thank you

    Thank you for the solution. I am sure this works until the next vi in the vi library gets this option selected.
     The bigger issue is I was doing something that National Instruments did not support. When I started in the days of LV 4.0 it was recommended to me that I use this method as virtually all my applications were for in house projects. This is still my preference because it gives the most versatility and allows modifications of single files rather than compiling the entire application.
    The final solution I ended up with for those who may be having the same issues. My recommendation for what it is worth, is to compile the application as an executable. This is from what I can tell the only acceptable and supported method. Using this method the problem is solved.
    I have accepted this as the solution. I still don't like it. I could list the reasons why but it is a mute point.
    Thanks again for taking the time to respond to this issue and offer the solution you found.

  • 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

  • Can't install run-time engine on Ubuntu 8.04. Get /bin/sh failed to load.

    Simply receive a message when trying to install the LabView run-time engine .rpm file that says /bin/sh failed to load (or is required, I forget exactly).  I checked, I have BASH installed, and /bin/sh is a shortcut to an executable on my machine.  Is this a bug in the installer, or is there something else I need?

    LabVIEW installation is not supported on Debian based Linux systems (of which Ubuntu is the most popular).  However, many people have had success installing to various flavors of Ubuntu.  You can search these forums using the key Ubuntu and find the problems they had and how they solved them.  If you cannot find an answer to your problem, let us know.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • 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

  • Unable to run vi with labview run time engine

    Hi All,
    I have a VI that controls and reads from an NI PXI Spectrum Analyser (5600). The VI works perfectly as expected, I can make a project of it and create a runtime application and installation with no problems, using Labview 8.6.
    When I make a call to it from Test Stand 4.1 it works lovely.
    When I change the VI adaptor in Test Stand 4.1 from development to use the LV Run Time engine 8.6 it fails to work, Test Stand gives the following dialogue (see attached).
    I have uninstalled all older versions of Labview as I've had similair issues before, I've mass compiled everything I think is associated with this VI.
    I don't really understand! And am tearing my hair out.
    The only idea I have is that perhaps there is something in one of the 5 DLLs that is causing a problem or the NI_AALBase.lvlib, NIAALPro.lvlib or NI_PtbyPt.lvlib librarys that are password locked and I presume don't get mass compiled.
    I have attached the problemVI.lvproj.
    Thanks for any advice or help.
    Matt
    Attachments:
    problem VI.lvproj ‏41 KB
    teststand.JPG ‏43 KB

    Matt,
    it sounds like you are having older versions of toolkit/driver VIs in your application. In developement environment, this works since the dev-system is capable to recompile older VIs just during loading and therefor not having issues with older versions.
    Running the VIs using the Runtime Engine, recompilation is not possible. Because every VI knows "its version", the VI will not be executable unless the RTE version matches the VI's. If the VI is older (or newer, doesn't matter), the observed error occurs.
    Please make sure that you have current versions of drivers and toolkits installed in your LV environment instead of simply copy them from older versions of LV (this would be the common source for such issues).
    hope this helps,
    Norbert 
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Run-Time Engine error

    I have created an automated test and had it running as an executable on a stand alone test computer. I updated my LabView software to 8.6.1. I just made some changes to the test and recompiled it. When I tried to run it on the stand alone computer it gave me an error about the LabVIEW 8.6.1 run-time engine missing. I thought when the project was built all the files that pertained to running it were also built into the folder. Has anyone run into this that could offer some advice.
    Thanks
    Chirs
    Solved!
    Go to Solution.

    Did you create an installer or simply build the exe? If you only built the exe you will need to install the run-time engine on the target machine. If you created an installer you can include the installation of the run-time engine as part of the installer.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • VISA Write differs between TS Development System and LV Run-Time Engine

    Hi all
    I made an application on LabVIEW to test BERs (Bit Error Rates), and I used VISA Write between two COM ports to exchange data.
    Everything works fine using just LabVIEW.
    Afterwards, I used TestStand to call my application (VI). The LabVIEW adapters from TestStand were set to Development System by default, and everything works OK!!
    Finally, I needed to disable the development system, and set the LabVIEW adapters from TestStand to LabVIEW Run-Time Engine and I notice that the speed of the data exchange between the two COM ports decreased dramatically.
    The only difference was the speed...because all the data (changed slowly in this case) arrived correctly on the other COM port too.
    The symptom was the same as decreasing the baud rate...but the baud rate and all the other configurations remained the same. The only difference was the change between Develpment System to Run-Time Engine to notice this decreased speed between the exchanged data using VISA Write.
    Any solutions for this?
    Thanks in advance
    Joao
    Solved!
    Go to Solution.

    Joao,
    you state that using the LV Developement System as execution platform for your LV code modules result in faster datatransfer between the COM ports than using the LV Run-Time Engine.
    So i am pondering: Does this refer to TS at all?
    Please check the following:
    Run you communication using a sole LV application in LV Developement System. This should be fast. Now build an executable of this application and run that one. Do you see the same behavior?
    If there is no difference in a sole LV approach, there have to be some settings in the TS approach making this slow. So please let us know:
    Are there different modules involved in that data transfer (which in fact points to the reply Christophe made)?
    What about loading/unloading options of the modules?
    How big is the hierarchy of the modules, e.g. is it necessary for the RTE to load stuff the Dev Env has already in memory due to loading a lvproj.......?
    Could you provide a simple example sequence+modules showing this behavior?
    What versions of LV and TS are you using?
    hope this helps,
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Calling a VI which uses "system exec.vi" with LabVIEW run-time engine as adapter

    Hi,
    My TestStand sequence calls a VI which includes a call to "system exec.vi". When I try to load it in TestStand and if LabVIEW adapter is set to run-time engine, I get an error message "Unable to load Vi...". If I switch the adapter to "Development system", then it works fine.
    Is there any way to use "system exec.vi" in a VI which is called in TestStand with LabVIEW run-time ?
    Thanks,
    Alex
    Solved!
    Go to Solution.

    Hi Alex,
    In you case, you are getting a -18002 error.
    The reason is explained in the following link:
    -18002 Errors in TestStand
    http://digital.ni.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252?OpenDocument
    Please have a look at the 2nd reason. This is your case.
    Hope it helps,
    Regrads
    Julien De Freitas / Applications Engineer / Certified LabVIEW Developer (CLD)
    National Instruments Switzerland

  • 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 THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71

    UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71 REQUIRES A VERSION 7.1 (OR COMPATIBLE) LABVIEW RUN-TIME ENGINE。PLEASE CONTACT THE VENDOR OF LVBROKERAUX71 TO CORRECT THIS PROBLEM
    Uninstalled DAQ and reinstalled.  MAX still throws an error. 
    Any Isead besides uninstalling 3/4 of my software?
    Merry Christmas!
    Matthew Fitzsimons
    Certified LabVIEW Architect
    LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

    To clean up your system, you will need to uninstall the LabVIEW 7.1 run-time engine, and the "LVBroker," and the "LVBrokerAux71" components using the MSI Blast utility.  To obtain this utility, please create a service request for phone or e-mail support, and contact one of our Applications Engineers about this issue.  Thank you!

Maybe you are looking for