Error 7 File Not Found for LabVIEW Code Modules in TestStand

Updated Apr 4, 2023

Reported In

Software

  • 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.

Solution

To prevent this error:
  • Ensure any VIs with the same name are being called from the same VI Library or VI instance.
  • Ensure the unit under tests have internal serial numbers assigned to them.
This error can also occur because of a TestStand known issue reported in the 2019 and earlier versions of the software, in which TestStand generates the VI file path by replacing LabVIEW\ with TestStand\bin\. With that:
  • Call the VI directly and do not specify a project path.
  • Do not save LabVIEW projects in the instr.lib, user.lib and vi.lib directories.
  • Change the adapter settings to the LabVIEW Development System.
  • Build a deployment of the TestStand workspace or sequence, as the TestStand Deployment Utility moves the dependencies to a different location that does not experience this issue. Please refer to this article for guidance on Deploying LabVIEW Code Modules with NI TestStand .
In case VIs included in an add-on package are being used, try reinstalling the add-on.

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement may be required, and support options vary by country.