TestStand Crashes When Calling 3rd Party DLL in a LabVIEW PPL

Updated Apr 26, 2023

Reported In

Software

  • TestStand

Issue Details

  • I have created a LabVIEW Packed Project Library (PPL) that consists of a VI that calls a 3rd party DLL. The VI runs without issues in LabVIEW. However, when I call the VI by referencing the PPL path in TestStand, TestStand crashes.
  • I am calling a DLL in LabVIEW using the Call Library Function Node. When I place an Action Step in TestStand, it crashes when trying to load the VI.

Solution

This crash can be caused by a number of factors. The steps below help to troubleshoot the issue.
Note: If the DLL is developed by a 3rd party, NI are not responsible for how it interacts with TestStand. Contact the DLL's developer to understand how the DLL works.
 
  • Remove the DLL-calling VI from the PPL and try loading it into TestStand using the VI's path rather than the PPL's path.
  • Ensure that the DLL has been configured to use the C or stdcall calling conventions.
    • Other calling conventions are unsupported and will result in a crash.
  • Check whether the DLL tries to create any files or folders.
    • Some DLLs will create log files for debugging purposes. If the DLL tries to generate this file in the TestStand application directory, a crash may occur due to insufficient permissions.
  • Generate a WinDbg Dump file for TestStand.

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 or active software subscription may be required, and support options vary by country.