VI not executable: Runtime error with TestStand 3.5 and LabVIEW 8.2 "Get Property" VI

[Edilberto]

Hello

This is my problem: I have a test sequence made in TestStand 3.5, I used also LabVIEW 8.2.

Everything was working perfectly while using Development system adapter configuration, even I was (am) using operator interface, however, when I changed to Runtime engine, my sequence stopped working and I got an error that say that one of my VIs was not executable, I checked this VI and everything seemed to be OK, but the error remained, I skiped the VI and the sequence started without a problem, so the issues is actually inside my VI, and it happened to be the Get Property/Set Property VIs, those you use to interact with TestStand, when I removed them all the tests were loaded and the sequence started OK (but useless for me without those VIs, of course). It's very strange since I'm using them throughout the sequence (even in a previous step), but only there they cause this failure.

Can somebody give me a clue?

Regards,

-E

[BeCeGa]

HI Edilberto, for receiving this error there can be different reasons, but as it only fails with the runtime and not with the LabVIEW Development system, it can be narrowed to 2 possible causes: the Runtime has a different version than the VIs or your VIs are using some support files from LabVIEW. When using the developer Environment LabVIEW manages all of this, here simply the VI can’t find its files.

The following KB has more details on this:

Why Do I Get Error -18002 "VI is not executable" with TestStand?

Hope this helps

Best Regards

[Edilberto]

Hi Benjamín,

Ok, the reason is the second one, I'm using support files that cannot be located, but only in a single step of my sequence... I'm not handling projects so, I'm not sure if I can make a source distribution, what else can I do to solve this problem?

Gracias

-E

[BeCeGa]

When you make your distribution with a workspace in Testand it makes some of the steps required to deploy you system in automatic form. For example it changes some of the absolute paths, so this reduce deployment errors in the following link you can se more about it:

Deploying TestStand Systems

So I would recommend using this tool in TestStand, the other options are make a source distribution from LabVIEW, or manually copy the support files that your VI is using to a directory where TestStand can find them.

Best Regards