I just wanted to direct other users to the KnowledgeBase article that describes the cause of the issue most people on this thread have run into, along with the solution.
I also have issues with TestStand 2010SP1 and the LabVIEW 2010 SP1 runtime.
Is this thread still alive ??
Here's a copy of an e-mail I sent to NI Support:
When you configure TestStand to execute VIs using the LabVIEW Run-Time Engine, all VIs called throughout the test must be saved by the same version of LabVIEW (the version that you set when configuring the LabVIEW Adapter to use the LabVIEW Run-Time Engine. This includes VIs called directly from the TestStand sequence, VIs called as subVIs of the VIs called directly from the TestStand sequence, and VIs called dynamically (using VI Server) from VIs that fall into one of the two previously mentioned scenarios.
When calling VIs from TestStand using the LabVEW Development System, you do not face this same restriction because the LabVIEW Development System will automatically re-compile any VI, that is saved in a previous version of LabVIEW, when attempting to load the VI.
You are experiencing errors because the LabVIEW Run-Time Engine cannot load one of the VIs used by your test application. Some steps that might help:
Hi Manooch H.
Teststand indeed tells me which steps fail.
I stripped one of my sequences to keep 1 failing step.
I opened the vi that i call in LabVIEW and didn't see the 'dirty dot'. However, still did the ctrl-shift run. And it saved a lot of library vi's (Open G) and a few motor classes that i use.
Afterwards, the sequence was able to load ...
I'll do some further tests next week and let you know the result.
OK, it all works now.
However, deploying seems very usefull to service our customer when the systems have moved.
But I'll keep this solution in mind when I have the same error again in other projects.
You may want to consider using the TestStand Deployment Utility to deploy your TestStand application.
I'm already using it. Building an installer of the code is easy and easy to deliver to my customer when he needs a few changes.
I am trying to complete the TestStand tutorial, and in part 11 Calling LabView VIs (Test stand User manual) I am supposed to load VIs from the NI Template.
I am using TestStand 2014 32-bit, seq editor 22.214.171.1244, and LabView 2013 SP1.
I am facing the same problem, warning message appears: "Unable to load VI LabVIEW Pas-Fail Test.vi with the LabVIEW Run-Time Engine version "11.0" The version of a subVI mighht not match the version of the run-time engine or a VI dependancy might be missing."
On the following link http://digital.ni.com/public.nsf/allkb/1AC89FA9E9424B6A86257904000624B4?OpenDocument
it says that the problem is only with LabView 10 or earlier.
On my system I have LabView run-time engine 14. What should I do?
Try changing your LabVIEW adapter to the 2013 Development system.
Run time can have issues with recompile and linkage to vi's.
The dev env is better with this.