Problem with LabVIEW RunTime Server after Remote Execution of TestStand Sequences using VB

[Sunny]

Hello,

We use custom build steptypes in TestStand. One step of most of these steptypes is the call of an Labview VI.

Everything is working fine while i'm use the TestStand Sequence Editor to run any sequence including the Remote Execution Call of one of these Steptypes. But if i use the method NewExecution from VB (no ModelEntrypoint and run of MainSequence) for any sequence calling these steptypes the LabVIEW RunTime Sever (running on the Remote Server) is closed after the Execution of the first steptype (with any VI -Call inside).
What is the reason for this different behaviour an how
can i avoide the shutdown of LabVIEW Runtime Server on remote machine?

Thanks,
Sunny

[rpfi]

Hello Sunny,

When you say you use the method NewExecution, are you using the default VB OI shipped with TS or you created your own? Before calling the NewExcution method you should use the Engine.LoadTypePaletteFiles() method to load the types into memory. Inside those VIs you are calling from your step types, are you invoking LabVIEW methods like quit application, etc? Are you using TS method calls inside this VIs? I guess we need some more information...

Besides that, what if you create a very simple step type that just calls a VI that does nothing inside, does it work?

Regards,

Roberto Piacentini
National Instruments
Applications Engineer
www.ni.com/support

[Sunny]

Hello Roberto,

Sorry, the problem wasn't exactly described in my question. I continued in evaluting the behaviour of TestStand Engine and LabVIEW RunTime Server.

The Problem is that even if the LabVIEW Runtime Server isn't started from TestStand Engine (we start in Autostart folder of Windows), the LabVIEW Runtime Server will be shut down after closing TestStand Editor (or any application using the TestStand Engine), if any steptype using the LabVIEW Runtime Server was executed before.

Could this be avoided with any workaround?