Well the .NET idea is interesting. I'm not using any .NET functions or containers.
Perhaps I'll get him to disable his firewall and install the .NET framework on his PC.
He is using windows XP SP3.
Thanks for the help people but it looks like I'm going to have to delve deeply into his PC confiuration to resolve this.
Try "mass compiling" (which physically opens and closes VIs in a directory versus "recompiling" the binary of VIs in memory):
Tools >> Advanced >> Mass Compile
"Mass compiling simply opens VIs up and closes them in an automated fashion. This has a couple of benefits:
If you would like to recompile the binary of the VIs in memory, press <Ctrl-Shift> and the run arrow of the main VI. While it is typical for nothing to happen after binary recompiling the VIs in memory, this can frequently fix/isolate many errors. "
If your application is really small, and not "highly commercial top-secret", then just post it here. We will try to run it, and you will get more suggestions why it happened.
Also you can post here screenshot of hierarchy, then we will see which toolkits/SubVIs was used and where you can get potential problems.
I had the same problem and I was using .NET objects in my code. A quick look into LabVIEW help files and I found "Note Creating and communicating with .NET objects requires the .NET Framework 1.1 Service Pack 1 or later. National Instruments strongly recommends that you always put VIs that use .NET objects in a LabVIEW project and not leave them as stand-alone VIs."
Looked into the PC where the application gave the error "This VI is not executable. The full development version of LabVIEW is required to fix the
errors" and of course no .NET framework there. Installed the NET Framework 1.1 and .NET Framework 1.1 Service Pack 1, rebooted the PC and voila it works 🐵
Sorry I didn't report back earlier. This is going backa while now but I finally narrowed the problem down to a classic list box. I found that installing .NET 3.5 fixed the problem.
Thanks for all your help.
I am receiving this same error. I am using LabVIEW 8.2 to create the execution file. The computer without LabVIEW has .NET 2.0. I have tried to create an installer and add the required dll files. My USB-6008 is active telling me the installer worked correctly. My program uses the DAQ assistant. This has many depentant vi's. Do they all need to be added as support files?
A LabVIEW application will report this error if it can't find any of the components it requires to run. This includes dlls, .Net, the runtime engines or even dynamically called VIs. I would make sure that all of your paths are correct, that you have installed all of the necessary components in their correct locations and that all the runtime engines are installed. This error message is the default message when a LabVIEW applications effectively ends up with a broken arrow.