LabVIEW 8 Run-Time Eninger on 2011 Startup

Hey All,
Weird issue here where the LabVIEW 8.2.1 Run-Time engine trys to install/configure itself everytime I start the 2011 development environment. Has anyone ever seen this?
It quickly goes to a prompt asking for...
"The Feature you are trying to use is on a network resource that is unavailable."
Clock OK to try again or enter an anternate path to a folder containing the installation package 'lv82runtime.msi' in the box below.
Why would it be asking for this at all? It tries to install itself 3-4 times before finally launching the development environment.
Regards,
Ken

Hi Ken,
That is odd behavior, there could be a corrupt file in you run time install. I would suggest repairing your LabVIEW 8.2.1 Run Time Engine. Refer to the document below for repairing NI software.
How Do I Uninstall or Repair National Instruments Software?
http://digital.ni.com/public.nsf/allkb/AC6ED75D3D93375686256E8E00245F0D?OpenDocument
Tim O
Applications Engineer
National Instruments

Similar Messages

Is Labview 2012 run-time on TPC-2206?

When I go to Uninstall programs on my TPC-2206 I see Labview Run-Time 2009, 2010 and 2011. Labview 2012 Run-Time does not show up in the list. When I download and install it, I still only see the above plus a generic National Instruments program. The new TPC-2206 touch panels we have show a generic National Instruments program in the program list, but I don't know how to find out if that is Labview 2012 Run-Time. I can't find anywhere on the NI website that lists what Run-Time software is already loaded on the Touch Panels.

I did try running a Labview 2012 executable after I had put up the post. It did not work, so I knew that Labview 2012 Run-Time was not on it. I put Labview 2012 Run-Time on it, but afterwards when I looked in the Remove/Change programs list in the Control Panel, Labview 2012 Run-Time was not in the list of installed programs. There was a generic National Instruments program, but there was nothing identifying what NI program it was. This was the real problem, because all of the earlier versions of Labview Run-Time were clearly identified in the installed programs list and Labview 2012 Run-Time was not. There is no way to know if Labview 2012 Run-Time is installed except to try to run a Labview 2012 executable.

Labview 2010 run-time engine silent install

I am having trouble with installing the run-time engine for LabVIEW 2010 with the silent option.
I am using the minimum version of the run-time engine.
Before I used the LV7 run-time engine. Then I could install it silently using LVRunTimeEng.exe /qb!
In LabVIEW 2010 the run-time engine is no longer a single file but a directory that contains the installation files. There are two files that can be used to launch the installer Setup.exe and LV2010runtime.msi.
Setup.exe does not seem to accept any command-line arguments. LV2010runtime.msi however accepts the command-line arguments and can be installed silently.
Now my problem is that I am building a windows installer using a third party application and it is only possible to launch exe files after the installation completes. Before I could launch the LVRunTimeEng.exe /qb! to install the labview 7 run-time engine but now when I have upgraded to labview 2010 I cannot do the same for Setup.exe.
My question is if it is possible to use the Setup.exe file to install the Labview 2010 run-time engine (minumum) silently?

Setup.exe runs a number of other .exe files during its execution. This article looks like it will allow you to run setup.exe silently by supressing all messages and windows:
http://digital.ni.com/public.nsf/allkb/878FC4C374013ADF8625733D00688F67

LabVIEW 8 run time

Am upgrading from 7.0 to 8. Is Run Time compiled with the .exe during
the build? Does Run Time install with the .exe on the target machine?
Are there any hoops to jump through during the build, or target
installations?
Instructions for 8 Run Time seem to be slim.
newbieDLD

The run-time engine isn't really compiled with your built application since it's a separate program. You can, however, include the installer as part of your build so that when you deploy your application you will also distribute the run-time engine with it. From the LabVIEW documentation:
If you use the Application Builder to build an installer for an application or shared library, you can add the LabVIEW Run-Time Engine to the installer build. From the Additional Installers page of the Installer Properties dialog box, place a checkmark in the NI LabVIEW Run-Time Engine checkbox in the National Instruments Installers to Include listbox.
Generally, the run-time engine is a separate install, and the installer for it is included on the LabVIEW CD, or you can download it from NI: http://digital.ni.com/softlib.nsf/websearch/1F1EBEA6D03A67E6862570A400531F97?opendocument&node=13206...
-Saverio

LabView and Run-Time

Hello, I have written a vi in LabView 7.0 and I would like to install this vi on other computers for which we do not have a license to run LabView. I understand the way around this is to download Run-Time from the National Instruments website. This I have done (downloaded and installed the latest run-time software from NI website) but I have no idea how to run my vi in the run-Time suite of programs. Which program should I use and so on. Are all sub-vis supported etc.
Nevica
Message Edited by nevica on 08-12-2009 09:11 AM

You also need to check to make sure you actually have the Application Builder, depending on which "edition" of LabVIEW you have. The Professional edition had the Application Builder included. The Full and Base did not, and needed to be purchased separately. I think this still applied going back to 7.0. If you don't have the Application Builder then you will need to check with NI to see if you can still get it.

Install Labview DSC Run Time without SQL Express

Hi
I have an application of DSC run time that I tested successfully but now must be installed on a server and my client does not allow install an instance of SQL Server Express because he are already using the Enterprise version. What should I do to not install the SQL Server Express incorporated in the DSC Run Time and use the SQL Server Enterprise already installed on the server?

Hello Jdrendon
Did you try to install your application on a PC with an instance of the Enterprise version?
Maybe another instance of SQL will not be installed in this case, because you already have a later version installed.
The second possibility is just uncheck the option to install the SQL Server Express when you are installing your application.
Let me know if it is possible and if it solve your problem.
Plínio Costa
Application Engineer
National Instruments Brazil

Which command I can use to exit from a subvi without exiting from labview in run-time?

Similiar to 'Exit Sub' command in Visual Basic.

> Similiar to 'Exit Sub' command in Visual Basic.
There isn't a command to do this. Since LV is a dataflow language, it
is important that all the data be delivered to the output terminals.
BASIC is a procedural language, with all sorts of control flow commands
like this, and if you are using a functional language or a dataflow
language, you simply focus on getting to the end of the function. If
you are in a while loop, you terminate the while loop by the value going
to the conditional terminal. If you are in a For loop and need to exit
early, perhaps it should have used a while loop. If there is code in a
normal diagram that you sometimes do not want to execute, it should
probably go in a case structure.
The other reply has some good suggesti
ons in that you probably have a UI
or a sequence that you want to exit out of. Organizing your code so
that you are in a button handling state or exiting state will help you
organize how you think about the transitions between states. On the
other hand, there lots of examples and user contributed VIs to look at.
I'd recommend you get comfortable with a few of them since the state
machine is just one programming tool, just like the loop and case
statement that it is built from.
Greg McKaskle

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

Why does my LabVIEW Run-time server return the message "source does not exist Last UI message: Start Execution"?

I am trying to build a stand-alone application on a target pc for which I have built a LabVIEW server that TestStand can use as an adapter.
In order to do this, I searched this site and found the topic: "How do I build and Use the LabVIEW Operator Interface as a LabVIEW ActiveX Run-time server?" After following the procedure to the letter, I ran the testexec.exe file as instructed and loaded my sequence file. As soon as I try to "Single Pass" or "Test UUT" I get an error which says "source does not existLast UI message: Start Execution". This error appears when running the testexec.exe file on the target pc or the development pc.
I have found though, th
at if I open the Operator interface through the Start: Programs>National Instruments>TestStand>Operator Interfaces>LabVIEW then the sequence file runs without these errors.
Any ideas why this is happening?

Hello Robroy,
The KB you mentioned explaines how to build the LV Operator Interface (OI). So, I assumed you built the LV OI and also configured the LV adapter to use the TestStandGUILVRTS server without problems.
The error you are getting may be due to missing VIs. In other words, the LabVIEW OI may not be finding all the VIs your sequence is calling.
In order to deploy sequences that call VIs, you need to first run Tools >> Assemble VIs for Runtime Distribution. This tool gets all the VIs your sequence needs and saves in a separate directory.
For more information, you may check the TestStand User Manual chapter 17, it describes how to distribute TestStand and sequences.
Regards,
Roberto Piacentini
Applications Engineer
National Inst
ruments
www.ni.com/ask

Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installation package for Run-Time Engine 7.0

I recently installed LabVIEW 2013 on a computer (running Windows XP 32-bit). The machine also has LabVIEW 8 installed, which is what I was using prior to upgrading. I opened a VI that was created in LV8 and then saved it and all its subVIs in LV2013. Now when I open the VI in LV2013 and try to run it, a window pops up asking me to find the "lvruntimeeng.msi" installation package for LabVIEW Run-Time Engine 7.0. If I cancel that dialog box and the subsequent message stating that the installion files were not found, the VI appears (at least from intial inspection) to run normally.
I closed LabVIEW, downloaded Run-Time Engine 7.0 from the NI website, and tried to install it, but I received a message saying that it is already installed (as I had suspected). How can I determine what part of the VI and/or its subVIs is trying to make use of Run-Time Engine 7.0? Alternatively, how can I get LabVIEW to instead use the Run-Time Engine 2013 that was installed when I upgraded to LabVIEW 2013?
Solved!
Go to Solution.

Bob_Schor wrote:
Are you running your VI from a Project? If so, you can look at Dependencies and get an idea what "dependent" VIs you might have. There may be "something old" in your LabVIEW 8 code that has been superceded in 2013, but still "hangs around" -- if you can identify it, you can probably replace it with its "more modern" equivalent.
If you do not have the VI in a Project, you can simply open LabVIEW, create a new blank project, and add your top level VI to it. If all of your relevant VIs are in a single folder, add the entire folder. Now look in Dependencies.
BS
Yes I am running the VI from within a LV Project. After some more searching in the NI Knowledgebase I was able to fix the problem by using the following procedure:
1. Use the Measurement and Automation Explorer to uninstall Run-Time Engine 7.0
2. Restart the PC
3. Open the project, close the project choosing to "save all"
4. Restart the PC
5. Re-install Run-Time Engine 7.0 using a file downloaded from ni.com
6. Restart the PC
7. Open the project, close the project choosing to "save all"
8. Open the project and run the VI. No more messages about LabVIEW trying to find Run-Time Engine 7.0.

Does CVI install the LabVIEW Run-Time Engine?

Hello,
running the NI Update Service suggests to download a 226 MB patch for the LabVIEW 2012 Run-Time Engine... (all I installed knowingly was CVI2012)
--> How can I check if the computer has this engine installed, what is the file name to search for (and is it needed by CVI)?
Thanks!
Solved!
Go to Solution.

Hello,
1) You can use Measurement And Automation Explorer (MAX) to see the National Instruments Softwares installed:
2) Some CVI softwares use the Labview runtime.
By example, when you use the CVI Menu: Help / Find Examples... , you launch NIExampleFinder.exe which uses the labview runtime:
3) When you install the NI-VISA library, the software C:\VXIPNP\WinNT\NIvisa\NIvisaic.exe is also installed. This utility is a Labview Software.
I think it's difficult to avoid the Labview runtime on a computer with NI softwares installed...

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

Can I use the labview run-time engine 2010 with my LV 2012 program?

Hi all,
I will receive the new Labview Developer Suite 2012 DS2 in a few days and
I am wondering if it is possible to run LV2012 programs on the LV run-time engine 2010 or is it necessary to update all my clients from run-time engine 2010 to 2012?
Stay Hungry, Stay Foolish
Solved!
Go to Solution.

Hi Benjamin,
You will not be able to use the LabVIEW 2010 run-time engine with LabVIEW 2012 applications. Versions of run-time engines need to correspond with the version of LabVIEW that you have installed.
The following links direct you to our download pages for the run-time engine:
The 32-Bit Run-Time Engine can be downloaded from our website as can the 64-Bit Run-Time Engine, depending on which version of operating system you, use by clicking the link under "Standard Download".
Hope this helps.
Marshall B
Applications Engineer
National Instruments UK & Ireland

Sequence in Labview Run time error

Hello,
When i want to execute my sequnce with run-time LABVIEW, i have sequence error indicate VIs broken. This error appears only when i launch the sequence with an labview executable. If i use, testexec.exe or TESTSTAND this error doesn't appear.
I used LABVIEW 2009, TESTSTAND 4.2.1 and try with LABVIEW2012 et TESTSTAND2012. Same problem.

Hi EricGau,
Did you try building a deployment package through the TestStand deployment utility?
deployment
You can get detailed process for creating a deployment image in the TestStand reference Manual.
You should ensure all the VIs you used and their dependencies are compiled in an identical and correct version. (either by using the Mass compile tool of labVIEW: tool>>advanced>>Mass Compile) or creating an .llb which automatically mass compile everything.
Normally creating an llb resolve the issue you are experiencing.
I presume the broken VIs are VIs you used as code module and not VIs implemented and used in the UI source code?
There are a few reasons that a LabVIEW vi could fail to run using the Run-Time engine:
Your LabVIEW vi contains subvi's that were not saved in the same version of LabVIEW, prior to TestStand 2010 all your LabVIEW vi's needed to be saved in the same version of LabVIEW so they all used the same RTE. Try mass compiling your LabVIEW VI's to verify they are all saved to same version.
Your LabVIEW VI may contain code that needs to be compiled in order to run using just LabVIEW's Run-Time engine. You can build the VI into a Source Distribution, this will compile the VI allow it to run with just the LabVIEW RTE.
Best regards,
Romain DUVAL || Application Engineer Specialist ||Certified LabVIEW Architect (CLA) || Certified TestStand Architect (CTA)
National Instruments France

How can I use undo and redo with run time menu?

Hi..I try to built my own menu for graphic programming. How can I use undo and redo in labview with run time menu?

filozof-
During runtime, by default, LabVIEW has undo/redo data changes under the edit menu. This will undo/redo changes made to controls during runtime. If you want a more extensive undo/redo (custom for your application), you are going to have to do quite a few things
1) Create a custom runtime menu (Edit>>RunTime Menu) and place your own undo/redo controls on it
2) Keep an action history in your program
3) Catch the Shortcut menu event for your custom undo/redo controls
4) Reverse the last action in your histroy when you catch the event
This method would allow you undo entire operations (like resize, move, or whatever kind of functionality you are building into your application) unstead of just undoing data changes.
Xaq

LabVIEW 8 Run-Time Eninger on 2011 Startup

Similar Messages

Maybe you are looking for