TestStand 2017 SP1 Bug Fixes

Visão geral

This document contains the TestStand Bug Fixes that were discovered before and since the release of TestStand 2017 SP1. Not every bug fix known to NI will appear on this list; it is intended to only show the severe and more common issues that have been addressed.

Bug Fixes

The following items are Bug Fixes in TestStand 2017 SP1.

 

ID Legacy ID Fixed Issue Issue Details
657808 - The Deployment Utility does not find an environment file if any of the TestStand paths are the same as the path to the .tsenv file and are not the same as the global environment N/A
677099 - Error -19001 occurs when building a deployment if sequence file contains a packed project library that references a DLL. "Error -19001: File Not Found" can occur when building a deployment if a sequence file contains a reference to a packed project library and that library references a DLL
677891 - TestStand throws an error if a Sequence Context is passed into a variant control in LabVIEW N/A
680553 - When installing TestStand silently through a feed or package-based installer, the licensing prompt is displayed. N/A
682669 - ForEach Loop does not automatically close a Data Stream object after Break When using a ForEach loop to iterate over a data streams object, if a break statement occurs within a loop the ForEach loop will not close the data stream object. As a consequence, the data stream file is not closed.
692734 - TestStand Deployment Utility does not automatically include in a deployment the CSV files specified by the CSV Input Stream step N/A
692809 - Class Member Call causes TestStand to not release PropertyObjects after first call on shutdown with LabVIEW Development Environment The LabVIEW adapter must be set to the Development Environment. The calling step must have a project path referenced. This only happens the first time that the sequence is run and then TestStand is shut down after the execution. If the LabVIEW project is not open with the LabVIEW development environment, the TestStand warning dialog will list two references to PropertyObjects that were not released properly. If you reopen the same sequence afterwards, the error will not come up again.
696631 - The Edit code button is dimmed in the LabVIEW Specify Module dialog when displayed in a custom sequence editor that does not use the Application Manager The tool tip suggests that executions are running, even when there are no actual executions running.
696876 - TestStand errors when trying to load a polymorphic VI in the Sequence Editor When attempting to call a polymorphic VI, TestStand will report that "TestStand cannot call a polymorphic VI directly." If the VI is opened in the development environment and LabVIEW shows a dirty dot for the polymorphic VI, the error will not appear. The VI must be saved without LabVIEW indicating any unsaved changes for this error to appear.
703304 - UUT_RESULT records can not updated properly if all executions are terminated when using the Parallel model with on-the-fly database logging N/A
705097 - A Property Loader step reports an error indicating that the property could not be found when the option 'Skip if the properties does not exist in destination' is set and the sequence or a step does not exist. N/A
705578 - TestStand applications do not launch after installing Tool menu file for import when the file contains new and existing menu items already defined in an existing menu N/A
709093 - The Deployment Utility fails to build a deployment that contains a LabVIEW library with unused missing items If a LabVIEW library contains a reference to items that can no longer be found on disk and this library is included as a component in the build specifications for TestStand Deployment Utility, the build will fail. Even if the missing VIs are not referenced within TestStand, the build will fail if the items cannot be found within the LabVIEW library.
713198 - TestStand reports the error -17001 when loading a sequence file that was saved as a previous version and has the file contains a PreUUT callback sequence If you override the preUUT callback in TestStand 2017 and save the sequence file as 2016, TestStand reports an error when opening the file in TestStand 2016 or 2016 SP1.
713771 - Creating New Project from the LabVIEW NXG property node dialog errors with "Object Reference is not set to an instance of an object" N/A
714039 - TestStand is unable to select and configure custom plug-in for the Property Loader step type When you select a Property Loader step and choose a custom plugin in the Source Type drop down, the error "Object reference not set to an instance of the object" repeatedly appears and you have to end the TestStand process.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).