Calling a VI which uses "system exec.vi" with LabVIEW run-time engine as adapter

Hi,
My TestStand sequence calls a VI which includes a call to "system exec.vi". When I try to load it in TestStand and if LabVIEW adapter is set to run-time engine, I get an error message "Unable to load Vi...". If I switch the adapter to "Development system", then it works fine.
Is there any way to use "system exec.vi" in a VI which is called in TestStand with LabVIEW run-time ?
Thanks,
Alex
Solved!
Go to Solution.

Hi Alex,
In you case, you are getting a -18002 error.
The reason is explained in the following link:
-18002 Errors in TestStand
http://digital.ni.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252?OpenDocument
Please have a look at the 2nd reason. This is your case.
Hope it helps,
Regrads
Julien De Freitas / Applications Engineer / Certified LabVIEW Developer (CLD)
National Instruments Switzerland

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

System requirement for Labview run-time engine 8.6

Hello
is there any system requirements for LabVIEW Run-time engine 8.6? for example, same system requirements for LabVIEW 8.6? Internet Explorer 5 is fine? or Internet Explorer 6.0 or higher is fine? Does it work for Firefox on an Athena Linux mechine?
Thanks
Cynitha
Solved!
Go to Solution.

The system requirements can be found in the Release Notes. Pages 2 and 3 indicate the specific requirements for the Run-Time Engine per platform.

Getting LabVIEW load error code 59 using LabVIEW 2010 with a Run Time Engine.

I use a vi compiled with a run time engine to run separate vi’s in my application directory. Once a file association is made with this exe file any Vi in my application directory is available to be loaded as needed. This is a process that has been very successful for me over the years and would prefer to continue using this process. Most of my applications are running in LabVIEW 8.6 and have moved them to 2009. First indications are in 2009 this process is still working. However, I plan to go on to 2010 before upgrading my test stations.
In 2010 I get the error 59: “The source file’s compiled code has been separated, and this version of LabVIEW does not have access to separated compiled code.”
The same dialog box also presents, (Hex 0x626) “Cannot open a VI with separated compiled code in a Run Time Engine that has no access to the VIObjCache.”
What can I do in the build that will get around this error?
Thank you

Thank you for the solution. I am sure this works until the next vi in the vi library gets this option selected.
The bigger issue is I was doing something that National Instruments did not support. When I started in the days of LV 4.0 it was recommended to me that I use this method as virtually all my applications were for in house projects. This is still my preference because it gives the most versatility and allows modifications of single files rather than compiling the entire application.
The final solution I ended up with for those who may be having the same issues. My recommendation for what it is worth, is to compile the application as an executable. This is from what I can tell the only acceptable and supported method. Using this method the problem is solved.
I have accepted this as the solution. I still don't like it. I could list the reasons why but it is a mute point.
Thanks again for taking the time to respond to this issue and offer the solution you found.

Sand Box has stopped working error when using System Exec.vi with wait until completion is true

I get the following error message in Windows 7 "Sand Box has stopped working" when using System Exec.vi with wait until completion set to true, if I set it to false there is no error message.

Hello JJVerdi
mmm well System Exec.vi simulates a DOS command window, can you run the sandbox from the cmd window using the same commands without any errors?
you may take a look to this KB, it may be related to your issue:
http://digital.ni.com/public.nsf/websearch/2393462BD57B854186256C4F007B706A?OpenDocument
Regards
Mart G

System Error 998 While loading the Labview Run-Time Engine

Hello.
I have a DLL made with LV 7.1 I run the dll using a C compiler and works great in WINXP, but cannot run in Win2K. Error is:
"System error 998 while loading the Labview Run-Time Engin(c:\program
files\National Instruments\Shared\Labview Run-Time\7.1\\lvrt.dll)
READVOLTAGE requires a version 7.1 (or compatible) Labview Runtime
Engine. Please contact the vendor of READVOLTAGE to correct this
problem"
READVOLTAGE is my function inside the dll. The runtime is already
installed. I tried it in another WINXP running machine and works fine.

This is actually a Microsoft bug with statically loaded DLLs. There are a couple of workarounds for it, and I have included two links below to posts that address this issue:
Not found error message from LabVIEW runtime when called from VC++ with statically linked MFC
I get error 998 when calling a LabVIEW buildt DLL from MSVC++
Kind Regards,
E. Sulzer
Applications Engineer
National Instruments

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 using Report generation toolkit in 2011 run time engine

is that possiblity to run the word in labview using Report generation toolkit in 2011 run time engine

It is possible to use the Report generaion toolkit with the run time engine. But you will have to include a lot of VIs from User lib since the report generation toolkit uses a lot of dynamically called VIs and classses.
Certified LabVIEW Architect
Certified Professional Instructor

Building an Application in Windows to be used in Linux (with the Run-Time Engine)

Hi All,
I have an LabVIEW project I have developed in a Windows environment. I can create an Application (.exe) using the Build Specification -> Application Builder which works fine on the development platform.
I now want to distribute the application to a Linux Environment. The OS is openSUSE v10.3 (with GNOME). I have downloaded the two rpm files needed for the run-time engine and installed them, as per here:http://digital.ni.com/softlib.nsf/websearch/97E14BA3E0C14A89862572C300567733?opendocument&node=13207...
Now, the question is; how do I create an Application in Windows which can be used on the Linux Box? According to the Application Builder instructions, it's simply a case of removing the .exe extension in the Target File Name options, however, this gives an error "Invalid Extension."
If I do create an exe and manually remove the extention is doesn't work on the Linux enviroment (typing ./application).
Has anyone had experiance of this?
Many Thanks for Any Help,
Oliver
Windows XP SP 2
Labview 8.2.1
openSUSE v10.3 (with GNOME)
LabVIEW Run-time Engine Version 8.2.1 for Linux

The cross-platform nature of LabVIEW refers more to the code than to the executable.
LV (given the appropriate development version) can compile the same source code into a Windows (using LV for Windows), Linux (using LV for Linux) or Mac (using LV for Mac) program.
This means you will still have three versions of your program, one for each platform.
If you want to distribute VIs (without block diagrams), you will also need different versions of these as without the block diagram, they cannot be re-compiled for a new platform.
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant

Error -18004 with LabVIEW Adapter using LabVIEW Run Time Engine 7.1.1

Hi to all,
I am trying to use the LabVIEW Run Time Engine 7.1.1 instead of the Development System for executing VIs in TestStand with the LabVIEW adapter.
The Problem is that I get the following error, saying that my VIs cannot be executed:
-18004; An error occurred accessing the LabVIEW Run-Time Engine DLL.
All my VIs were masscompiled with LabVIEW 7.1.1
How do I manage this problem, in other words how do I get my VIs in TestStand to run with the LV Run Time Engine?
Thanks for you help,
- Caribe -
PS: I configured the adapter to use the LabVIEW Run Time Engine 7.1.1. When I check back in the dialog "LabVIEW Adapter Configuration" the selector went back to LV Runtime 7.1??? Thats weird dude!

Hi Caribe,
Did you find any solution to this weird behaviour? Even I am facing the same problem! If we set the adapter as LV 7.1.1 runtime engine, it changes back to LV 7.1 runtime engine.
I am also facing -18002 error after mass compiling LV 7.1 folder and my source code folder.
If you can share your solution, that would be of great help to me. If i couldnt find any solution, I have planned to revert back to LV 7.1 version.
Thank you,
Sasi

How to load dynamically String into a VI using LabVIEW Run-time Engine Version 7.0?

I would like to be able to traduce string into my application using import string method. I create an program with my VI to translate. When I use the import method, I get this error: the VI is locked. WHY ? because it works well in the edit mode but not using LabVIEW Run-time Engine Version 7.0 .

Hello loup,
If you call dynamically a VI in your LabVIEW application you must add this VI when you build the .exe file.
To add this VI, go to the Tab "Source Files" when you build application and click on "Add Dynamic VI..." then chose the VI you call.
It should solve your problem.
In the attached file you can found an example of LV program that translate front panel.
Try to build exe file and add "Languages.vi" as dynamic VI and .txt files as "Support files".
I test it, it works.
I hope that this will help you.
Best Regards,
Sanaa T
National Instruments
Attachments:
Translation.zip ‏69 KB

System Error 31 while loading the LabVIEW Run-Time Engine

I'm getting the following error message. I've attached a screen shot of it as well.
System Error 31 while loading the LabVIEW Run-Time Engine (<Pathstuff>\\lvrt.dll)
I'm trying to update an instrument running Windows95. What is system error 31? I can't find anything on it using Google or the forum's search function.
The instrument is a Romulus-IIIA from Quad Group. I'm pursuing assistance from them as well.
Solved!
Go to Solution.
Attachments:
Winzeta Error LabVIEW.JPG ‏17 KB

Howdy Szandstra,
Check out this KnowledgeBase article describing what you are seeing. Follow the steps there to correct the problem. Have a great day, and let me know if that solution doesn't work for you!
Sincerely,
Chris G in AE

System error 999 while loading the Labview Run-Time Engin

Bonjour à tous,
J’ai un PC avec un Runtime LV71.1 qui me retourne l’erreur suivante. Je ne trouve pas d’info sur cette erreur. Une Idée sur la cause ?
System error 999 while loading the Labview Run-Time Engin(c:\program files\National Instruments\Shared\Labview Run-Time\7.1\\lvrt.dll)
Luc Desruelle | Voir mon profil | LabVIEW Code & blog
Co-auteur livre LabVIEW : Programmation et applications
CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW
Résolu !
Accéder à la solution.

Bonjour Maxime, merci pour ta réponse qui est très intéressante. Le soft est en LV7.1.1 est fonctionne depuis plusieurs années. Le PC est chez un client, dans un pays très « hostile », je n’ai donc pas accès à ce dernier. Un superviseur local m’a fait le retour qu’après redémarrage du PC ce dernier indiquait un problème, avec photo pour descriptif. Je n’ai pas plus d’info pour le moment. Je viens donc de demander un CHKDSK c: /F
Luc Desruelle | Voir mon profil | LabVIEW Code & blog
Co-auteur livre LabVIEW : Programmation et applications
CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

Can I use the labview run-time engine 2010 with my LV 2012 program?

Hi all,
I will receive the new Labview Developer Suite 2012 DS2 in a few days and
I am wondering if it is possible to run LV2012 programs on the LV run-time engine 2010 or is it necessary to update all my clients from run-time engine 2010 to 2012?
Stay Hungry, Stay Foolish
Solved!
Go to Solution.

Hi Benjamin,
You will not be able to use the LabVIEW 2010 run-time engine with LabVIEW 2012 applications. Versions of run-time engines need to correspond with the version of LabVIEW that you have installed.
The following links direct you to our download pages for the run-time engine:
The 32-Bit Run-Time Engine can be downloaded from our website as can the 64-Bit Run-Time Engine, depending on which version of operating system you, use by clicking the link under "Standard Download".
Hope this helps.
Marshall B
Applications Engineer
National Instruments UK & Ireland

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

Calling a VI which uses "system exec.vi" with LabVIEW run-time engine as adapter

Similar Messages

Maybe you are looking for