LabVIEW Run Time Engine and ActiveX Automation Server

[Troy12]

Hi,

I have a question related to LabVIEW Run Time Engine and ActiveX Automation Server:

We have a tool developed in LabVIEW and TestStand. End user interface is a LabVIEW GUI (it's an executable) which executes TestStand sequences. Some TestStand sequences call lower level LabVIEW VIs.

Everything works fine with LabVIEW installed, but I was wondering if I could run this tool on deployment machine with only LabVIEW run time engine installed. We are using LabVIEW 6.1 and with only the run time engine installed, I get the error message: "Unable to launch the 'LabVIEW.Application' ActiveX automation server ". 

BTW, we are planning to upgrade the versions soon.

Is it possible to make things work only with the run time engine?

Thank you.

[Lycangeek]

Yes, those versions of LabVIEW/TestStand used the ActiveX server interface feature in LabVIEW - and that requires that you have the full IDE installed on the machine. Starting in LV 7/TestStand 3, we added support for using just the RTE, so it sounds like you'll have what you're looking for once you do upgrade.

[Troy12]

Thanks for the response, Brian.

I did upgrade to LabVIEW 8.0 and TestStand 3.5. Everything works fine on the development computer where LabVIEW and TestStand is installed. On the target computer in the lab, I installed LV RTE 8.0 and TestStand 3.5, and now when a VI is called in a sequence file, I get the following:

RunState.PreviousStep.Result.Error.Code  -18002 

RunState.PreviousStep.Result.Error.Msg  "LabVIEW: The VI is not executable"

So, the executable opens and works fine (which means that the LV RTE is installed properly), but when a sequence calls a low level VI, it does not make it through.

comments/suggestions are appreciated. Thanks.

[Lycangeek]

I'm not an expert in the TestStand side of things - the only thing that comes to mind is to ensure that the VI is compiled and saved for the version of the LV RTE you're using. If that doesn't fix it, I'd recommend posting the question on the TestStand forum to see what the experts there say.