Why does my LabVIEW Run-time server return the message "source does not exist Last UI message: Start Execution"?

I am trying to build a stand-alone application on a target pc for which I have built a LabVIEW server that TestStand can use as an adapter.
In order to do this, I searched this site and found the topic: "How do I build and Use the LabVIEW Operator Interface as a LabVIEW ActiveX Run-time server?" After following the procedure to the letter, I ran the testexec.exe file as instructed and loaded my sequence file. As soon as I try to "Single Pass" or "Test UUT" I get an error which says "source does not existLast UI message: Start Execution". This error appears when running the testexec.exe file on the target pc or the development pc.
I have found though, th
at if I open the Operator interface through the Start: Programs>National Instruments>TestStand>Operator Interfaces>LabVIEW then the sequence file runs without these errors.
Any ideas why this is happening?

Hello Robroy,
The KB you mentioned explaines how to build the LV Operator Interface (OI). So, I assumed you built the LV OI and also configured the LV adapter to use the TestStandGUILVRTS server without problems.
The error you are getting may be due to missing VIs. In other words, the LabVIEW OI may not be finding all the VIs your sequence is calling.
In order to deploy sequences that call VIs, you need to first run Tools >> Assemble VIs for Runtime Distribution. This tool gets all the VIs your sequence needs and saves in a separate directory.
For more information, you may check the TestStand User Manual chapter 17, it describes how to distribute TestStand and sequences.
Regards,
Roberto Piacentini
Applications Engineer
National Inst
ruments
www.ni.com/ask

Similar Messages

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

Are LabVIEW VISA functions supported by LabVIEW Run Time Engine?

I have an executable file that I created using LabVIEWS Application Builder. When I run the application on another computer that does not have LabVIEW installed, it crashes with a Windows message stateing the my application has generated erros and will be shut down by Windows. I have isolated the problem as having something to to with VISA Reasource Names.
Does anyone know if there has been any issues regarding the use of VISA function in LabVIEW Run Time Engine? The version of LabVIEW that I have is 6.0.2. The version of Run Time Engine is 6.0 .
Dan

Yes there are issues with the RTE 6.0 and VISA. Use the RTE 6.0.2
LabVIEW, C'est LabVIEW

What is "LabVIEW Run Time Engine"?

I'm trying to find the differences between two computers that I'm troubleshooting. One of them is my development system which has the whole Development Suite installed, and the other is a test station which has LabVIEW 8.0 Evaluation Version installed. When I was looking through the list of programs in my development system (in Add/Remove Programs), I found a program named "LabVIEW Run Time Engine" and the size is 0.11 MB that is not in my test station. I thought all the NI components are installed under "National Instruments Software" including the Run Time Engine...
Does anyone knows what this is?
See-Ming

The Run Time Engine is a library of routines that a compiled Labview program needs to run on a system that doesn't have the development environment. It is similar to Visual Basic's vbrun.dll, which compiled VB programs need to run.
As far as I know, the run time engine gets installed whenever you install any Labview development environment. This engine is usually only necessary when running a Labview program compiled to an exe format. Both the exe and the run time engine can be installed on another computer so that the program can run without having to buy another development package for that computer.
The runtime engine is called LVRT.DLL. Search for it. For version 7.1, the run time engine is in C:\Program Files\National Instruments\shared\LabVIEW Run-Time\7.1\lvrt.dll
- tbob
Inventor of the WORM Global

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

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 to include LabVIEW Run-Time in executable file ?

Hello folks,
I have an application that need the user to simply calling executable file without setting up LabVIEW run-time because my executable file will be posted in LAN and anyone can run it remotely. What should I do? Any help very appreciate...
Thanks so much

You have to have labVIEW run-time installed on your computer in order to run a LabVIEW programs (vi or exe). What you can do when you distribute an exe file is to create an installer which lets you install LabVIEW run-time and create a menu item (in Windows) in the Start>>Programs menus. Then you can distribute the whole package and after running the installer, LabVIEW run time as well as the exe is installed.
You can do this in the installer settings of the Application builder (when you create the .exe file). Go to the "Advanced" section. There you can add the LabVIEW run-time Engine to the installer.
One other possibility you can do if several people want to use the programm over Lan is to use the LabVIEW webserver. You can run a programm somewhere on the
network and other people can open the front panel in their Webbrowser. But maybe that's not exactly what you want. ??

Compact RIO and LabVIEW run time

Dear All,
Good Morning.
We are developing a new experimental setup which will have different components, such as mass spectrometer, pressure transducers, valves and thermocouples, RTDs. We are currently having LabVIEW 8.6 Run time. We would like to control different components and acquire data using CompactRIO. I am not clear if compact RIO works with 8.5 run time. In the developers guide NI, mention about the real-time LabVIEW.
Thank you very much for help,
Zach

You need the Real-Time Toolkit (and possibly the FPGA toolkit, depending on your needs) to work with the cRIO. The version of LabVIEW installed on the cRIO must match the version you're using for programming on the PC (so you can't have LabVIEW 8.5 on the cRIO and 8.6 on your computer). The LabVIEW Real-Time is not the same as the LabVIEW Run-Time engine. The Run-Time engine lets you run compiled applications on your computer. The Real-Time toolkit lets you program real-time targets such as the CompactRIO.

DNS: The selected log file does not exist

Hi to all,
I am using Lion Server on a Mac Mini and everything seems to work fine. However, when I want to check my DNS log file (Server Admin > DNS > Log) I get a message that "The selected log file does not exist"! Stopping and starting the DNS service doesn't help. Anyone any idee how to view the log file within the Server Admin app?
Thanks in advance!
Ewald.

hi John!
if you have time, patience, and squared balls (just for laugh! ):
Use "strace" to trace all system calls a binary make... System calls like "open" file and "close" file =)
That's say, we are going to "trace the files opened by specific application".
"Strace" in MacOSX comes with Developer Tools, so you'll need to install these to continue.
First you have to know which are the Applications in the game, because "Server Admin" is a client-server application, there will be a client application in the client machine, and a server application running in the server.
You have to trace the server application running in the server. It will be the one which opens the log file, and sends the data to the client application.
I've made some previous investigation about the Server Admin Log parser (see https://discussions.apple.com/thread/3352647?start=0&tstart=0).
Also will be helpfull to read a little bit about strace ( http://linux.die.net/man/1/strace )
Here i do my bet, maybe that command line is what you look for:
#sudo strace launchctl load -w /System/Library/LaunchDaemons/com.apple.ServerPerfLog.plist | grep "open"
sudo: do as super user
strace: trace the binary
launchctl: system service
load -w file: load, as defined in this file
| grep open: and substract just the "open file" traces
Let me know if that gives you more clues!
regards, T

User does not exist in this period / ESS does not work anymore ;-(

Hello experts,
starting any ess application on portal side (leave request), I get the follwoing error code:
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User TESTUSER does not exist in this period
Starting application personal data I get the message: "There are no services in the area."
I know, that this error has often been discussed in this forum. So I check the hints I found, but I could not solve my problem.
The HR user TESTUSER is assigned to the portal user TESTUSER in IT0105 and the user is not exceeded.
TESTUSER got SAP_ALL on HR side.
The error appears for all users, that worked propably a few days before.
Login on portal side and HR works. ESS overview is shown for TESTUSER. For a user that has not a login to HR system it does not appear. So the single singn on (SSO) between portal and HR system seems to work.
The ESS applications worked fine until two days ago. Portal guys said, they had not done any changes on portal side.
Where could the error occure on HR side? How can I recognize if any changes have been made on HR side?
Thank you for your help.

TX HRUSER seems not working.
Using the function 'Set Up and Maintain ESS User (Overview)' in TX HRUSER with my test-PERNR it is shown under 'Employees with deleted users'.
Clicking on it I got the Information:
PERS.NO: 12345678 (i.e.) NAME: Test User FROM: 01.01.2011 TO: 31.12.9999 USER: Name: FROM: TO: User does not exist.
But in IT0105 the PERNR is assigned to user TESTUSER in that period.
When I try to assign PERNR to TESTUSER with TX HRUSER under 'Assign Employees to Existing Users' I read the follwing information:
USER: TESTUSER Name: FROM: 01.01.2011 TO: 31.12.9999 USER GROUP: IT PERS.NO.: NAME: FROM: TO: no employee assigned.
Trying to 'assign employees' I get the message 'Error occurred when creating relationship for user ESSUSER-B to employee'.
Please create the appropriate assignment manually in HR master data.
But I have assigned it manualy in IT 0105.
Concurrent employment (CCURE PAUIX) is not activated.

Why does "NI LabVIEW Run-Time Engine 6.1" window appear when I start LabVIEW?

it also prompts "insert the 'NI LabVIEW Run-Time Engine 6.1' disk.
Attachments:
windows.jpg ‏26 KB

Hi,
There can be many reasons why this error would appear. Most probably, you have a broken installation of the Run-Time engine.
Just reinstall the run-time engine from the LabVIEW 6.1 CD. You can also download it from our web site:
LabVIEW Run-time Engine Version 6.1 for Windows 95/98/NT/2000/ME/XP
Zvezdana S.
NAtional Instruments

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.

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

Does labview run time engine 8.6 LVRTE86std.exe supports DAQ?

Due to the LONG TIME required to build an installer with exe, and this kind of DAQ issues http://forums.ni.com/ni/board/message?board.id=170&message.id=324343&query.id=1071542#M324343
I want to just give the user the Labview run time engine 8.6 LVRTE86std.exe http://joule.ni.com/nidu/cds/view/p/id/1101/lang/en , and ask them to copy paste the exe.
But does the LVRTE86std.exe contains all the necessary dependency for DAQ? Including the Sound and Vibration dependencies required for DAQ? Is there some document I can look up to see whether LVRTE86std.exe supports DAQ and I dont have to build an installer of my own?
Solved!
Go to Solution.

No, the runtime does not include DAQmx. It does not include any hardware drivers. That is discussed in numerous posts.

Data Socket Server installation on Labview run-time PC

How do I install data socket server on a PC with Labview run-time licence only? Is it part of the installer?

Yes, this will install entire DataSocket software. This includes: DataSocket Server, Manager, and Help.
Zvezdana S.

Why does my LabVIEW Run-time server return the message "source does not exist Last UI message: Start Execution"?

Similar Messages

Maybe you are looking for