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.

Similar Messages

I can't Install cubase sx3 on my Mac pro, keep getting installation has failed

I can't Install cubase sx3 on my Mac pro, keep getting installation has failed
Does anyone out their have any answers to this please ?
Thank you.

Have you contacted Cubase support, they may have an answer.

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

Installing Run Time engine question

Hi,
I am new to this and I am looking for information on how to set up a test system PC.
I have the 2014 developer software and one test seat but need to know how to install the labview 2014
runtime engine and anything else that I need in order to use this test system PC to run Labview and teststand
applications that I create with my development system PC...
Is there any tutorials or instructions out there that I can download that will tell me everything that I need to install and how on my target test system?
Thanks

the Installation instructions are on the Download Page
Installation Instructions
Close all NI software.
Run the LVRTE2014_f1Patchstd.exe self-extracting executable and follow the prompts.
Repeat these steps for all development systems where you want to install the LabVIEW 2014 Run-Time Engine (32-bit).
The installation files for the Run-Time Engine are automatically extracted to a directory on disk. The installer does not remove the files after installing, if you want to remove these files from disk, be sure to note their location during the unzipping process.
Jeff

Installing run-time engine 7.0 on windows NT

I attempted to Install Labview run-time engine 7.0 (LVRunTimeEng), on windows NT with workgroups 4, but got the message wrong OS. I am sure I downloaded the correct version (which is supposed to support Windows NT). Anyone have the same problem ? Anyone know how to fix it?
Thanks in advance
Jonny

This message comes from the MSI installer engine. The engine requires Service Pack 6 to be installed on NT 4.0 systems. Can you verify that you have this service pack.
Naren

Where can I download Run-time engine 6.1 for Mac OS

When trying to run an executable I receive a message "Could not load LabView Runtime Shared Library: err = -2804, "Labview 6.1 Runtime". I did not see Run-time engine 6.1 for Mac OS 9 available for download. I only saw version 6.0.2. Does anyone know where I can download version 6.1??

Hi majo008,
If you click on the 'Drivers and Updates' under 'Option 3' on the Technical Support page (www.ni.com/support), you can select 'All Software Versions' and choose 'LabVIEW >> Run-Time Engine'. This page will then have a link to the LabVIEW 6.1 Runtime Engine for Mac OS.
Have fun!
- Philip Courtois, Thinkbot Solutions

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

How can I uninstall Labview run time engine from the machine?

I understand that Labview has not given any provision to show customized 'License Agreement screen'. Isn't it? This is the main cause of my problem. Since I want to show our own license agreement (LA) screen, I made the one using Labview. To show this license agreement screen, I first install a small application which has only this LA screen with Labview run time engine. The customer can see License Agreement Screen with Labview Run Time Engine on his machine. If My customer accepts the LA, I will install the main application further by calling another setup.EXE file.
If my customer selects 'Do Not Agree' to the LA, I will quit the installation process. Here I also want to 'uninstall' Labview Run Time Engine
from his machine since he doesn't accept License. I would like to know how to uninstall Labview run time engine from his machine?
Another way which I could think is to run the LA screen from the CD with Labview run time engine on the CD. I will start installing the main S/W to the customer's machine with LABview Run Time Engine only after he accepts License agreement. I would like to know how to run the Labview application from CD without installing run time engine on the target machine?
Can anyone suggest solution to my problem?
Thanks,
Chander

J-Tek,
I would suggest re-installing the Run-time Engine and then uninstalling it after a reboot. Also, you can download a program called Msicuu.exe (for NT, 2000, XP or Msicu.exe for 9x) to help clean up the registry for uninstalled programs.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Can labview export shared libaray use in C++ without run-time engine?

Hi, everyone
Now, I write a VI for a algorithm and export it as a dll. I use the dll in my C++ apps. It is good. But I want to know how my apps can run without labview run-time engine or I must install run-time engine?

you can install run time engine or include dll which will be used by your application.

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.

Client view vi webpage without needing run time engine

I am trying to create a environmental webpage attached to a Labview vi where end user can browse the web page from their home computer internet. Problem is I read that the end user need to have the Run Time Engine installed in their computers, now this sucks. If the end users need to remember to install run time engine to every computer their visit, there will no business. Is there someway to bypass this?
http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/creating_html_documents_an/
"If you want clients who do not have LabVIEW installed to view and control a front panel remotely, they must install the LabVIEW Run-Time Engine, then view the front panel remotely."
Solved!
Go to Solution.

Hi sunflower2772,
if you want to use the NI function of webserver, then you have to install the runtime engine (there is also a smaller one), the same as using some JAVA code.
If you don't want to do this, then you have to write your own webserver.
Mike

Error 63 run-time engine

Hi, I'm trying to communicate with an instrument through TCP/IP using AK protocol. I've created a VI that works fine on my PC where I have installed Labview 2011.
When I create an executable from this VI to use it on a PC without Labview, it does not work and I receive the error 63.
Of course, I've have installed run-time engine and also VISA run-time, and I use the same configuration on the port (same ip address and port).
Moreover, the executable works also fine on my pc as well as the VI.
Have you got any suggestion?

Error 63 is "LabVIEW: The network connection was refused by the server.".
Is the target machine on the same subnet as the instrument?
No routers/firewalls between the two devices?
Net nanny/web filtering/firewall turned off on the target PC?
Instrument doesn't have to be configured to allow connections from the target machine's IP?
My guess is network configuration. Try pinging the instrument's IP from the target machine, see if that goes through.
First thought was missing drivers/modules, but since you've got VISA and RTE installed, I think you're covered there.

Programatically determine if Vision Run-Time Engine Activated

I am working with an application that requires the Vision Run-Time Engine. After installation, if the Vision Run-Time Engine is not activated I get a pop-up (Vision Evaluation notice) that is behind my main application window. The pop-up is launched when I am running an analysis with the application (I assume the pop-up is invoked when I am calling a Vision Development VI). It appears to the user as if the application hangs. I can force the pop-up to be frontmost so the user will see the window. However, I'd like to be able to programatically determine if the Vision Run-Time Engine has been activated. This way I will not have to continue to poll for this window after it has been activated. Is there a way to do this?
Also, suggest that this pop-up window should be made front most so this work around isn't necessary. Please take a look into this NI R&D.
Thanks!
Brooks

Hi Brooks,
You should be able to probe the error wire and look at the error message to see if the RTE is activated or not. This is the standard way of programatically checking to see if a license exists.
-N
National Instruments
Applications Engineer

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

Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
-install using the plugin
-install using LVRTE.exe
-install after rebooting the server
But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
Is there any compatibility issues with the new Run-Time Engine 6.1 ??
Thanks for your help
Cyrille

Cyrille,
What is the error that you get when trying to install the run-time engine?
Are you installing it from the LabVIEW CD, or did you download it from the web site?
To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
Also, try running the installer from the command prompt window, and use the following syntax:
setup.exe/l*v
This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
Thanks
Zvezdana S.
National Instruments

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

Similar Messages

Maybe you are looking for