In the company I work, we have a solution that uses both TestStand 2014 and LabVIEW 2014.
We work with Development version of both, but we Deploy our automation using TestStand and Labview Runtime engine 2014.
We were trying to deploy a new station, but when analyzing our project, the Teststand User Interface (Deploy version) froze.
I tried several things and decided to install TestStand 2014 and LabVIEW 2014 full version to try and debug the issue.
What I found out is that, when I create a new Sequence in TestStand, add a VI Action and try loading the Project Path, the TestStand freezes if I'm using the Runtime adapter.
If I switch to LabVIEW Development System Adapter in TestStand, it works. However, I need to use the Runtime since it is free while the LabVIEW Development is paid.
We already use our solution in other places, and this is the first time this has ever happened. The only post that I found online that had something to do with this issue is THIS ONE.
If I remove the Project Path and call the VI itself, as "dvu" said in his second post, it works.
However, this is something not good to do in our whole automation, since we have several LabVIEW Calls.
Any ideas about how to make this works with TestStand 2014 Runtime and LabVIEW 2014 Runtime only?
Thanks!