Error -19034: TestStand Deployment Utility Unable to Execute Files

Issue Details

• I keep seeing error -19034 when using TestStand™ Deployment Utility. How can I fix this?
• I am trying to create a deployment image using TestStand Deployment Utility, but the following error occurs:

Solution

1. Ensure that TestStand is using the Run-Time version of LabVIEW. 
   • This is the recommended version for deployment because deployment machines often do not have the LabVIEW Development Environment installed.
   • Refer to How to Change the LabVIEW Version TestStand Uses  for instructions.
2. Verify that LabVIEW is not running in the background before creating the deployment.
   • This will ensure that existing VIs are not being held in memory.
3. If multiple versions of TestStand are installed on the host PC, change the active version to re-register the TestStand API VIs.
   • Open the TestStand Version Selector application.
   • Select a different version of TestStand under the Installed TestStand drop-down menu and click Make Active.
   • Revert back to the original active version of TestStand to re-register it.
4. Mass compile all LabVIEW VIs to ensure that the deployed VIs are using the correct version of LabVIEW.
   • Refer to How to Mass Compile in LabVIEW for instructions.
5. Open the TestStand Deployment Utility Build Log to find additional details about the error.
   • To create a Build Log, click the Save Log button at the top of the Build Status tab of the Deployment Utility.
   • Investigate the Build Log and Status Log files to determine the source of the error.
6. Navigate to the directory of the problem VI and verify that the VI can run independently of TestStand.
   • The error shown above refers to a problem with TestStand - Read Linker Info from File LV 8 or Above.vi, which is a part of the Distribution VI.llb library located in C:\Program Files (x86)\National Instruments\TestStand <version>\Components\Tools\Deployment Utility\DistVIs\<version>.
7. If the problem VI is broken or missing, reinstall TestStand.
   • Ensure that all TestStand Additonal Packages are reinstalled to verify that the old installation has been completely overwritten.
   • Refer to Uninstall NI Software or Drivers Using NI Package Manager for further instructions.