How can I find out what top level VI TestStand cannot find a sub-VI for?

[trosier]

I am trying diligently to build a TestStand deployment and keep getting errors. TestStand is telling me that an error has occurred because it cannot find a sub-VI in a certain path. The problem is it does not tell me what VI it cannot find a sub-VI for. It just gives me the path that it is trying to find the sub-VI in. Is there any way I can tell what top level VI in a sequence TestStand is trying to find the sub-VI for? Thanks in advance for any help.

[Josh_W]

trosier,

In most cases, this error can be resolved by mass compiling your VIs.  However, there are two cases we know of where mass compiling does not save VIs correctly.  You need to correct these cases before mass compiling.

1. VIs in a Diagram Disable structure are not compiled by mass compilation, but are still included by a source distribution or TestStand deployment.
2. Read-Only VIs are skipped when mass compiling, but no warning is given.

[trosier]

Josh - I did not have any disbale diagram structures in the sub-VIs that were giving me trouble. Nor did I have any read only VIs. I mass compiled my entrire directory structure...twice. I had no choice but to go through every single sequence and open every VI. Once opened there were three that did not have the correct directory for a sub-VI and need saved. There were no errors due to a Labview mismatch. For some reason these three VIs did not save the sub-VIs new directory therefore causing trouble during my TestStand deployment build process. The thing I find odd about this is there are hundreds of other VIs that use these same sub-VIs in the same new directory that mass compiled fine. I am continuing my TestStand deployment build process and I will see how it goes from here. I definitely got further, after finding these three errros, than I have before. Thanks for the help.

[RayFarmer]

hi trosier,

Dont forget the teststand directories as well. VI's can come from these directories, therefore have to be at the same LabVIEW version.

Regards

Ray Farmer