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.

Similar Messages

Using Win2000 Group Policies to distribute runtime engine

I have a Win2000 domain and would like to distribute the 7.1 runtime engine using Group Policies for a group of computers in the domain. I created the policy called LVRuntime and tried to add the 7.1 runtime MSI file to the policy under ComputerConfiguration\SoftwareSettings\SoftwareInstallation however I get the error message:
"Add Operation Failed. Unable to extract the deployment information from the package. Run validation on the package to ensure the package is correct."
MS has an article on this if the package is already installed on the system or if you are using a GPO of a different version, but neither are the case. I am creating the policy right on the Domain Controller just as I have many other policies like it.

Hi Jordan,
The MSI deployment through group policies is not supported for LabVIEW RTE. Although MSI is used as the outer layer, we use our own technology inside.
Regards,
Ankita A.
National Instruments

[HowTo]Use Pane method "SetScaling" in runtime engine

Hi all,
In LabVIEW help it is write that "Set Scaling Mode is available in Run-Time Engine (in read and write)...
I try to use this method and :
- 1 - With teh first code (see ScalingFirstMethod.png)
* It's working well in LabVIEW execution
* It's NOT working in RunTime Engine execution (you obtain error 1044 --> VI is locked)
- 2 - With teh second code (see ScalingSecondMethod.png)
* You don't have error in LabVIEW execution
* You don't have error in RunTime Engine execution
--> But in the 2 cases the mode set is NOT apply !!!!!
If anyone as a solution... This method is essential for my UI, so...
Thanks in advance,
OJO
PS : Config : LabVIEW 8.2.1 + Windows XPMessage Edité par ojo le 06-26-2007 12:35 PM
Olivier JOURDAN
SAPHIR | Certified LabVIEW Architect | Topaze on NI Community | LabVIEW add-ons on NI Community | Follow me on Twitter
Attachments:
ScalingFirstMethod.png ‏39 KB
ScalingSecondMethod.png ‏49 KB

Hi, thanks for the answer.
Like I wrote in my first post (cf attachment nammed ScalingSecondmethod.png) I already tryed to add open ref... Unfortunatly scaling mode is not applyed...
I add the two examples, if you find a workaround...
Regards,
OJO
Olivier JOURDAN
SAPHIR | Certified LabVIEW Architect | Topaze on NI Community | LabVIEW add-ons on NI Community | Follow me on Twitter
Attachments:
ScalingFirstMethod.vi ‏19 KB
ScalingSecondMethod.vi ‏25 KB

Cannot start exe in runtime engine

Hello, I know there is a thread about this issue, but it did not help me, so I start a new thread.
Link
Here my problem:
The message of the MessageBox is:
in german: "Das VI ist nicht ausführbar. Zur Behebung der Fehler ist das LabView Full Development System erforderlich."
in english: "This VI is not executable. The full development version of Labview is required to fix the errors"
Under LabView development environment (LV2011 SP1), it works, under RunTime Environment (on same PC ! ) it does not.
I use this options:
for all dependencies:
I use these settings:
And this are the removements:
For logs while loading EXE, see attached file.
Any Idea why it does not work?
Thans in advance
Eugen Wiebe
Bernstein AG
CLAD - Certified LabView Associate Developer
Solved!
Go to Solution.
Attachments:
14_03_2012_dbgview_log.txt ‏26 KB

Hello Norbert, thank you very much for your help.
This helped for me:
uncheck "SSE2 optimization"
When SSE2 option was unchecked, it worked.
You also asked:
>You have not attached your sources.
No, the project is too big
>Is that issue connected to your previous post?
No, its another project
>Do you use dynamic VI calls where you possibly miss VIs of that hierarchy (issue: source distribution)?
no, currently not
>Have you tested if "Use LabVIEW 8.x file layout" does have any effect (advanced options tab)?
yes, this works also, when SSE2 is disabled
>The debug log (origin?) states something of "target not found" and "target has no VI.LIB. I would focus my search in this direction....
Thanks
Eugen Wiebe
Bernstein AG
CLAD - Certified LabView Associate Developer

Runtime engine 8.6.1 on Labview 11

Hello,
I have upgraded labview 10 to Lv 11. A program that used to work on Lv 10 is giving problems now. It asks for runtime engine 8.6 ( usually gets stucked preparing the installation ). Once i cancel this process, it loads all the vi's, and it seems to work, but I can't be sure until all the devices are connected, and it can't be done until september. My question is, do i really need to install runtime engine 8.6 to make it work properly, or it can work without it?
And if I downgrade to Labview 10, will i solve this issue??
Thanks in advance!!

This is actually strange behavior because the runtime engine 8.6.1, if it is installed on the computer, should be accesible both from LV2011 and from LV2010.
What do you mean by "downgrade to LabVIEW 2010? You may have multiple version of LabVIEW on the same computer. Did you uninstall LV2010 first? If you did, then it may happened that you uninstalled the runtime engine 8.6 at the same time.
Do you really need or don't need the engine depends of your application. In any case, it should not be a problem to download the runtime engine from ni.com and install it. http://joule.ni.com/nidu/cds/view/p/id/1244/lang/en
Sergey Kolbunov
CLA, CTD

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

Errors while installing runtime engine netframework 4 (32bit)

While installing the update for runtime engine netframework 4 we get diffrent errors. We can't register DLL files.
This is the error we get:
Error 1904. Module C;\Program Files\ SAP BusinessObjects\Crystal Reports for .NET Framework4.0\Common\SAP BussinesObject Enterprise XI 4.0\win32_x86\commonjob.dll Failed to register. HRESULT -2147023898. Contact your Support personal.
same error for:
saxserialize.dll, datadefmodel.dll, cubedefmodel.dll, rptdefmodel.dll, rptcontrollers.dll, requestmodel.dll, clientdoc.dll,
prompt.dll, dtsagent.dll, localcon.dll, crlov.dll, crqe.dll.
Installation ends with installation succesfully. When ignored is pressed.
Hope someone can help to fix these errors. Its not working properly now.

This is the way I resolved a similar issue this week:
In the registry, search for 139E8906DC83 Search HKLM\Software\SAP BusinessObjects. This will lead you to the actual file name.
Download [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx]. Se the filter for regsvr32.exe.
Manually (Start | Run regsvr32 <path to the file>) register the dll.
Save the process Monitor log.
Do a search in ProcMon for cryptocme2.dll. Rename this dll.
Try the install again.
- Ludek

Reg ABAP as UME for J2EE engine with portal

Hi ,
I am using ABAP as the UME for J2EE engine.
The main user is j2ee_admin. In case of login to portal with this user there is no roles assigned to this user.
what roles should i add in the R/3 side to make this available ?
I am also not able to create users or access any role related operation in the UME interface available for the J2EE engine.
Any suggestions..
Regards
Bharathwaj

Hi Bharthwaj
Since thr portal user and Roles are relies on portal database u used Only SAP system as the UME tha's why
u cant's assigned or get any role in the portal
SO if u want to use SAP system as UME u should use
datasource Read only SAP system + Database
regards,
kaushal

Tools for reverse engineering an ERD from the database

We were thinking about using Visio as a tool for Reverse Engineering ERD's from our database. Unfortunately, we can't find any good training that goes over this part of the tool in detail.
So, then I started thinking, maybe it's not the best tool, then. Any suggestions on whether this is the tool, or if there's a better alternative?
Thanks
--=cf

Hi ,
The Oracle Designer contained in the Oracle Dev Suite 10g can accomplish your requirement...
Greetings....

Make the installer for my executable run the DAqcarddriver and runtime engine installer automatically

*Hi
I would like to know how to make the installer for my executable run the DAqcarddriver and runtime engine installer automatically
I would like to include run time engine and the drivers of my daqcard(AI16XE50),( and maybe Ni daq or anything else needed?) in order to make my application portable for other computers on OS win98 and winXP .
How can I do that
thank you in advance
Olivier

Olivier,
What version of LabVIEW are you using to build your application? On a remote computer you should only need the drivers you are using and the Run-Time Engine. You can attach installers to LabVIEW 8 installers, but for previous versions you will have to add it by opening the installer configuration page, configuring your installer and then configure the Advanced properties. This will allow you to attach a EXE to the installer which you can run. Also depending on the version of LabVIEW will affect the OS version that you will be able to install the RTE on. LabVIEW 7.0 is the last version that can be installed on Windows 98.
Please let me know if you have any further questions and please include the version of LabVIEW you are using. Thanks!
Andy F.
National Instruments

Unable to determine the install root path for the LabVIEW Runtime Engine

Hi,
i have an issue with using a LabVIEW interop assembly in a .NET application. I get an exception "Unable to determine the install root path for the LabVIEW Runtime Engine" when calling the assembly.
The little test program is attached below. It's called dotNETHost.exe. If you excecute the programm a dialog with an button appears. Clicking the button shall open another dialog (the LabVIEW Interop component). But the only thing I get is the exception message. The ZIP folder also contains the complete exception meassage (ExceptionMessange.jpg & ExceptionDetails.txt).
The Interop Assembly was built with LabVIEW 2011. We use Visual Studio 2010 and .NET 4.0.. The dotNETHost.exe.config file is prepared as mentioned in Knowledge base - Loading .NET 4.0 assemblies.
The Interop assembly contains only one simple dialog (loop is finished by clicking OK) without calling any other VIs or other DLL's. In case of this there's also no support directory generated by the build process.
I have no idea why it doesn' work. I hope anyone can help me.
Thanks in advance
Kay
Attachments:
Debug.zip ‏75 KB

This may be unrelated, but Labview and .Net4.0 dont work well together. Not yet anyway. I had to compile my assembly in 3.5 to get it to work.
Please read the following:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configuring_clr_version/
http://digital.ni.com/public.nsf/allkb/32B0BA28A72AA87D8625782600737DE9
http://digital.ni.com/public.nsf/allkb/2030D78CFB2F0ADA86257718006362A3?OpenDocument
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Run labview exe in other way than runtime engine?

Hi guys
This might be stupid question, but can I run labview's *.exe in other way than in the runtime engine? In these days in have done *exe and installer with runtime engine and give it to the end-user. It does not matter how tiny ur code is, user have to install 40 conponents and then restart computer... How annoying. Is there eny other way? Can i use other programming languages some how?
-AA-

If the runtime is only one out of 40 components, it should not make a big difference for you.
I always tell my users to download and install the runtime engine directly from NI. This needs to be done only once per PC and per runtime version, at which point you can distribute a small installer.
There is also an idea to simplify all this. Please support it.
(It is not reasonable to be able to build an executable with embedded runtime, that would make a LabVIEW 2009 executable 100+MB in size. (We had that back in LabVIEW 4.0, where each 20kb VI turned into a 3+MB executable, which was significant in the days of 1GB drives.)
Message Edited by altenbach on 12-16-2009 11:42 AM
LabVIEW Champion . Do more with less code and in less time .

Exe in french and runtime engine in english can it run?

exe in french and runtime engine in english
also max version is english
can it run successfully?

Hello,
You can build your executable with the french version of LabVIEW and run your executable with the english Run-Time Engine. However, note that strings in menus (such as File, Edit, Project, Help, and so on) and pop-up menus depend upon the version of the LabVIEW Run-Time Engine you are using with the executable. If you use the english Run-Time Engine, the menus always appear in english, regardless of the language of your operating system.
Also, note that for standard dialog boxes, LabVIEW uses strings (such as Open, Close, Save, and so on) that are specific to the operating system. Some dialogs contain LabVIEW specific strings (for example, Select Cur Dir), which LabVIEW displays in french, german, or japanese, according to the operating system's regional settings.
So if you need french menus and LabVIEW resources in your executable, use the french version of the Run-Time Engine available here.
Good luck and have a nice day!
Shakhina P.
Applications Engineer
National Instruments

Call a sequence of VIs (not .exe)) in VB. only LV runtime engine Installed

I am try to reuse my labview vis in VB enviroment. I would like to call a sequecne of vi from VB just like in LV with Call By Reference. This is a production enviroment, only Labview runtime engine installed in the computer. I realize that I can call labview exe file from VB, but then I have to compile every vis (more than hundreds) and have to reference every vis servers in VB.

Actually, the runtime engine can run any VI--not just ones built into an application. The problem will be getting data in and out of the functions.
If you have much of the code already written in LV why are you messing around with VB? Wouldn't the easiest solution be to write the entire application in LV? Just wondering.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

I can not open Excel (97, 2000, or 2003) spreadsheet in Win98 OS PC using LabVIEW 7.0 Runtime Engine

Hi,
I have a problem opening an Excel spreadsheet by a LabVIEW application that is using Runtime Engine 7.0 in a Windows 98 OS environment .
I tried LabVIEW 7.1, it will not install on Win98. Meanwhile, I installed Excel 97 and 2000 (Excel 2003 does not install on Win98) and tried to open the spreadsheet, no luck with any combination.
Same code can open the spreadsheet in a WinXP OS, RTE 7.0, Excel 2000/2003 environment.
What can I do? Any advise?
Regards,
LVLV

Hi,
I did some experiment, I found out that Run-Time Engine 7.0 running executable generated at LabVIEW 7.0 environment (code written in LabVIEW 7.1 but save as 7.0) cannot open Excel 2000 files. If I replace Excel 2000 with Excel 2003 application on my pc, the executable code will open the Excel file (Run-Time Engine 7.0 works with Excel 2003).
Is the Excel 2003 and higher versions will only work with Run-Time Engine 7.0 and higher code?
How can I make executables using Run-Time Engine 7.0 work with Excel 2000 (Windows 98 operating system)??? (I cannot change Excel and Run-Time Engine and OS versions due to limitations, how can I work with what I have?).
Thanks for your help.
Regards,
LVLV

Using LV2009 to produce EXEs for Runtime Engine 8.6

Similar Messages

Maybe you are looking for