Runtime Engine Redistribution Options

I noticed that when developing Crystal Reports for Visual Studio 2010, one must install the Crystal Reports runtime engine in the client machines in order for the reports to work.
According to the documentation, the runtime engine can be installed by executing any of the following files as appropriate:
CRforVS_redist_install_32bit_13_0_1.zip
CRforVS_redist_install_64bit_13_0_1.zip
What I am curious about is if this is the only way to install the runtime engine or if there are other ways. For example, what if someone purchased the full version of Crystal Reports 2011? How would you deploy the runtime engine to the client computers in this case? Is the runtime engines for the full version the same as the one that comes with Visual Studio 2010 runtime engine?
Most importantly, if there are two engines, what would happen if both engines are installed in the same computer?
Thanks.

Hi Rene,
As far developing the Reports with CRVS2010 is concerned you would require Visual Studio 2010 and then install the following
http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_13_0_1.exe
The other you mentioned should be used when deploying the application. You can learn about it here.
Crystal Reports for Visual Studio 2010 - Deployment
If you purchase CR2011, you can design the reports, but it does not contain .NET runtime. You would have to use CRVS2010 runtimes. Do look at this.
So, what's up with CR 2011 and .NET SDK - actually, any SDK?
Two engines shouldnu2019t be a problem as each of them would have different version.
CRVS2010 (13.x) and CR2011(14.x)
Thanks,
Saurabh
Edited by: Saurabh.Pathak on Nov 3, 2011 8:30 PM

Similar Messages

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

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

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.

What is needed to run a .llb file using a runtime engine?

I would like to run a .llb file on a computer that doesn't have LabVIEW installed. Is that possible? If so, what is needed to do that? I have tried to install a runtime engine, but can't get it to work. The .llb file is currently running on LabVIEW version 6.0 on another computer, but I don't know with what version of LabVIEW the .llb file was created. The computer on which I would like to run the .llb file has Windows XP.
Thank you for any help!

Mathan wrote:
You have to create an executable with the help of project explorer.
The user has LabVIEW 6 (as he noted in the original message). LabVIEW 6 has no project explorer.
To OP: I am assuming the LLB contains a top-level VI that can be run. Otherwise, this is a moot question. If you want to open the VI and view it, then you need the development version on the target machine. If you want to run the top-level VI in the LLB then you must create an application that you can copy over to the other computer. The other computer requires the LabVIEW Runtime Engine in order to run the executable. To build the application you need the Application Builder. This is a separate product from LabVIEW, but was included with certain LabVIEW editions.. If you do not see a menu option for building the application then you do not have the Application Builder. You would need to contact your local NI sales office to see if you can still buy a copy. I doubt you will be able to, but it's worth a try.
EDIT: Sorry for the duplicate info. I got sidetracked while composing the message, and did not see the additional responses from Dennis.
Message Edited by smercurio_fc on 08-18-2009 09:51 AM

NI VISA Runtime engine

When "Building" a LabVIEW program containing NI-VISA sub VI's (e.g. to communicate with USB), I have had problems getting the "Built code" to find my NI VISA devices, even though the NI VISA USB Drivers are correctly installed on the "target machine".
(The "built" code WILL run if the target machine has a LabVIEW installation on it, including NI VISA)
So - will the NI VISA runtime engine be automatically included in the "Build" (Because of the NI VISA sub VI's), or do I have to specify this myself - And how?
Thanks. Peter.
Solved!
Go to Solution.

You specify installing the NI VISA Runtime Engine when you build and installer for your built executable. Look on the Additional Installers tab of the Installer Properties Dialog Box. The NI VISA Runtime Engine should be selected automatically but if it's not you can uncheck the Automatically select recomended installers checkbox and select any other installers you want to include in your install.
If you're not using an installer then no runtime engines are installed and you'll have to do that manually on each machine you copy the executable to.
This all assumes LabVIEW 2013. The selection process is slightly different in earlier versions but all the options are still available.
Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome

NI Developer Suite 8.2 / LV Runtime Engine 8.2 vs 7.1.1

I have NI Developer Suite 8.2 and have installed LabVIEW v8.2 from it onto my development computer. I have converted a LabVIEW 6.1 application to 8.2 and am now setting up an installer build for the application.
When setting up installer build properties, I find NI LabVIEW 7.1.1 Runtime Engine, NI LabVIEW Run-Time Engine 8.0.1, and NI LabVIEW Run-Time Engine 8.2 listed as additional installers that can be included in the build.
Wanting to use the latest and greatest for my application, I have selected Run-Time Engine 8.2 for inclusion in the installer.
Upon testing the installer, I find Runtime Engine 7.1.1 installed, not 8.2.
I checked the development computer (Control Panel->Add/Remove Programs->National Instruments Software) and found only Runtime Engine 7.1.1 installed. I then uninstalled LabVIEW 8.2 and reinstalled it, hoping to be able to specify which runtime engine to install, but there is no option in the installation process for runtime engines.
My question is: what happened to runtime engine 8.2? Why can't I get it installed on my development computer? If it doesn't exist, why is it listed in the installer build properties as an installer that can be included? Is it vaporware?

Hi Igk,
On your development machine, the LabVIEW RTE 8.x will not appear in Add/Remove Programs because it is an invisible MSI Installer. The installer is invisible because other applications (LabVIEW Development environment, for example) are dependent on the RTE. Uninstalling the RTE would cause problems for all the other programs with dependencies, so the option to remove it is not there. If you uninstall all the programs that depend on the RTE, the RTE will be uninstalled with the last program. You can see in the attached image that I don't have LV RTE 8.0, or 8.0.1, or 8.2 in Add/Remove Programs, but it is listed in MAX Software.
If you run this LV installer on a clean PC(without the LV development environment), I havn't tested for sure, but because the application installed depends on the RTE, the RTE still probably won't show up in Add/Remove Programs (but your application will). You can verify the RTE's existance by checking the <Program Files\National Instruments\Shared\LabVIEW Run-Time\8.2> directory and verifying the lvrt.dll version is 8.20.x.xxxx. Also, when the application runs, you will know the RTE exists. Also as TonP mentioned, you can use MAX to verify its installation.
As a side note, I would generally avoid running LV built installers on a development machine that already has LV. Installing the RTE (or any other NI installer) from a LV custom installer will change its installation source stored in the registry from the LV CD where it was originally installed from to the installer that you built. Future repairs of the RTE will then look for this custom installer rather than the original source. If that installer disappears or changes, repairs or uninstalls become more difficult. I usually set up a test machine to test my LV built installers.
Cheers,
Spex
National Instruments
To the pessimist, the glass is half empty; to the optimist, the glass is half full; to the engineer, the glass is twice as big as it needs to be...
Attachments:
820RTE-Installed.jpg ‏127 KB

DSC runtime engine problems

Hi,
I recently started a project which involves DSC runtime engine. This being my first contact with runtime engines, i obviously ran into some problems. Hope someone can shed some light. Here goes: I developed a project on my work laptop on which I have LV / DSC 8.6 installed. The project is then built into an EXE application and then run on a desktop computer with DSC runtime engine.The desktop computer receives data from a PLC through an OPC server (which is not NI OPC server). At first, I imported a csv file containing the list of variables in my project with the correct path of the OPC server from the desktop. When I ran the EXE application on the desktop, I got an error (PSP Led was red) saying that the variables could not be read / written. This was because the variables were not declared in the Distributed System Manager. And so my first question is this: is there a way to import my list of variables from a csv file or something similar, and if so, how can i achieve this? Because so far, all I was able to do was to manually enter only one variable at a time in the Distributed System Manager, and after about 50 of them I decided I would really hate to enter almost 800...
My next question regards the Citadel Database. As I told you before, I entered a few variables in the system manager and played with them for a brief amount of time. I set them T / F, I got the correct readings from OPC server, my PLC leds light up, the works. Now I wanted to see my actions in the Citadel DB, but when i ran MAX, there was no Citadel DB, only Default DB, and I could not find any of those variables which I entered and chaged states. Is there a problem with the Citadel DB not showing up? Am I not declaring correctly the variables in the System Manager? (i followed the help directions to the letter). Anyone has an idea as to why I cannot see the varaibles in my DB?
And now for a final problem.. In the LV front panel, i have some boolean buttons which are set to switch when pressed Mechanical Action. When I have the PLC connected sometimes when I press a button, it remains stuck on the TRUE state, thus screwing up my logic scheme (e.g. for a feed mill conveyor motor I have two buttons - start, stop. If i sometimes press the start button and it gets stuck, i can no longer SHUT DOWN that conveyor, which is really a big problem. I found a so-called 'fix' - right click on the stuck button and select Reinitialize to default value, but I was looking for an answer to understand this problem, not a silly little fix).
Hope I have been clear enough and you have not got tired of reading so much,
Cheers,
Sabin

Hi Andrew and thanks for the reply!
I don't think I deployed the library file, because I didn't know exactly how to do it. In the Source Files Property Page on Build Specifications I only selected VIs. I never selected lvlib files, so this may be the case. On the Source File Settings I saw that .lvlib files had the property Include if referenced and I thought that was the property which deployed the library. I will change the build specifications at once and keep you updated, but it could take 1 or 2 more days, because the computer with DSC runtime is in another city, and I have to get there first maybe tomorrow.
I have several buttons set on Mechanical Action Switch Until Released. They are all Shared Variables which are connected through OPC server to memory locations in the PLC CPU. In my LV Block Diagram, they are NOT connected to anything. They are just located in a While Loop, to get their state. The preffered action is that when I press a button on my Front Panel, I get to change a memory location in my PLC and then something happens in Ladder Logic. So, the boolean values are just there, in my Block Diagram, alone and not connected to anything. Do you have an idea as to why I get that kind of behaviour (I mean the buttons get stuck on True state)?
And finally, someone told me that the Citadel 5 might be missing because of incorrect option checking at install. However, I remeber that on the desktop, I installed the DSC runtime engine FULL INSTALL, I mean I checked each and every tick box, everything, examples and the like. One thing I was told was to insert the install CD once again and perform a re-install. I will of course try this, but let's not consider this for a second. Do you have another idea as to why the Citadel DB wouldn't show up?
And no, in the EXE Build Specifications, I did not check the option Enable Enhanced DSC Run-Time support. What does it do? Could you please elaborate?
Looking forward to your answer,
Sabin

2012 missing runtime engine in newly created build

in 2012, when i complete a build, it creates an .exe file. when i run the .exe on a new computer, it says " runtime engine is missing". what option / button do i select to add the runtime engine to the build so everything is in one .exe, which makes it easier for our customer support team when dealing with customers that replaced their laptop?

Additional Installers >> NI LabVIEW (xxx) Run Time Engine
http://digital.ni.com/public.nsf/allkb/E09BA0E2F31D304F86256A640070058E

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.

Runtime Engine VISA Treiber in EINEM Installationsschritt - wie ?

Folgendes Problem:
Mein Programm benutzt den seriellen Anschluss. Damit das funktioniert müssen sowohl die Runtime Engine als auch der Visa-Treiber installiert werden. Beim Visa Treiber 3.01 soll man sogar noch eine fehlerhafte Datei per Hand austauschen - Wie bring ich das Ganze in die vom Application Builder erzeugte Installation ?
Man kann ja kaum dem Kunden zumuten, 2 Programminstallationen durchzuführen und dann noch eine Systemdatei manuell zu patchen..!

Just an idea for a workaround:
-Include the VISA Install files as support files into your main install package.
-In the installer options you can start a program after installion, so it should be possible to start the VISA installation
-For the patch... maybe that might work with a script (.bat) file that you start for the installation and replacement ? But then you shouldn't reboot after Visa installation and do this reboot in the script.
Henrik
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

Using LV2009 to produce EXEs for Runtime Engine 8.6

Hi,
I am currently running LabVIEW version 8.6. However, having purchased this less than a year ago, I think I am eligible to upgrade to v2009 for free.
At the moment, if I produce an EXE file using the Application Builder, my colleagues are able to run this on their machines using the LabVIEW Runtime Engine version 8.6.
If I upgrade to LabVIEW 2009, will all my colleagues who use the runtime engine also have to upgrade to the Runtime Engine 2009, or will I have the option to build an EXE file that is compatible with version 8.6 of the Runtime Engine.
Many Thanks,
Dan
Dan
CLD

There are no option for build "8.6" compatible application from LabVIEW 2009 (other than save for 8.6 and build in 8.6).
For LabVIEW 2009 - builded application you will need according version of the Run-Time Engine.
Important point, that Run-Time Engine version 2009 will not replace version 8.6. It means, if you have PC where Run-Time 8.6 installed, and after that on this PC you will install Run-Time 2009, then you can run both 8.6 and 2009 - builded applications.
Andrey.

Customizable Runtime Engine

Hi,
I am using LabVIEW 8.6 and I am interested to understand how to customize the LabVIEWRun time engine. Basically to shrink its size.
I just create a sample program and installer with and without Runtime Engine.
The VI and the projec is attached.
The Sizes are,
VI         ->      6.9 KB ( Just a UI with a loop)
EXE                                      -> 151.0 KB
Installer without Runtime Engine    ->   10.4 MB
Installer with Runtime Engine ->   74.7 MB
I understand the Rutime engine includes the support for all the LabVIEW features (Web service, trace, tdms, etc).But while distributing the application developed in LabVIEW we may need the support for only the features the Application developed/configured for. Right?
Though transfering a 100 MB is not a problme now a days, I am just wondering, how it can be customized.
Thanks,
Pandiarajan R
Certified LabVIEW Architect
Attachments:
RTE.zip ‏122 KB

Pandiarajan wrote:
I understand the Rutime engine includes the support for all the LabVIEW features (Web service, trace, tdms, etc).But while distributing the application developed in LabVIEW we may need the support for only the features the Application developed/configured for. Right?
Though transfering a 100 MB is not a problme now a days, I am just wondering, how it can be customized.
Besides the options then you create the installer no. I think NI could have done it, but they do not dare. If the installer was more modular it would have resulted in a lot of extra support work for NI. As people hate to read read documentation. It is much more convenient to phone NI support and yell at them. So NI has taken the all or nothing approach. As a self defense. And I can not blame them. But I have to admit a modular RT setup would have been nice.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Installazione silenziosa RunTime Engine

Salve,
avrei la necessità di fare una installazione "silenziosa" del run time engine 2014 SP1 e seguendo le indicazioni che ho trovato sul sito national a questi due indirizzi non ci sono riuscito; o meglio faccio probabilmenteun errore che non riesco a vedere e sistemare;
http://digital.ni.com/public.nsf/allkb/643587ADF69756DF86256B4D00720DC6
http://digital.ni.com/public.nsf/websearch/188FE05BA8933F4486256BC300708527?OpenDocument
In allegato ho messo uno screenshot del risultato del test che ho fatto usando il RunTime Engine 2009 SP1...
Grazie

Ciao MF01,
puoi provare a fare partire l'installazione da riga di comando:
What Are the Options With a Command Line Install for the LabVIEW Run-Time Engine for Windows?
http://digital.ni.com/public.nsf/allkb/173DA5B72D02560686256DF30081D73F?OpenDocument

Runtime Engine Redistribution Options

Similar Messages

Maybe you are looking for