TestStand 4.1.1 Deployment Utility Built Installer with Custom Commands CrashesPrimary Software: TestStandPrimary Software Version: 4.1.1 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: I used the TestStand 4.1.1 Deployment Utility to build an installer that includes custom commands that execute after all files have been installed. When I run this installer on a target machine without the NI TestStand Engine installed, the installer prompts me to finish but an error occurs with the Wait Then Run MFC Application when it attempts to execute my custom commands.  Solution: This is a known issue introduced in TestStand 4.1.1, and has been fixed in TestStand 4.1.1 Patch 132949. Please download the patch and follow the installation instructions to fix this problem. Apply the patch to the development system before you use the TestStand 4.1.1 Deployment Utility to build an installer that uses custom commands. The problem is due to the Wait Then Run.exe program which controls the execution of custom commands. The version that shipped with TestStand 4.1.1 requires that the TestStand Engine already be registered to work. The patch includes an updated version of this executable which does not require the TestStand engine to be registered to work correctly. Related Links: TestStand 4.1.1 Custom Command Patch Attachments:
Report Date: 11/19/2008 Last Updated: 11/21/2008 Document ID: 4RI8D1T3 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
