Solution
This issue can occur when TestStand is unable to find the proper code modules at the path specified. In order to resolve this issue, it is recommended to
use a TestStand Workspace File to create the deployment. By using a Workspace File for the deployment, TestStand will internally resolve path errors and circumvent this issue. If the issue still occurs after creating a Workspace File, be sure to manually add any code modules that can't be found to the Workspace.
If the issue still occurs after the step and your code modules are included in a LabVIEW project, try adding the project path for each code module called your sequence file. When prompted, add the directory that contains the file you selected to the list of search directories :
The step settings for code modules that are in a project should look like the following :
For databases, if the above-mentioned steps do not work, instead of the using the path or the connection string in TestStand, declare a local string and save the path/connection string in the local string. Then use the local string to specify the database path.