A VI Dependency Might Be Missing Error Occurs When Loading TestStand Modules

Issue Details

I have a TestStand sequence that calls into several LabVIEW code modules. After I run the sequence, while preloading the modules, I get the following error:

Error calling sequence Single Pass.
Error loading step '[step name]' of the sequence 'MainSequence' in file '[filename].seq'.
Failed to load VI [VI name] in the 'LabVIEW Development System' version '[version number]'. Unable to load VI [VI name] in 'LabVIEW Development System' because the VI is broken.

A VI dependency might be missing.

"LabVIEW: (Hex 0x3EB) The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it.

LabVIEW reported an error. See 'LabVIEW: ' message for more details on how to resolve this issue. [Error Code: -18002]
 

Solution

This error indicates that the LabVIEW adapter cannot find a dependency of the VI that it is trying to load. Usually, this is due to not having a driver, toolkit, or other dependency installed on the system and can occur if the code modules were developed on a different computer than the one where the VIs are being loaded.

If you have the LabVIEW Development System installed on the computer, you can open the VI in LabVIEW to see what is missing.

• From the TestStand Sequence Editor (this option is only available when the LabVIEW Development System is being used as the LabVIEW Adapter):
  1. In the TestStand Sequence Editor, click the step where the VI is being called. 
  2. Next to the VI path in the Step Settings, click the Edit VI button to open the VI in LabVIEW.
• From LabVIEW:
  1. Open LabVIEW from the Start Menu.
  2. Click Open Existing.
  3. Browse to the VI that is throwing the error.
  4. Click the broken run arrow  to list the VI errors. This list will show you what specific subVIs and functions are missing.

Once you have identified the dependencies that are missing, install the corresponding driver or addon from NI.com/downloads or NI Package Manager. If it is a VI from a custom library, make sure that any LLBs or PPLs containing the VIs are copied to the system where the Sequence is being run and that they are located in one of TestStand's Search Directories.