Labview 8.5 executable won't run on Runtime Machines

Created an .exe from my Labview Project TS_playback.lvproj. I am running Labview 8.5. Target computers have Runtime Engine 8.5. Windows XP mostly (and 2000). When I run the .exe I either get a quick flash of the loading vi box , or nothing at all. If I have task manager open, I do see the exe open briefly before disappearing.
When creating the exe, I use my main vi as the startup vi.
I don't use any other files in 'Always included'
All subvi's and dependencies are 'Included if referenced'
Custom vi properties of startup vi are basically default, except - turn off run when open, turn off allow debugging.
Note - the vi has locked subvi's associated with LockinPLL and LockinDemodulator.
The code itself is a torn down version of a much more complicated real-time version. This version is simply to post-process data, mainly for a client to fiddle with, so it is meant to function and not be pretty. Sadly, now it only functions on our office machine.
Any help would be great.
Thanks
Attachments:
TS_Playback.zip ‏3064 KB

Lokis wrote:
Target computers have Runtime Engine 8.5.
There are two flavors of the runtime engine and you need the 97MB one. Could it be that you installed only the 24MB web browser version
See this page for details.
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

Executable won't run

I have a main application calling a sub VI 'Sub Al getest2.VI" into a sub panel. When I include a 'display message to user' from the functions palette in de sub VI, the whole program runs fine in developer mode. After building an application, the sub VI opens in the main applications sub panel, but it won't run. The same if I add another custom VI to the "Sub Al getest2 VI" it also won't run after building the full application.
The fun part is: If I create a new project with the sub Al getest2.VI as the main program (and including embedded sub VI's) I can build an executable and it will run fine on it's own.
In the main application build I include all project files as 'Always included'.
Do you have a suggestion what could be wrong?
Attachments:
Sub Al getest2 runs not.vi ‏34 KB
Sub Al getest2 runs.vi ‏20 KB

Putting a VI in a subpanel is not the same thing as calling it. If you want the VI that you're going to put in the subpanel to start running after you open the reference to it, you have to tell it to run by using something like the Run VI method an asynchronous call node.
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

Vi outside executable won't run - Labview 8.0

Hello.
I have a main program including a set of vi:s. I then have modules that hook into the program using vi:s in the main program.
I call the module from the main program with a open vi reference + invoke node.
#1 Main <- #2 module
And it works great. I then build my main program to a executable and
when I launch the executable (main) there is a popup searching for vi:s
and then it dissapears. The module is not executed.
I logged the error output on the open vi reference in the main program and it states: "Error 1003, could not find subvi:s".
In application.ini i have:
[application]
viSearchPath="/path/path/application/*"
Even if i remove the viSearchPath line the main vi looks for the sub
vis, but Im not sure if its actually looking for the vi:s in my
executable. Is there a way to check that the application is actually
using the application.ini file? Am I doing something wrong? This is
possible right? =)
I'm running Labview 8.2, Linux version.
Any help is more then appreciated.

"Fox_Mccloud" <[email protected]> wrote in message news:[email protected]...
Hello.
I have a main program including a set of vi:s. I then have modules that hook into the program using vi:s in the main program.
I call the module from the main program with a open vi reference + invoke node.
#1 Main <- #2 module
And it works great. I then build my main program to a executable and
when I launch the executable (main) there is a popup searching for vi:s
and then it dissapears. The module is not executed.
I logged the error output on the open vi reference in the main program and it states: "Error 1003, could not find subvi:s".
In application.ini i have:
[application]
viSearchPath="/path/path/application/*"
Even if i remove the viSearchPath line the main vi looks for the sub
vis, but Im not sure if its actually looking for the vi:s in my
executable. Is there a way to check that the application is actually
using the application.ini file? Am I doing something wrong? This is
possible right? =)
I'm running Labview 8.2, Linux version.
Any help is more then appreciated.
Well, it's clear that the exe cannot find some subvi's used by the subvi. Some vi lib vi's are not included in the runtime (e.g. some of the picture control stuff). To be sure, you can save the sub vi as development llb, and include vi library vi's. That should include everything it needs.
Under windows, you can start a VI with the executable. When the exe is running, you can use the command prompt to start a vi in the exe (e.g. c:\test.exe "c:\vi with missing subvis.vi"). This does almost the same as starting a vi dyamically, from the exe. A big difference is that you get a list with all the vi's that are missing in a dialog. Don't know if this works with Linux, but usually this work better...
Another thing is when you use type defs. The exe, by default disconnects the type defs. The vi that is started doesn't. That will conflict. So untag the "disconnect from type defs and polymorphic vis" tag in the app builder (if it's in the linux builder).
Regards,
Wiebe.

7.0 executable won't run on xp with new pci-gpib.

This executable ran on previous version of windows. Automation explorer talks to gpib and instruments ok. GPIB version 2.2 installed. Executable doesn't seem to try to talk to gpib, ie. doesn't hang up.

Hello,
If you can talk to your instrument from Measurement and Automation Explorer then it means that the driver and hardware are installed properly. So it has to do with the application itself.
Make sure that you are using the correct device name, because this new board might have gotten a different device number and also check the primary address.
If you have LabVIEW installed in the computer sometimes the problem is because it was installed after the driver, so you might want to reinstall the driver.
If you don�t have LabVIEW but only the .exe and the run time engine, then you can open NI-SPY and see if the application is trying to talk to the instrument at all.
You can find NI-SPY in Start»Programs»National Instruments. Enable the capture a
nd then open the LabVIEW application and run it. You should see some GPIB or VISA commands in the capture.
Hope this helps.
Ricardo Santa Olalla
National Instruments.

Executable won't run on target PC

Hi
I have written an application to control a 'Data Translation' PCI data acquisition card (DT302) using LabVIEW (8.6.1). I have used Data Translations 'LVLink' VIs in the application. It works perfectly on the development PC as a VI and as an executable.
The problem arises when I try to run the executable on a target PC. The program fails to recognize the DT302 card. I believe I have the necessary extra files/software installed:
LabVIEW RTE (8.6.1)
DT Open Layers for .NET Class Library
LVLink2.dll
Driver for DT302 card
I know the card is installed correctly as it can be recognized by other (non Labview) programs. I think I may require an additional file or .dll but I'm not sure.
Any help would be greatly appreciated
Thanks
Stuart

Suspect this is due to a relative path call to the dlls being created by the calling VIs when you compile.
It may be due to a version difference in the files mentioned on your PC and the ones used on the "blank PC".
Recommend you make an installer which includes the dlls and re-installs them to the PC - it is possible that the NI calls to the dlls are modifying them or the registry.
James
Edit:
Compare the Path between your LabVIEW PC and your blank one
Also check the correct params are inserted in the path for any calls to functions external to LabVIEW, this could be causing breaks if %PATH% has not got the required files in it.
Message Edited by James W on 05-18-2010 04:31 PM

Matlab script in executable won't run

I'm having trouble with getting a VI with a MATLAB script to run reliably, specifically when built into an executable.
I'm using LV8.0, Matlab R2006a.
The VI (not executable) runs properly when I start the computer fresh (i.e. just after a reboot)
The MATLAB command window opens as soon as I open the VI.
If I build an executable and run it, it works, so long as I haven't closed LabVIEW and the VI.
If instead, I attempt to close out LabVIEW and run the executable alone, the MATLAB command window does not start, and the MATLAB functionality is ignored.
I have updated all of my dlls, and I have checked the box enabling the ActiveX server (though I don't know what to name the server). I have also read all the associated Knowledge Bases, and found their solutions did not apply.
I also have intermittent issues running the VI once I have tried running the executable.
If I make a change to my MATLAB script, I can get the VI to run again, but if it has failed once, the MATLAB command window no longer opens when the VI is opened.
I can solve this problem by rebooting too, but it seems like there should be a better way.
Any ideas?

Hi tblir,
Can you try to run and build into an
executable one of the shipping examples (i.e. MATLAB Script – Fractal.vi)? Let me know if this exemplifies the same behavior.
Ecleamus Ricks, Jr.
National Instruments
Applications Engineer

Old PhotoDeluxe won't run on XP machine

I have a version of PhotoDeluxe (2.0) that I have been using since I had Windows98. I have many images saved in it's format, I liked using it. I am now running Windows XP, I have run it on other XP machines. When I try to run it on my current machine I get an error "There is not enough memory (RAM) to launch PhotoDeluxe."
I have tried, unsuccessfully to install updates (both 4.0 and 3.0) to no avail. What must I do to get a version of PhotoDeluxe running on my computer?

MichaelKazlow,
My machine has 990 MB of RAM.
In fact the system is : Pentium Dual CPU T2310 @ 1.46GHz, 0.99GB of RAM, Physical Address Extension.
I have been using PhotoDeluxe since the '90s when it ran on a a machine with 96 MB of RAM running at a few hundred MHz.
What would prevent the program from reconizing the memory when I try to open it?

All video file formats won't run on my machine.

This includes mov, avi, mp3, mp4 file formats. I tested using the following software: Quicktime 7 Pro, x, all browsers, iTunes, and mpeg streamclip. Quicktime gives me the following error, "The movie could not be opened. The operation couldn’t be completed. (OSStatus error -50.)". I can't locate the associated error listing to suggest where to look next.
I can only get wmv files to run in windows media player. I deleted quicktime preferences from my library, and rebooted my system, to no avail. Any other suggestions?

Cmasillon:
Thank you for the good advice on the Update Combo. I've been running Snow Leopard since it was relatively new. As of recently, I had been unable to open any .mov files with my Quicktime 7 Pro and was getting the "OSStatus error -50" error message whenever I tried to do so. I don't know when and why that problem/conflict arose, but I had downloaded and installed Microsoft Office 2011 for mac about a month ago and this was the first time that I'd seen that error message. Can't really blame it on MS, but if it walks like a duck...
Given that fact, I tried to use my Quicktime 10 to trim those videos. They opened and played in QT 10, but after I'd trimmed them and tried to Save them - whoops, the "OSStatus error -50" message again. It wouldn't let me save my chages. (QT 10 would first tell me that I couldn't save under that filename, prompting me to try to change the name, to no avail.
Previously, the only problem I'd experienced was that my Quicktime 7 Pro would crash if I clicked to open a media file in the Finder without first having opened QT 7 Pro. My make-do solution for that was simply to keep in mind that I needed to open the ap first. When I had previously tried to download and re-install QT 7, the machine wouldn't let me do it, saying that QT 7 was already installed. - Frustration galore -
Anyway, I was recently able to download and install Quicktime 7 version 7.6.6, which is acceptable to Snow Leopard. I also saw your post about having resolved your problem by downloading Combo Update 10.6.7 for OSX Snow Leopard and immediately clicked on "Software Update" the combo update included 10.6.8 update for Snow Leopard, so I downloaded and installed. Boom! my problems are all gone. Quicktime 7 Pro and Quicktime 10 both work as they should, and I don't even have to pre-open 7 anymore, so I can simply double click on QT 7 files in the finder.
Thanks again for pointing me in the right direction.

JRE 6.3 won't run on Solaris machine

Hi all
I've just tried to install the latest JRE on a Solaris 5.8 SPARC box. Downloaded, untarred and setup the path fine. However, whenever I call java, I get:
Error occurred during initialization of VM
dlinfo SERINFOSIZE request: ld.so.1: java: fatal: __vsnprintf: can't find symbolThis also happens if I try java -version, making me think it's a pretty basic error occurring early on. ld.so.1 seems related in some way to linking and, although I'm not doing in dev/compiling here, I did have set up a fair few symbolic links across my system that all point at bin/java.
I'm completely stuck. Thinking it's a missing library, I reuntarred (what a word..) - same problem. The soft links and paths all look good. Any idea what I should look at next?
Thanks!

uninstall the JRE 6u3 then re-install it:
- 32 bit OS: http://java.sun.com/javase/6/webnotes/install/jre/install-solaris.html
- 64 bit OS: http://java.sun.com/javase/6/webnotes/install/jre/install-solaris-64.html
(http://java.sun.com/javase/6/webnotes/install/index.html)

Stand alone labview application (.exe file) does not run properly

Hi all,
I am trying to make a stand alone labview application to run on another computer ( I have never done this before).
I went through the tools->build application prompts and was able to build an exe file.
the program is supposed to control a power meter and make power measurements then save them to a text file.
When I run the exe file, on the same computer I compiled the exe file on, the program generates a text file to save data to but it can not communicate with the power meter.
There are some sub-VIs and a dll file that are used to communicate with the power meter. Could it be that I am not telling labview to correctly
include these files when I create an executable?
What are some common problems that occur when generating stand alone applications that could be causing my issues?
And does anyone know of any good tutorials on generating stand alone applications in labview other than the NI help files?
Thanks for your help,
Solved!
Go to Solution.

edCubed wrote:
Hi Bill, thanks for your suggestions.
I haven't tried to run this app on another computer yet. I'm just trying to run it on the computer it was developed on.
The computer I developed it on has all the drivers/resources I need to control the power meter.
Also, I don't know how to include the VISA runtime with my installer. could you explain how this is done?
This is the first time IV tried to turn any labview programs into stand alone exe files so I don't anything about how to do it other than what I've seen in youtube videos and help files.
If you know of any good tutorials that will help me figure this out I would appreciate it.
Thanks,
My fault - I didn't read that this was the same computer. I know the very end of Core 3 studies shows how to build an executable and installer, but even that is very general. I'm not sure if there exists a tutorial on how to do it.
As for including the runtimes, when you build an installer, you have to include the runtimes that your executable will need. It's fairly straightforward.
Since it won't run on the machine that built it, I'll have to think about it a little bit...
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

What won't run in Rosetta?

Hi,
What type of Apps will not run in Rosetta?
Michael

For one, Apple's own Pro software will not run on these computers, despite the fact that they are using Final Cut Pro as a benchmark on the iMac/MacBook product pages. Final Cut Pro or Express, DVD Studio Pro, Logic, Logic Express, Aperture... you'll have to wait until the Universal Binaries come out (supposedly in March), and then you'll have to pay to "upgrade."
I can't believe they are using benchmarks from pieces of software that won't run on these machines (yet) to sell them. Someone who didn't do his research would think these machines would be great for Final Cut, only to find out they don't run them, period.

Labview 2011 executable does not run on AMD Quad Core

I have recently bought a brand new Toshiba Satellite with AMD Quad Core- A8-4500M 1.9GHz processor and Windows 7 OS. It does not run any labview executables. It runs on all my Intel machines without any problem. This is the first AMD ever bought (and the last). I need help in resolving this problem.
When I run an exe on the AMD, under Task Manager\Processes, I do see *.exe process running, but the Memory usage goes up and tops off at 100% and then it returns to 0. It's like a saw tooth waveform of memory usage, as if it's looking for some missing files. I have cleaned up the computer twice now and even a simple Add Two Numbers.exe does not work on this AMD.
Any clue, anyone? please?

I believe you are running into the problem described in this KB.
http://digital.ni.com/public.nsf/allkb/4734A6405B123FA58625799900813593
Regards,
Jon S.
National Instruments
LabVIEW R&D

When running labview's test executive I recieve runtime error: Call to step "PRE-RUN" failed. Could someone explain this error?

I have a set of vi's that work when run under labview. However, when calling these vi's from labview's test executive I recieve runtime error: Call to step "PRE-RUN" failed. in Assign Connector Pane.vi->Call Test.vi->Execute Pre-Run.vi->Test Executive. Could someone explain this error to me? (or ideally tell me how to fix it?) Thanks.

Hello,
There are any number of possible causes to this problem. Which version of Test Executive are you using? Have you upgraded your Test Executive recently? The latest version is 5.1.1. If you have changed anything about Test Executive on your computer recently, I recommend you perform a mass compile of all your VI libraries, as having different versions of the VIs on your system could often result in the "Call to Step XYZ Failed" errors. Also, are you using any DAQ or Analysis VIs in your steps? We have seen problems where the use of DAQ or Analysis VIs in the sequence can cause intermittent "Call to Step...Failed" errors. There are some KnowledgeBase entries on our website that discuss this problem. Are you using the Test Executive in the VI environment, or
as an executable? Again, there are some problems with using Test Executive as an executable that result in these errors, and there are also KnowledgeBase entries that discuss these problems.
If you have a pared-down application that demonstrates the problem, feel free to send me your VIs and your .seq file and I will try to reproduce the problem.
Alternatively, I would suggest you visit www.ni.com/teststand to learn about TestStand, our state-of-the-art Test Sequencing software that completely outperforms Test Executive. It is very easy to use and much more powerful, and we have a top-notch support team available dedicated exclusively to supporting TestStand. As you are probably aware, we are no longer developing Test Executive, and instead are concentrating our efforts on making TestStand the penultimate solution for all our customers' test sequencing needs.
I appreciate your patience on this issue. Please let me know if I can offer further assistance.
Have a pleasant weeken
d.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Mac executable file won't run on Mac

I am trying to get a mac executable file to run on a mac. It has been authored in Captivate 5.0 PC version.
I have tried to run it on a Mac book, about 5 years old and nothing opens at all and same on an old G4. I have had no other opportunity to test it on another mac.
The the html/flash version plays ok in safari, but not .app or PDF. All files designed to run on PC run ok.
I am a complete novice on mac's, but assume that opening the .app file like an .exe file on PC will launch the program.
The package I have made is about 96 mb as a .app file and is about 80 odd slides long and also contains an number of flv files.
I have been looking very hard to see if anyone else is has experienced the same or similar problem and have found nothing useful.
I would assume it has nothing to do with flash player as everything that the program needs should be self contained in the executable.
Thanks

The G4 is running OS 10.2.3.
I created a test Mac projector in Director then tested it on the same Mac and the .classic and .osx files ran ok.
Do you think it is an issue with Captivate .app files not being compatible with early version of OS?, or something more fundamental with the .app files and the OS.
I guess there is no realistic way to convert the Captivate .app file directory to a .osx file?, as there may well be occasions when the package will be used on older Mac OS systems.
I will try and get it tested on a later OS System.
Many Thanks

My aplication won't run if debugging is not allowed

I am using Labview 1011
I have one application with debugging not allowed in the file settings, it won't run and I have to use task manager to stop it.
this is only with the Application Builder. And my other applications do not have this problem. What can I look for?

Well it might be helpful to know what you've already tried; what makes you think that the debugging setting is what is causing your issue? Does the program execute as expected in the development environment? (ie, not as an executable) Does the executable work when debugging is allowed? Just because you can't get a program to respond to the user interface doesn't explicitly mean that it isn't executing; it could be stuck in a loop. Are you using the Current VI Path constant within your program? This will return a slightly different path from the development environment than when in an executable (see the link for more detail).
http://digital.ni.com/public.nsf/allkb/FD7DE8BC8FFC256C862565F4006BE363
Providing more information should help someone to point you in the right direction.
Tessa

Labview 8.5 executable won't run on Runtime Machines

Similar Messages

Maybe you are looking for