Error 7 File Not Found for LabVIEW Code Modules in TestStand

Updated Jul 13, 2020

Reported In


  • TestStand
  • LabVIEW

Issue Details

I'm trying to call a code in a LabVIEW VI using an Action or Test Step in my TestStand sequence. I'm running TestStand using the LabVIEW Run-Time Engine in my adapter configuration, and I get the following error for some of my code modules:

LabVIEW: (Hex 0x7) File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.


You can prevent this error from appearing by using one of the methods below:
  • If you are specifying a project path for the VI, remove the project path. Instead, call the VI using a relative or absolute path without any project path chosen.
  • Change the adapter settings to the LabVIEW Development System.
  • Build a deployment of the TestStand workspace or sequence.
  • Ensure any VIs with the same name are being called from the same VI Library or VI instance.
  • If you are using VIs included in an add-on package, try reinstalling the addon.

If possible, avoid saving your own LabVIEW projects in the instr.lib, user.lib, or vi.lib folders.
Additionally, if VIs being called by TestStand have any dependencies that reside in these folders, this issue may also occur.

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.