Why are my VIs Broken after Building a Deployment with the TestStand Deployment Utility?Primary Software: Primary Software Version: 4.0.1f1 Primary Software Fixed Version: 4.2 Secondary Software: N/A
Problem: I’m using TestStand 4.1.1 or previous with LabVIEW 2010. When I build a deployment using the TestStand Deployment Utility, I receive the following error(s) after the build is finished: Aborted *************************************** Error: The following VIs are broken: <VI Path> while Processing VIs... ++++++++++++++++++++++++++++++++++++++ I notice that the deployed VI(s) mentioned in the error is actually broken when I open it with LabVIEW, but the original VI(s) is not broken when I open it with LabVIEW. Why are these VIs breaking during the deployment process? Solution: This problem is caused by compatibility issues with the inline subVIs feature added in LabVIEW 2010. This option can be used to decrease memory overhead and improve performance. In order to inline a subVI into its calling VIs, you must uncheck the Allow debugging and Enable automatic error handling options and check the Reentrant execution option of the VI Properties Execution page, otherwise the subVI will be broken. The TestStand Deployment Utility uses internal components to package VIs when building a deployment. The internal components used in TestStand 4.1.1 and previous incorrectly set the Allow debugging option of the VI Properties Execution page for every polymorphic VI and subVI being packaged causing any polymorphic subVIs that have the Inline subVI into calling VIs option enabled to break. NI-DAQmx 9.2.3 drivers enabled the Inline subVI into calling VIs option for some of their driver VIs (e.g. DAQmx Read and DAQmx Write VIs). Thus, if you were to use the TestStand 4.1.1 or previous TestStand Deployment Utility to deploy LabVIEW 2010 VIs that call DAQmx Read or DAQmx Write VIs, you would encounter this issue. You can work around this issue by disabling the Inline subVI into Calling VIs option for any subVIs that have the option enabled. If the workaround is not a viable option for you, please contact National Instruments Support. NOTE: This issue does not exist in TestStand 4.2 and newer versions due to updates made to the internal components of the TestStand Deployment Utility. Related Links: LabVIEW 2010 Help: Execution Speed: SubVI Overhead KnowledgeBase 3VME8NYV: What Do the Various Warnings Given by the TestStand Deployment Utility Mean? KnowledgeBase 4JDB8NT3: TestStand Deployment Utility Generates Internal Error When Locking VIs in Project Libraries or Global VIs Attachments:
Report Date: 01/20/2011 Last Updated: 02/01/2011 Document ID: 5HJGA6GI |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
