LabVIEW 8.5.1 executable opens on the task bar and then immediately disappears.

[javiucsd]

I have been using LabVIEW 8.5.1 for some time now and built several executables but now I have 2 executables that do not work on machines that I needed to install LabVIEW Runtime 8.5.1.

I installed the executable (which works fine on my development machine) on another computer.  It wouldn't run because I didn't have LabVIEW Runtime 8.5.1.  So I then installed LabVIEW Runtime 8.5.1, but I don't see it in the installed programs.  I now try running my executable again and it does open momentarily (I can see it in the task bar) but then it immediately closes.

I have since tried thsi with a completely different executable on a completely different machine that also needed LabVIEW Runtime 8.5.1 and teh same thing happens.

Any thoughts on why this is happening?

[smercurio_fc]

Since you were missing the LabVIEW Runtime on the target machine, it's quite likely that you're probably missing something else. What does your app do? What does it use? What does it do when it encounters an error? Do you log it? Do you display it?

[javiucsd]

It reads in a file, put the info on some graphs, does some simple calulations (averages, subtractions, etc.) and then creates an output file.

I don't know what it missing in the installation so I just installed the entire Device Drivers set from the LabVIEW 8.5 disc.  It previously had the device drivers from a 7.1 disc but apparently that was not enough.

Now it works but I don't know which package it was that I needed.  It would be nice if NI would tell us exactly which packages are needed for an install.

Thanks for your quick reply.

[smercurio_fc]

If that's all that you app was doing, then I can't see why installing the Device Drivers would have actually done anything, since you're not dealing with hardware, which is what's on the Device Drivers CD(s).

NI can't know what package you need for your app since they're not writing your app. The documentation that comes with the software indicates whether or not a runtime component is required. 

If you upload your code then we may be able to shed some light on this mystery. 

[javiucsd]

I don't know why it works by installing the device drivers but it does.  It doesn't make sense to me either.  It worked on 2 different executables which basically both read file, use graphs, do some simple math calculations and write an output.

I don't understand why couldn't the application builder know which packages are necessary for building an executable.  The builder already knows the list of LabVIEW VIs I am using.  I am sure some of those VIs are linked to some package.  For example, one of the packages says it is needed for 3D graphs.

Thanks for your help, though.

[Dennis_Knutson]

Did you actually create an installer or did you just build the app? Building an application has never included any drivers and never will. Creating the installer is where you have the option to include drivers and the LabVIEW runtime is one of those that is automatically included. Using some analysis functions also requires the lvanly.dll and this would also have automatically been included.

[javiucsd]

Dennis,

   Yes, I actually created an installer.  And it did include the lvanly.dll.  But for whatever reason LabVIEW runtime 8.5.1 was not enough for the exectuable to work.  Something on the Device Drivers makes it work but I don't know which one.  This application doesn't require me to save space so I can afford to put the entire Device Drivers but I have done other applicatiosn where memory space was an issue.