Error 17600 When TestStand Code Module Uses a MathScript Node with LabVIEW Run-time Engine

Updated Jan 29, 2018

Reported In


  • TestStand
  • LabVIEW MathScript Module
  • LabVIEW

Issue Details

In my TestStand sequence, I am calling a LabVIEW VI code module which contains a MathScript node. This step executes successfully when using the Development Environment setting in the LabVIEW adapter, but I receive the following error if I attempt to execute it using the Runtime Engine setting:

Error Loading Step '<Step Name>' of sequence '<Sequence Name>' in file '<Sequence File name>'.
Failed to load VI '<VI path>'in the LabVIEW Run-time Engine version '<RTE version>'

LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located.  Select File>>Open to open the VI and then verify that you are able to run it.

VI Path: <VI path>

Error Code -17600, Failed to load a required step's associated module.
Source: 'TSAPI'


However, when I open the VI, it can execute successfully. Why is this error occurring?


This error occurs because the MathScript node requires VIs in vi.lib in order to execute. When using the LabVIEW Run-time Engine, the dependencies are not found because these VIs are not present in the Run-time Engine. You can prevent the error using the procedure below:
  1. In LabVIEW, create a source distribution containing the code module VI. Refer to the LabVIEW help topic Building a Source Distribution for more information on creating a source distribution
  2. In the Project Explorer, expand My Computer. Right-click Build Specifications»New»Source Distribution
  3. In the Additional Exclusions tab of the My Source Distribution Properties window, uncheck the following settings:
    • Exclude Files from vi.lib
    • Exclude Files from instr.lib
    • Exclude Files from user.lib
  4. Build the source distribution
  5. Configure the TestStand step to call the VI in the newly created source distribution folder

Additional Information

When deploying a TestStand system, the TestStand Deployment Utility will automatically find the dependencies needed for the MathScript VI to execute. For this reason, the above procedure is not required to use MathScript VIs on a deployed target.


Not Helpful