08-26-2009 07:44 AM
Hi all-knowing forum
In the attached file, I have a VI called CheckFileSrvForGODialog.vi in the ModelSupport folder. When I try to add this file as an "Action" step in TestStand 4.1 I get an error -180002 "The VI is not executable. Most likely the VI is broken...".
I see this error only when I use LabVIEW run-time engine as my LabVIEW adapter. If I use LabVIEW development as my adapter it runs without errors. (with LabVIEW 8.6).
I have made sure that the correct folders are in the TestStand searchDirectories and I have searched this forum and tried various solutions that I found from others. Bu, alas, none of it seems to help.
Any good suggestions?
B.R.
Martin
Solved! Go to Solution.
08-26-2009 07:30 PM
Hello Martin,
Are you running your sequence on your development machine or a target machine that you deployed to? What version of the LabVIEW Run-Time Engine have you configured the LabVIEW Adapter to use? If the CheckFileSrvForGoDialog.vi or any of its subVIs are not saved in the same version of LabVIEW as the Run-Time Engine that you are attempting to execute them with, you will receive Error -18002. Have you tried mass-compiling your CheckFileSrvForGoDialog.vi? Please see the following KnowledgeBase Article for reasons why you might be receiving this error:
08-27-2009 01:42 AM
Hi Manooch_H
I am, currently, running it on my development PC - Later it is supposed to be distributed to our test PC's.
Everything should be mass-compiled, at least as far as I know (unless some subVIs were hiding when I did the mass-compile). I have set the run-time adapter up to use LV 8.6, which is the same LV version that I have used for developing the code.
I will check the knowledge base article for hints, thanks.
/Martin