VI is not Executable Error

[Heruta]

Hello. I have a TestStand project which works fine in developer enviorment. I deployed the project succesfuly, but After run the "Test UUTs" in the target Machine I got the Error "VI is not Executable". Please help ...

[RayFarmer]

Hi Heruta,

Do you have a development labview on the target system?
Are you running from an Operator Interface or from the sequence editor?

What Version of TestStand are you using?

If you do not have a full development System for LabVIEW you will need to configure the LabVIEW adapter to either use the runtime engine (For TS ver3.0 only) or the ActiveX Server "TestStandLVRTS" or the activeX server of the OI, if you are running from the OI. You can do this from the Menu item Configure | Adapters..

It, might be a path related problem. Where are your VI's in relation to the sequencefile. Did you using absolute paths or relative paths when you specify your VI's?

Did you use the deployment tools in TestStand?

Regards
Ray Farmer

[Heruta]

Ray Thanks !

I don't have development labview on the target system and I son't have development TestStand either.

I used the deployment tools of TestStand 3.0. I also configured the Labview adapter.

I am not sure about using relative paths in all the Vi's but I checked and found the Sub Vi's of the "non executable Vi" in the Support Vi's folder, so I hope it solves the problems of the sub Vi's path although I am not sure ...

Regards
Heruta

[Matt Pickard]

Heruta,

Hi. Are you using the LabVIEW Operator Interface? If so, my guess is that if you go back to your development machine and open the LV OI and configure the LabVIEW adapter to use the LV Run-Time Engine instead of the Development Environment that you would get the same error.

If that is the case, you might try running a different OI (CVI, C#, etc), which you can find at Start Menu >> Programs >> National Instruments >> TestStand 3.0 >> Operator Interfaces. If that works, then it is most likely a conflict between a LabVIEW code module and the LabVIEW OI.

First, try mass compiling your LabVIEW code modules and make sure that they are compiled (along with the whole hierarchy) for the same version of LabVIEW as your run-time engine.

If that doesn't
work, start by skipping all the LabVIEW steps inside your sequence file. The error should go away. Then unskip one step at a time until the error comes back. This should pinpoint the error and hopefully it will be obvious what is wrong. By the way, are you using Fieldpoint?

Best Regards,

Matt P.
Applications Engineer
National Instruments