Runtime Engine 7.1.1 Disk 2 when starting Labview

I have labview version 8.2.1 installed on my computer.
The other day I installed some application by another company that must have installed Labview Runtime Engine 7.1.1 on my computer. I didn't need that program anymore, so I uninstalled it.
Now anytime I try to run any labview programs on my computer, I get several dialog boxes wanting me to put NI Labview Runtime Disk #2 in my CD drive.
How can I get rid of these dialog boxes?
Please help!!!

Hi bkundework,
This issue seems very strange but I do have a few suggestions. The first idea that comes to mind is to repair LabVIEW 8.2.1 from Add/Remove Programs. If you no longer have the 8.2.1 disks or if a repair does not work, you should install the LabVIEW Run-Time Engine 8.2.1. This download is available on NI’s website.
These two ideas are the easiest ways to possibly fix things. If they don’t, a list of all the NI Software you have installed would be helpful for going forward.
Charlie M. CLD

Similar Messages

How to access Disk utilities when starting up. Is it Shift, Apple , R?

How do I access Disk Utilities when starting up. Is it Shift, Apple, R?

If your objective is to get into the recovery partition, try COMMAND + R keys.
Ciao.
If you are still on Leopard OSX, it will not work.

LabView Runtime Engine 7.0 trys to install at start up

This just started happening, every thing was fine a few days ago. Now when I click on the LabVIEW desktop ICON it says it wants to install the 7.0 Runtime Engine. And asks for disk#3 Do I need this? Eventually after canceling prompts for a few minutes it loads my lab view and my VIs seem to work fine.
I,m using the 8.6 student edition,
Any Ideas?
Thanks
Alan Martin
Solved!
Go to Solution.

Alan,
The lvruntimeeng.msi that you said your program is looking usually resides in your drivers installer folder with a path like this:
C:\National Instruments Downloads\NI-DAQmx\<Your Version>\NIDAQ<Version>-1\Products\LabVIEW_Runtime_Engine_71\LV711RTE
Mine is exactly this path:
C:\National Instruments Downloads\NI-DAQmx\9.0.2\NIDAQ902-1\Products\LabVIEW_Runtime_Engine_71\LV711RTE
The 7.1 Runtime Engine is uniquely named "lvruntimeeng.msi". The 8.0 is named "lv80runtime.msi" and 8.2 is "lv82runtime.msi" and so on. Since we cannot install this 7.1 RTE because you have a more recent version installed, please check the path name described above to see if your 7.1 Run-time Engine MSI is in there. Maybe even run a search to see if it is present anywhere on the system.
If not, we can uninstall and reinstall your DAQmx drivers and reinstall them since they will have each Run-time Engine MSI.
Clearly there has been a file structure mishap and these can typically only be remedied by completely reinstalling the program(s) that initially installed the file(s).
Logan H
National Instruments
Applications Engineer

MSVCR90.DLL Error when start LabVIEW 2009

Hi,
   My LabVIEW 2009 failed to start. It pops up a window says fault module MSVCR90.DLL. I have reinstalled LabVIEW but the problem is still there. Anybody has similar problem before?
   Thanks for help!
   Tom

Hi,
unfortunately I can't do anything in c:\windows\... because I'm not an adnministrator. I have to wait at least a week before he comes back and maybe do it for me. There are 2 Versions of Microsoft Visual C+ installed on this comuter: 2008 and 2010. When LabView crashes and I select "Debug" there are 2 possibilities: 2008 and 2010. The msvcr90.dll which is marked as "failure" in an error message referres to Microsoft RunTime Engine 2008 (according to its properties).
I had made another experiment: set "runTime Engine" as VI server by Test Stand. In this case VIs are marked as "erroneus" (with a red button on the module panel). I have to reload every VI (the red button stays, but the picture is loaded), then start execution and ingnore the message, that there are errors. The sequence works OK. When I close TestStand I get an error message "TestStand doesn't work any more-> SeqEdit APPCRASH".
I think it shows, that RunTime Engine (I select the option "Recognize the version automatically") loads VIs in another way than LabView Development Environment does.

Ni::dsc::osdep::PosixError when starting labview

Hi
When I try and start Labview i get the following error
terminate called after throwing an instance of 'ni::dsc:sdep:osixError'
what(): Invalid argument
Aborted
we have version 9.0 of labview on linux rhel 5.4 and from what i can see from the gui it get's up to running "converting toolkits" before it crashes.
Thanks
Caleb

Hi,
When I try and start Labview i get the same error
"'ni::dsc:sdep:osixError"
I launch labview as root and It works.
Why ?
Presently I wait for the answsers with
grep -r "'ni::dsc:sdep:osixError" *
Cheers,
jo

Error 2 when starting LabVIEW from ELVIS Instrument Launcher

I have a WinXP Pro SP2 box that's running LabVIEW 7.1 (academic license) and NI ELVIS 2.0.1.
When I perform the following steps,
1) Log on to the WinXP machine as a user who does not have Power User or Administrator privileges.
2) Click on Start > All Programs > National Instruments > NI ELVIS 2.0 > NI ELVIS
3) Wait for the "ELVIS - Instrument Launcher" application to finish initializing.
4) Click on the "Launch LabVIEW" button at the bottom of the ELVIS - Instrument Launcher window.
I immediately get an error dialog that says
_dialog_box_text_
Error 2 occurred at System Exec.vi. Command
was "LabVIEW.exe:\ "C:\Program Files\National
Instruments\NI ELVIS 2.0\ELVIS - LabView
Launcher.lib""
Possible reason(s):
LabVIEW: Memory is full.
NI-488: Write detected no Listeners.
["Continue" button]
_/dialog_box_text_
[n.b. The characters ":\" that immediately follow the LabVIEW.exe program name (see above) are not a typo on my part. Those characters are shown on the Error 2 dialog box.]
It seems unlikely to me that the ELVIS - Instrument Launcher application has run out of memory. The host machine has 512MB of physical memory and the ELVIS - Instrument Launcher application is the only (user-layer) application. The Windows Task Manager (via a "3-finger salute" - Ctrl+Alt+Delete) indicates ample memory resources are still available when the Error 2 dialog pops up.
For what it's worth, if I perform steps 1 thru 4 above while logged on as a WinXP administrator user, I do not get the Error 2 dialog. I get instead the "NI ELVIS - LabVIEW Launcher" dialog which offers the following 3 choices: View NI ELVIS Examples; View NI ELVIS Instrument Source Code; Open LabVIEW.
Is there anything I can do to correct the Error 2 problem for non-administrator users?

Hi,
Well since it works as an admin, I am assuming there is a problem with you being an admin all the time. If there is, then I would suggest giving full sharing privileges to the National Instruments folder, to whichever user you are. See if that works. Let me know.
George

How do I determine if a VI is running in the runtime engine or LabView Development Environment?

Is there a function or VI that I can call that will tell me if the program is running in the LabVIEW Runtime Engine or if it is running in the LabVIEW developement Environment? I am using LabView 8.5.
I have a menu item, File/Exit, and I would like to call the Exit LabVIEW vi if running in the runtime engine when that item is selected. However, in development, I don't want to shut down LabVIEW when I select that menu item.
Maybe there is a more appropriate way to exit the program. However, I am looking for something elegant. I'm sure I could find some other way to accomplish the same thing, but I'm looking for a clean way to do it.
Thanks

Here is a small VI with this exact function.
Attachments:
Is EXE.vi ‏9 KB

Can't uninstall runtime engine 6.0.1

I'm trying to update a computer from a labview runtime engine 6.0.1 to runtime engine 6.0.2. I am able to install and uninstall runtime engine 6.0.2 but I can't uninstall runtime engine 6.0.1. In the control panel on "add/remove programs", I can't remove "NI Labview runtime engine 6.0.1". In fact when trying to remove it, I get a dialog box that displays the message "This action is valid for products that are currently installed". Any suggestions on how to remove 6.0.1 runtime engine before or after installing runtime engine 6.0.2?

Jeff,
When you install the run-time engine 6.0.2, do you still see the run-time engine 6.0.1 in the add/remove programs? If so, then go and delete the run-time engine 6.0.1 folder from the installation (Shared) directory.
If you installed the run-time engine 6.0.1 with LabVIEW 6.0.1 update, try running the LabVIEW uninstaller, and select to uninstall just the run-time engine.
I hope this helps.
Zvezdana S.

Runtime Engine

If I build an exe on one machine with the Developers Suite and port it over to another machine do I need to purchase the runtime engine??
Solved!
Go to Solution.

LabVIEW doesn't require purchase of the runtime engine. You can choose to include it in your installer or manually install it separately (it can be donwloaded from NI's website).

What is minimum runtime engine size when installed on XP embedded OS

I hope to build move an existing Labview 8.6 application to a Windows XP embedded machine and would like to know if their are any tools available to help minimize the hard disk memory requirement, specifically can the runtime engine installation be micro managed so that absolutely nothing that is not required by the application is installed?
If not, is their some way to install the runtime engine and then remove unused items, for instance one .dll file at a time?
I would appreciate any guidance.
Thanks,
Bernie

I believe NI does not officially support running LV apps on XPe, but if you search, you should find some references to it. In any case, I doubt you will find anything relating to the size of the RTE. You can probably safely remove some of the support files (e.g. language files, which take up some space), but I've never done it and it isn't necessarily safe.
In older versions, you could simply use all the files from the RTE folder if you didn't require any drivers, but I believe that doesn't work since ~8.0.
Try to take over the world!

I need to download Runtime Engine 7.1, but I get a 404 error when I try to download from the website.

I need to download Runtime Engine 7.1, but I get a 404 error when I try to download from the website.

Are you getting it from this link (assuming Windows): http://joule.ni.com/nidu/cds/view/p/id/703/lang/en? The download link on that page seems to work just fine.

Labview trying to find runtime engine when opening up VB6

This is bizarre. I'm not even trying to open a labview program, and I get this error.
when I go to open up VB6 from Visual Studio (Visual Studio 6, Enterprise Edition), I get a pop-up saying that the Labview runtime engine 7.1.1 is going to be configured. A new window then pops up, because it can't find the lvruntimeeng.msi file.
Problem is, I'm using Labview 8.2.
Worse, now my VB6 programs are hanging if I close out of all the installer boxes (it does this multiple times).
UPDATE-4:42PM EST-
I noticed when I went into Add/Remove Programs in the control panel, when I clicked on Change for National Instruments, it says that only the 7.1.1 Runtime Engine is installed. However, I can not uninstall it because another product relied on it. I also downloaded the 7.1.1 runtime engine, but it doesn't install because it says a higher version is already installed. (?)Message Edited by Dauntless on 12-26-2006 03:46 PM

There are some NI programs which were written in LabVIEW and so need the LV RTE in order to run.
Theoretically, the RTE should be properly installed when these programs are installed, but for some reason maybe it wasn't. Maybe one of the NI services running on your machine tries to do something when you're opening VB or maybe your code calls some NI component?
I used to have something similar where for some reason going into certain websites prompted me to insert the LV 7.1 CD so that I can configure the RTE. I think it stopped after doing it one time.
You can try downloading the 7.1 RTE and installing it to see if it will stop. If not, you can try pointing the dialog at the MSI once to see if that will stop it.
Try to take over the world!

System Level Exception, error -17502 when running VI with RunTime Engine

My sequence conains a single Labview VI. The sequence functions correctly with the Labview RunTime engine NOT selected in the "Advanced Setttings" tab. When I enable the check box to always run the VI with the Runtime Engine, TestStand generates the following error "System Level Exception, error -17502. My teststand version is 3.5, with LV 8.2.
Thanks
Peter V.

Hi,
Are you sure you have LV 8.2 RTE on your system?
Regards
Ray Farmer
Regards
Ray Farmer

Is there a .sld file for LabView runtime engine when creating Embedded XP image

I'm looking for a .sld file to aid inclusion of LabView runtime engine in my embedded XP image. Has anyone already written one?

Hi,
unfortunately, National Instruments doesn't have any sld files for embedded OS'es, however, please checkout the links from the Lookout discussion forum, where someone was trying to do something similar.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000AD5C0000&ECategory=Lookout
Although there's no definitive resolution to this thread, the person who answered has said he could be contacted.
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Installer build wants wrong runtime engine

LabVIEW 8.6
Windows XP Pro
When I build the installer for my application, it wants me to have available the install disk from November 2007.
Expanding the list for that disk, I find that it wants the runtime engine for version 7.1.1.
If I remove NI-DMM 2.9 from the 'National Instruments Installers to Include' list in the Installer Properties, the error goes away. The description for that installer indicates it comes from the August 2008 device drivers disk.
At one time I had other versions of LV on the computer. I have removed all other versions, including the directories in c:\Program Files.
My application uses the DMM device driver, so I assume that I need to check the box for the additional installer. I've looked for more documentation on when and why I should select different items in the list, but couldn't find anything useful. Would it be possible for the installer to automatically select those items required and perhaps let me direct it otherwise by choosing fewer or more items?
Bottom line, do I need to select the DMM driver to ensure that my application will run on a computer that doesn't have LV installed?
- les

Hello all,
I couldn't really understand what was doing on in the above questions and answers but from the forum topic I believe I am in right place. I have an issue similar to those desscribed above. I have LabView 8.6.0 installed on my computer but when I run LabView it starts asking for 'NI LabView Runtime 7.1.1'. I tried feeding in the labview 8.6.0 but it doesn't accept it and keeps asking for 7.1.1.
The program used to run fine couple of months back and I then didn't use it for a while and I had other prgrams installed durig this time. And when this month I tried to use LabView it started giving me this trouble. I don't know what went wrong. I installed some ftdi chip drivers also. So, I am thinking if that kind of messed things up.
Also, I have this windows installer message come up sometimes which is not when I open LabView but some other programs. I don't know if this windows installer has to do anything with it.
Whatever the case it is could someone please help me figure out how I can get the right runtime work for my LabView 8.6 and if also possible how i can get rid of this windows installer message. I don't remember the error code right now because it comes up randomly. Next time I see it I am going to save that number. But in the meantime if anyone can help me with LabView 8.6. runtime engine problem.
Thanks,
Lovepreet

Runtime Engine 7.1.1 Disk 2 when starting Labview

Similar Messages

Maybe you are looking for