When creating an application installer in LV, what run-time engine or driver must be installed to install the VISA interactive control?

I've created an application installer using LabVIEW's application builder and use it to install NI MAX. However, after running the installer, the VISA interactive control is disabled in NI MAX.
The installer installs the following NI components: NI LabVIEW Run-Time 2014 SP-1(64-bit), NI LabWindows/CVI Shared Run-Time Engine 2013 SP2, NI Measurement & Automation Explorer 14.5, NI-488.2 Application Development Support (includes run-time), NI-VISA Configuration Support 14.0.1, NI-VISA Runtime 14.0.1, NI-VISA Server 14.0, NI Systems Configuration Runtime 14.5.0, vision run-time, dc-power run-time.
If I download and run the 488.2 installer, the VISA interactive control is enabled in NI MAX. But, the installer created with the application builder does not seem to install the necessary components.
What needs to be added to the installer to enable the VISA interactive control (VISAIC)?
Thanks.
Solved!
Go to Solution.

From Pedro Munoz, Applications Engineer, National Instruments
Sorry for the confusion with the forum post that Jon sent you. I did some research on our internal database and I found out the component will not be installed by any of the components added from the additional installers section on the configuration of the installer. As you have already found out you need to install the full installer in order to enable this feature.
I know that this might be an inconvenient for you because you wanted to have one installer to run. On this case may I suggest using the NI Batch Installer Builder.
The NI Batch Installer Builder allows building installers that contain National Instruments software from several products. That way you can create an installer for you application in LabVIEW (and not include the drivers in the additional installer section), then use NI Batch Installer Builder to include the installer for your application and the full version of the drivers that you mentioned.
Here is the download link:
http://www.ni.com/download/ni-batch-installer-builder-14.5/5193/en/
And in here you can find instructions on how to get started with it:
http://zone.ni.com/reference/en-XX/help/374206A-01/
Let me know if you have any question.
Regards
Pedro Munoz
Applications Engineer
National Instruments
http://www.ni.com/support

Similar Messages

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

Installer Error of LabView Run Time Engine 6.0.2 "premature"

I cannot Install the LabView Run Time Engine on a Computer which runs on Windows 2000.
The Installation breaks on start with the Error Message: "Installation ended premature, because of an Error!"
Does anyone know what to do is ?
Thanks for Help

It's rather difficult to guess why since the error does not give any more information, but there are a few things you can try. First, if you are installing from a CD, try downloading the installer to your desktop first and then run it. CD-ROMs can sometimes run slower that the installer and this can cause problems. Also, check to see what other NI software may have been installed on this machine and determine if any of it could conflict with the 6.0.2 Run-Time Engine. Just possibilities but hopefully they can get you going!
J.R. Allen

Run compiled application (LV 8.6) without run-time engine

Hi,
I just recently wrote a small 200KB program that performs simple calculations that I'd like to use on several different computers. The application works perfectly, but the problem is that I really don't want to go through the download/install/reboot process of installing the LabVIEW Run-time 8.6 software on every single computer (especially since downloading a 100MB file to run a 200KB program seems counter-intuitive). Is there a way to get the application to run without the engine? Previous searches resulted in old posts of people simply copying the engine files from the shared folder into the application directory, but that did not work when I tried it. Is this no longer possible on LV 8.6? I'll have no choice but to rewrite the application in a different programming language if LabVIEW isn't capable of running standalone compiled applications.
Thanks,
Anthony

I made the test with LV 8.6 on Windows.
I used a VI which does not need any drivers neither serial nor any other hardware execpt the graphics card.
I made an application from this VI on my normal development machine and checked that it will start and work as expected.
I setup a NI free partition with Win XP Prof. SP2. I have some non NI programs installed like a virus scanner, defragmentation tool, Adobe Reader, a drive imageing tool and WLAN drivers. The .NET Framework 2.0 is installed.
I copied the application and all files under National Instruments\shared\LabVIEW Run-Time\8.6 to the machine in a temporary folder.
I booted the machine into this partition. The application will start and work as expected. You do not need to make a complete runtime installation until you do not need any drivers.
The above mentioned folder has a size of about 64 MByte. Dependent on the application and desired languages you can remove parts of it.
Dennis,
during the various LV 8.x versions it was possible to do it as described above exepct one version, 8.2 I think, which needed an ini-File in the Windows folder.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

LabView Run-Time Engine 2009 installation failure

Hi,
I have problem to install Labview Run-Time Engine 2009.
This error occur:
Die Installation von NI VC2008MSMs x86 ist auf Grund des folgenden Fehlers fehlgeschlagen.
Auf den Windows-Installationsdienst konnte nicht zugegriffen werden.
Die kann vorkommen, wenn Sie Windows im abgesicherten Modus ausführen oder der
Windows-Installer nicht korrekt installiert ist. Wenden Sie sich an den Support, um Hilfe zu erhalten.
(The installation of NI is VC2008MSMs x86 failed due to the following error.
The Windows Installer Service could not be accessed. That can occur when you run
Windows in Safe mode or Windows Installer is not installed correctly.
Contact your support personnel for assistance.)
I've tried to reinstall and reregistrate windows installer, I've even tried to upgrade windows installer to version 4.5
I've installed Microsoft Visual C++ 2008 Redistributable x86.
Im runing Windows XP Service Pack 3
(Microsoft Windows Version 5.1 (Build 2600.xpsp_sp3_gdr.100427-1636_ Service Pack 3))
I have no problem installing other programs, I can for example install labview runtime engine 7.1.1.
So my question is:
How to solve this problem, how can I make an installation of Labview Run-Time Engine 2009 on this computer that gives me the error described at the begining?
Best regards
Simon
Solved!
Go to Solution.

Hi,
I have already looked at that forum issue.
So I have already tried to delete all keys in regedit.
The problem is, if I continue with my installation, about 10 other new issues will appear.
And my installation will not complete, it will fail.
The installer does not install, it will tell me that the installation failed, and it will only install a few things.
Not all the things that I need to run my program.
See attached pictures ibn zip file to see some errors I receive, I only picked a few of them out.
So when I then tries to start my program I will recive the error in picture program error. (Run-time engine error)
So it's not only that the installer tells me that the installation doesn't go through, it doesn't.
Best regards Simon
Attachments:
Pictures.zip ‏414 KB

Error 1722 when installing Run-Time Engine 6.0

I am unable to install the necessary LabView Run-Time Engine 6.0 required to run my VitalView Software. I have reviewed the message boards and attempted all possible solutions: disabling anti-virus programs, following the NI support links: http://digital.ni.com/public.nsf/websearch/334E91287EDEA75286256D9B003A947A?OpenDocument.
None of these methods will allow for the Run-Time engine to be installed. What can I do?
Help very much appreciated, thank you!

My OS is Windows XP.
I am trying to install an older LabView run-time engine since my application VitalView asks for a LabView 6.0 Run-time engine (or something compatible).
I have attached the jpg of the error message that I receive whenever I attempt to install the LabView engine.
Thank you so much for your help!
Attachments:
Error1722.jpg ‏57 KB

Error 1722 when uninstalling Labview run-time engine 7.1.1

I have been trying to uninstall all NI software so I can start off with a clean slate. I have been going to the control panel under add/remove programs to remove the NI stuff. Everything is gone except the Labview run-time engine 7.1.1. Everytime i try to remove it, i get teh 1722 error followed by the 1603 error. I've tried repairing it but I still get the same results when i try to remove it agian. I've also tried removing it with MSI Blast. This did not work either. I've gone through the registry and manually deleted anything related to NI and that still didn't work. Is there anything else I could try?
Thanks,
Nick

Hey Steve,
I have tried repairing it through the control panel.
I tried reinstalling just the run-time engine and it said it was already installed. So I reinstalled Labview 7.1 and repaired the 7.1.1 run-time engine through the control panel. Then I uninstalled everything. Thanks for all your help
Thanks again,
Nick
Message Edited by Nick_C on 03-12-2007 03:57 PM

When creating documents in pages for ePub what dimensions will fit ipad?

when creating documents in pages for ePub what dimensions will fit ipad?

Here you are in a forum dedicated to Pages for OS X.
Most of us don't use Pages for iOS.
Yvan KOENIG (VALLAURIS, France) mercredi 18 janvier 2012
iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
My Box account is : http://www.box.com/s/00qnssoyeq2xvc22ra4k
My iDisk is : http://public.me.com/koenigyvan
For iWork's applications dedicated to iOS, go to :
https://discussions.apple.com/community/app_store/iwork_for_ios

Shortdump when creating new Application set

Hi All,
We have a newly installed BPC system (BPC 7.0, SP 02).
We are facing issues when creating new Application Set. Although on the .Net server it shows that the creation of appset was successful, in SM37 Copy AppSet job is terminated with Shortdump "Raise_Exception, X_Message".
I can see the new appset in RSA1, however not all dimensions and applications are copied from Apshell.
I've seen SAP Note: 1420399, which says that this type of issue happens when the user does not have sufficient access. But we are facing same issue with admin user who has full access.
Any pointers in resolving this issue would be highly appreciated.
Thanks in advance.
Regards,
Meera

Please verify you have followed the following steps from the installation guide.
These steps are required for proper functioning of the Business Planning and Consolidation software:
1. Set the /CPMB/ namespace to changeable:
a) Go to transaction SE06 and choose System Change Option.
b) Make sure that the BPC Addon is set to Restricted Modifiability.
c) Set the /CPMB/ namespace to Modifiable.
2. Set the /B28/ namespace to changeable:
a) Go to transaction SE06 and choose System Change Option.
b) Make sure that the BPC Addon is set to Restricted Modifiability.
c) Set the /B28/ namespace to Modifiable.
Thanks and best regards,
[Jeffrey Holdeman|http://wiki.sdn.sap.com/wiki/display/profile/Jeffrey+Holdeman]
SAP BusinessObjects
Enterprise Performance Management
Regional Implementation Group

How to specify the database file path when create FDM application

Dear All,
How to specify the database file path (MSSQL) when create FDM application?
Right now, all data file are placed in the D:\ . I want to specify the database files (log and mdf file) in other place. How to do it?
Thanks.

Where is the highS2.xml located on the disk? If you add it to your project you should set its Build Action to Content and its Copy To Output Directory to Always in Visual Studio:
Please remember to close your threads by marking helpful posts as answer once your issue has been solved and then start a new thread if you have a new question.

Does Labview run-time engine 6.0 application created by Window NT can install & run on other OS?

I created a Run-Time engine 6.0 application from my Vi and it is working fine! I wonder that this application can install and run on other OS system? What I have heard is "Yes" ... but I am not sure!
Any one know for sure? Thanks.

> I am sorry that I did not clarify my question enough, I meant other
> kind of OS 's that are not from Microsoft Windows!
>
Across multiple OSes, you will most likely be able to load the VIs and
execute them in the LV environment or rebuild the executable with no
problem. But, you will not be able to run executables built for Windows
on Mac, Solaris, or Linux. The reason is that executables have to meet
binary standards, and those standards differ between the OSes. It
really doesn't matter what language/tool the executable is built with,
if it is the OS that is loading it, it will be specific to the OS.
It would be great of someone like ISO or ANSI declared an executable
standard that all OSes could load and execute, but since t
he goal of
executables is maximum flexibility and maximum performance, it is
unlikely that this new standard would win out over the existing ones.
If this comes about, the LV team will definitely be looking to take
advantage of it.
Greg McKaskle

Error on installation of LabVIEW Run-Time Engine 8.5.1: "This application has requested the Runtime to terminate it in an unusual way"

Hi,
a colleague in India cannot install the LabVIEW Run-Time Engine 8.5.1 on Windows XP. On attempting to install, an error box is shown, which says:
(window title)
Microsoft Visual C++ Runtime library:
(message box text)
Runtime error!
Program: C:\National Instruments Downloads\LabVIEW 8.5.1\Runtime Engine\setup.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
http://img529.imageshack.us/my.php?image=runtimeerrorvt7.jpg
I didn't find any relevant clues for this in NI forums. A search at Google brought me to http://support.microsoft.com/kb/884538/en-us, offering a HotFix to solve the problem. Unfortunately, the installation of this HotFix does not solve the problem.
Do you know this behavior and do you have any ideas how the problem can be solved?
Thanks in advance.
Best regards
Manuel
Message Edited by Manuel Häderle on 10-07-2008 10:41 AM
Solved!
Go to Solution.

Hi there
log in as administrator and kill all processes not needed and try again. I've seen cases where one of these free download tweak applications (like "Memory Defragmentation" and stuff like that) caused that error.
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

How do I create installer that checks the available Run Time Engine on the target system

Hi,
I am looking for a soultion on custom Installer where this Installer once done with the Installation should be capable of checking the presence of Runtime Engine on the target system. I amaware of including/checking the LV RTE checkbox for such options and we are working on some other concept. The thing is we would like to give the user a pop-up or any message that shows the presence of Runtime engine on the target system after finishing the installation. In case the runtime engine is not already installed on the target system, this time the message will be for the link to get the .exe and close the installation.
Overall we would like to minimize the size of our Installer that in case will get increased if we include Run Time Engine along with the Installer.
I am also assuming that such checking can be done through Advanced Tab in the Installer properties by including any such .exe for performing those things but looking for more options if possible to get it done.
Please do let me know if someone has any idea about it.
Thnaks in Advance,
Vivek

Hi teststand,
you can start another program which checks if the rte is available. It should also be possible with only a batch file.
Mike

I have trouble in building stand-alone application, "you must intall Labview run-time engine on any computer on which you want to run this application"

I have installed the LabVIEW 7.0 run time engine and checked all in the advanced setup on the installer setup slide. but I still get such a message saying that the target computer needs to have LabVIEW 7.0 run-time engine. What I want is a real stand-alone application even without having labview ... I used to think that's due to my program contains MATLAB nodes. But this is not true, since even without Matlab, it's still wrong. Please help, thanks!!!

As was stated elsewhere, you have the option of building the runtime engine into your application when you build it. However, you can also create a "runtime engine application" by simply opening the application builder and doing a build without adding any source code files. The result is a small program (named lvrt.exe) that can run any LabVIEW code--whether or not its built into an executable.
Such an application can be helpful if you are wanting to install several LV-based applications on the same computer in that it reduces the amount of redundant code on disk. All you have to do is make sure that Windows on the target computer associates the llb and vi file extensions with the runtime engine program.
It can also be helpful during testing to run test code that isn't built into an executable.
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

Run time engine and NI-DAQmx installation order

Greetings Fellow Developers:
I'm looking at a product manual that contains instructions to install NI-DAQmx, a product software installer created with LabVIEW 2009 SP1 Full and then the LabVIEW 2009 Run Time Engine in that order.
This does not seem correct--particularly if a LabVIEW 8 (or previous) Run Time Engine is already installed.
Since I need to test installation of my builds before distribution I'll need to install them on machines that have never had any NI products and also on machines that may have previous Run Time Engines.
I feel the correct order is to install the Run Time Engine, NI-DAQmx and THEN the application. Prior to running the application the USB device should be plugged in so the 'add hardware wizard' can install the USB driver(s).
What is the consensus on this?
Warm Regards,
Saturn
Solved!
Go to Solution.

Hello Saturn,
Could you point out the location of the product manual that explains this order? Typically, when installing National Instruments products, in particular LabVIEW, we recommend installing LabVIEW, drivers, and toolkits in that order. So, installing the LabVIEW 2009 Run-Time Engine, DAQmx, and then your application should be the proper installation process.
Regards,
Roman Sandoval | National Instruments | RF Systems Engineer

When creating an application installer in LV, what run-time engine or driver must be installed to install the VISA interactive control?

Similar Messages

Maybe you are looking for