Additional Information
This error can occur when a code module VI is contained in a LabVIEW project that is saved in the
instr.lib,
user.lib or
vi.lib folder. This is due to how TestStand generates the VI file path when using the LabVIEW Run-Time Engine adapter to locate VIs within projects. TestStand replaces LabVIEW\ with TestStand\bin\ when generating the file path, causing this issue.
The Development System can access these VIs by their relative path, fixing this issue. Additionally, when building a deployment, the TestStand Deployment Utility moves the dependencies to a different location that does not experience this issue. For steps on building a TestStand deployment, see
Deploying LabVIEW Code Modules with NI TestStand.
This is a known issue, seen here:
TestStand 2016 Known Issues. This behavior can also be found in known issues lists for previous versions of TestStand.