Run-time engine problem in Labview 2009 and Labview 2010

I have a problem with Labview 2009 and Labview 2010. I updated my Labview 2009 into 2010. But it turned out to be a trial one, because i did not have the serial number. So I uninstalled the Labview 2010. however, the funny stuff came over. I cannot use my Labview 2009. So i uninstalled Labview 2009 again. But eventually, I could not reinstall Labview 2009. Every time i had a runtime error and i could not proceed with the installation. in addition, any installation related to Labview is not permitted and the same error came up every time. it is very annoying.
So, What is the deal?
I attached the error here. Any comments or advice are welcomed and appreciated.
Attachments:
error.docx ‏2305 KB

By chance is this machine's language set to any non-English locale? You would check the locale setting by:
Opening Control Panel.
Opening "Regional and Language Options".
Looking Under "Regional Options" >> "Standards and Formats"
If it is set to something besides English, trying setting it to English and please report back what locale it was set to (or if this even solves the problem).
Regards,
- WesW

Similar Messages

Browser plug-in with mac run-time engine problem

I have repeatdly tried to get web browser (Both Explorer 5.2.3 and Safari) VI viewing on my Mac (OS 10.4.2). I have reinstalled the run time engine (Labview 7.1.1 as downloaded from NI) numerous times with no luck. I get the usual "Browser plug-in required" message.
Doing a seach on my machine in the Internet plug-in folder reveals no new plug-ins after installation of the RTE.
I can run this VI work fine on a remote PC running Explorer, so I think my VI server is running fine. I quit the PC before trying it on the MAC to avoid any license limitations.
Any suggestions? Is the browser plug in available as a seperate down load? I could not locate it on the NI site.
Thanks
-G

Hi G,
Lets try this. Install the LV71NPlugin file, in the attached image, in the /Library/Internet Plug-Ins directory. I had to save the image with a different extension to be able to upload it to the forum so...
1) Download the file
2) Change the file extension from "abc" to "dmg"
3) Copy LV71NPlugin to /Library/Internet Plug-Ins
Please let me know if this works for you.
Thanks
Chris J
Attachments:
LabVIEW71BrowserPlugin.abc ‏83 KB

LabVIEW Run Time Engine and ActiveX Automation Server

Hi,
I have a question related to LabVIEW Run Time Engine and ActiveX Automation Server:
We have a tool developed in LabVIEW and TestStand. End user interface is a LabVIEW GUI (it's an executable) which executes TestStand sequences. Some TestStand sequences call lower level LabVIEW VIs.
Everything works fine with LabVIEW installed, but I was wondering if I could run this tool on deployment machine with only LabVIEW run time engine installed. We are using LabVIEW 6.1 and with only the run time engine installed, I get the error message: "Unable to launch the 'LabVIEW.Application' ActiveX automation server ".
BTW, we are planning to upgrade the versions soon.
Is it possible to make things work only with the run time engine?
Thank you.

Thanks for the response, Brian.
I did upgrade to LabVIEW 8.0 and TestStand 3.5. Everything works fine on the development computer where LabVIEW and TestStand is installed. On the target computer in the lab, I installed LV RTE 8.0 and TestStand 3.5, and now when a VI is called in a sequence file, I get the following:
RunState.PreviousStep.Result.Error.Code -18002
RunState.PreviousStep.Result.Error.Msg "LabVIEW: The VI is not executable"
So, the executable opens and works fine (which means that the LV RTE is installed properly), but when a sequence calls a low level VI, it does not make it through.
comments/suggestions are appreciated. Thanks.

Teststand error states that a vi failed to load in the Labview Run-Time Engine

I am getting an error in teststand that states that a vi failed to load in the Labview Run-Time Engine version '14.0.1'
If I look at the software loaded on my system with the NI Measurement and Automation Explorer I have Labview Run Time engines for version 2009, 2010, 2011, 2012, 2013, & 2014 on my system.
How do I get this VI to run on this system when it is called by test Stand?
Thank you

The RTE 14.0 was loaded as part of my deployment and after I ran this I got an update notice for the F1 patch which I also loaded.
I do not have labview loaded on this system, only the run time engines from running my deployment.
When I launch t he teststand sequence, when it calls the labview VI, I get the following error moessage:
Error: Failed to load VI 'C:\builds\RelayVoltageMeaure.vi' in the LabVIEW Run-Time Engine version '14.0.1'. LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it. VI Path: C:\builds\RelayVoltageMeaure.vi[Error Code: -17600, Failed to load a required step's associated module. ]
I have attached the teststand sequence if this helps.
Thanks
Attachments:
QuantumDigitalBd.seq ‏13 KB

Can I run two separate versions of the LabVIEW Run-Time Engine on one PC?

Hello, I am curious if anyone knew if it is possibly to install and use two separate versions of the LabVIEW Run-Time Engine on one PC? I currently have the 2009 Run-Time Engine installed on one machine and wanted to install the 2011 Run-Time Engine as well. I know that you can run two separate versions of the LabVIEW program on one machine, but what about the Run-Time Engine?
Thanks!
Solved!
Go to Solution.

I'm guessing this is a bug that NI needs to fix. I see no reason you shouldn't be able to install the run-time engine of an older version. I'd be interesed in if it allows you to install the older development environment, which also includes the older run-time engine. There are some command line switches for NI installers as mentioned here:
http://digital.ni.com/public.nsf/allkb/C361087EE9F20810862577850073128E
I wonder if there is a force install option.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Why do different versions of the LabVIEW Run-Time Engine not compatible?

LabVIEW Run-Time Engine to become more and more big
Why do different versions of the LabVIEW Run-Time Engine not compatible?
" 一天到晚游泳的鱼"
[email protected]
我的个人网站：LabVIEW——北方客栈 http://www.labview365.com
欢迎加入《LabVIEW编程思想》组——http://decibel.ni.com/content/groups/thinking-in-labview
Solved!
Go to Solution.

jwdz wrote:
LabVIEW2020 ....... ，it look like?
You need to express your ideas more clearly. We cannot fill in the blanks and read between the lines if the post has no substance.
jwdz wrote:
It will affect the future development of LabVIEW, right?
What is "it"?
There are many things that affect the future development of LabVIEW, starting with NI management, all the smart people in LabVIEW development, the economy, the LabVIEW users, etc.
If you are worried about the increasing size of the distribution, the good news is that the cost of data storage and data transmission has dropped much more dramatically. Even though newer versions are bigger due to great and welcome new features, the improvements in infrastructure have actually made the distribution and storage significantly easier over the years and will continue to do so. Trust me!
Nobody wants to go back to a LabVIEW version that fits on a floppy disk!
LabVIEW Champion . Do more with less code and in less time .

What is Run Time engine 5.1.1?

I came across on our network a Runtime engine 5.1.1 program for LabView??, Can anyone tell me what this does or can do?

The LabVIEW Run-time engine (RTE) is needed for compiled LabVIEW exes to run. So if you have any applications (exes) written in LabVIEW 5.1.1 then the RTE would need to be installed on the machine that uses those exes.
It basically consists of the shared primative functions in LabVIEW as well as the code needed to actually run the LabVIEW exes. The LabVIEW RTE is similiar in behavior as other languages RTEs.
Message Edited by Evan on 02-24-2006 10:18 AM

Where is VISA run time engine in new LV 7.1 from August?

Hello All
Can somebody help me locating run time engine to VISA in the new LV7.1 from August 2004?
Thanks in advance
Pawel

Hello Pawel
The Run-time engine is not related to the LabVIEW version you are using on your executable but the NI-VISA driver version you are using in LabVIEW on your executable. So if you are using the newest version of NI-VISA in LabVIEW 7.1 which is version 3.2 you would have to install VISA Run-time engine 3.2 on the target machine.
You can find all the VISA run-time engine version on the following site...
http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BAC002C51FA?opendocument&node=132070_US
Regards
Mohadjer

LabVIEW 2009 and its sp1

I have the LabVIEW 2009 and LABVIEW 2009 SP1. Do I have to install 2009 first and then 2009 SP1? Or the 2009 SP1 also includes the full 2009. The reason I am asking is that I installed my 2009 on a computer, which took forever by the way. After the 2009 installation is completed, I installed the 2009 SP1, and it took pretty much the same amount of them, so I am wondering did I have to install both?
Yik
Kudos and Accepted as Solution are welcome!

Thanks!
Kudos and Accepted as Solution are welcome!

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 involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

This problem seems similar to the post "Resource not found error in executable on development machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards.
I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010. The code was using a custom executive and my task was to rewrite the test using TestStand 2010. I reused the majority of the old code. The old code used NI-5660 to control the 5600 and 5620. When I run my sequence using the LV Development System and TestStand, it runs without any issues. When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues. It warns that the nipxi5600u.dll was not initialized correctly. Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter. The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again.
I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace. I also used Dependency Walker to track down the problems with the nipxi5600u.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32). I have also performed a Mass Compile to make sure everything was running in LV 2010. If I skip the steps involving the 5660, my entire sequence runs fine.
The previous code was running with the LabVIEW Run-Time Engine without any issues. Is there just a step I am missing? Has anyone seen anything like this before? I can send screenshots of errors to provide more detail if necessary.

I have tried some more things and still can't get it to work. I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs. This did not change the results.
When I try to run my sequence, The first error I get is shown in Error 1445.bmp. This happens when I try to use the NI 5660 initialize.vi. If I click ignore, the next error I see is shown in Error -20551.bmp. When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp. When I close TestStand, I get the error LabVIEW Fatal Error.bmp.
Attachments:
Error1445.JPG ‏164 KB
Error -20551.JPG ‏174 KB
Error loading nipxi5600u.JPG ‏9 KB

LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand,
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay

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.

Is Labview Run-Time engine 2009 SP1 compatible with Windows 8

I potentially need to install a Labview executable and Run-time engine 2009 on a Windows 8 OS. From looking at the run-time engine support, it only looks like it only shows windows 7 down to XP. Does anyone have any experience using Runtime 2009 on Windows 8?

Hi Awhite144,
The first version of LabVIEW to officially support Windows 8 is LabVIEW 2012 SP1. That being said, I would expect LabVIEW 2009 to work fine on Windows 8, and if you run into any trouble, feel free to post it here. LabVIEW 2012 SP1 installs a number of older LabVIEW run-time engines (including LabVIEW 2009), so it will install on Windows 8.
I have not personally used LabVIEW 2009 on Windows 8, maybe if someone else has experience with it they can weigh in, but I expect it to work.
As an important consideration, I assume you are talking about the full version of Windows 8, not Windows 8 RT.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments

Run-time engine problem in Labview 2009 and Labview 2010

Similar Messages

Maybe you are looking for