03-22-2012 10:27 AM
TestStand 2010 SP1, LabVIEW 2011, WinXP
Trying to build a deployment in TestStand.
During the build, I get the now-infamous popup:
Title: "Save Modified VIs?"
Text: "An error occured while trying to read the dependencies of your VIs; a possible cause for this problem is VIs not saved in the current version of LabVIEW. Would you like to save any modified VIs now?"
I select "yes", and the build then fails with errors in the log pane of the "Build Status" window. The error is:
Error: Unable to find all subVIs from saved VIs, either a subVI is missing or the VI is not saved under the current LabVIEW version.
The missing file path is: etc, etc.
I go to said missing path. The VI is in fact present. I open the VI and do "Save All", try again. Same thing. Then, I try a Mass Compile on the test VI directory. Attempt to build again, same error.
Note that I do call some VIs dynamically, but those are all present in my workspace, and are not found in this error.
Is there a debugging option or log file or some kind of trace I can do to dig into this and find out the state of things causing the error? Please help me out here.
-Andy
03-22-2012 05:18 PM
One quick way to narrow down the issue is to change your LabVIEW adapter to Run-Time engine and then try and run the sequence in the Sequence Editor.
Also, triple check your search directories and make sure you're not pulling in VIs from an unexpected location.
When you see that dialog it's already too late to save so trying to Save at that point never works.
Another tip is to ignore which VIs it says are not saved in the current version and instead look at the subVIs that those VIs are calling. You can run into this if you have two subVIs loaded with the same name.