TestStand 2019 Bug Fixes

Overview

This document contains the TestStand Bug Fixes that were discovered before and since the release of TestStand 2019. 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 2019.

 

IDLegacy IDFixed IssueIssue Details
305338465052SequenceAdapter.GetSequenceFile() does not enforce Absolute PathIf you pass in a relative path to the SequenceAdapter.GetSequenceFile() Method's path parameter, the method accepts this and will execute, often causing errors.
305342544563GetGUIDAsString in Modelsupport2.dll does not generate properly formatted GUIDsThere is a missing hyphen when the GetGUIDAsString function is used to generate a GUID.
305345566400LabVIEW VI absolute path check does not handle PPLs properlyAt load time, when the LabVIEW Adapter checks VI paths to make sure they are not pointing to two different copies of VIs with the same name, the code does not properly account for packed project libraries (PPLs). If two steps reference a VI with the same name in the same PPL located in different places on disk, the first VI loaded should be used for both VI calls. However, because the function that checks the VI paths does not correctly handle PPLs, an error is generated.
305350658319Connector panes that reference large LabVIEW class hierarchies reload the entire hierarchy when selecting a step.If a LabVIEW step references a VI whose connector pane uses data value references or directly uses a large LabVIEW class, the TestStand Sequence Editor reloads the step and all of its dependencies each time the step is selected.
305359678105The TestStand Deployment Utility returns the error -19062 when deploying components to a local repository or package installer.If the "NI Certificates Installer" package is not installed on the system, and NI Package Manager cannot locate the package on one of its feeds, when the TestStand Deployment Utility attempts to include NI Certificates package in the distribution, the build returns "error -19062: Could not calculate EULA dependencies".
305362684110Clicking on the filter icon for the file column in the log window of the TestStand LabVIEW NXG Conversion Utility throws an exception.When pressing the filter icon button in the TestStand LabVIEW NXG Conversion Utility, the exception "Object reference not set to an instance of an object." occurs.
305365684203Unable to load LabVIEW NXG VI under ThisComputer target from project in a path with multibyte characters.If you try to configure a step to load a LabVIEW NXG VI that is placed under the ThisComputer target in the project, and the project is located in a path with multi-byte characters, then you will receive the error "Error thrown in Get VI - LoadEnvoyAsync: Error loading envoy for specified document".
305369686846Calling DisplayFlagsDialog() in an application without the UI Controls does not expose the same functionality as an application that contains UI Controls 
305373691732Max and Min functions are not NaN aware in expressions 
305375695916"Access Denied" Error launching TestStand when Windows user name has Japanese charactersWhen trying to launch TestStand from a user with Japanese characters in the user name, TestStand throws an "Access Denied" error.
305381709638Timestamp UTC value will change for a LabVIEW VI step if the sequence file is opened in a different time zone but no edit is done to the step or sequence 
302428710154Editing a Sequence Analyzer rule that references a LabVIEW NXG code module crashes the Sequence Analyzer dialogIf a rule has been created in the Sequence Analyzer that refers to a LabVIEW NXG code module, then when the "Edit Rule" button is hit it will cause the Sequence Analyzer Available Rules dialog to crash.
306878711553Changing base destination of a packed project library in the TestStand Deployment Utility causes the build to failWhen building a packed project library with the Deployment Utility, you can select the .lvlibp item in the distributed files tab and change the base destination of the library. If you do so, the VIs in the library are incorrectly configured to have a destination subdirectory which matches the library name. This invalid setting causes the build to fail.
306392716835Time Stamp conversion fails intermittently when value passes between TestStand and LabVIEWAt random times when Time Stamps are passed back and forth between TestStand and LabVIEW, TestStand sends a Time Stamp string with a resolution of 0.0001 seconds instead of 0.001 seconds. This causes LabVIEW to default to an empty "00:00:00.000 PM MM/DD/YYYY" Time Stamp.
305388726406When using the FileOpenMode_Uniquify File Open Mode in the New CSV Output Stream, the non-uniquified name is shown in the report 
305336728989TestStand 2019 no longer supports selecting INI format for sequence filesTestStand now restricts you to selecting only the XML or binary formats. Configuring TestStand files to save using the INI file format is deprecated, and saving files in INI file format will be deprecated in a future release.

 

The following items are Bug Fixes in TestStand 2019 f1.

 

IDLegacy IDFixed IssueIssue Details
305876736115"Invalid VI Reference" reported during edit-time for a broken VI when the adapter is set to use the LabVIEW Run-time EngineWhen a broken VI is selected for the module in the TestStand LabVIEW step settings panel, with the adapter configured to RTE, the error message reports "Invalid VI Reference," which does not match what appears in the error log for the VI.
221029744812System error occurs when parallel sequence execution uses partial cluster passingSometimes a system level exception occurs when executing test sequence in parallel that are calling LV code modules which have clusters that contain arrays and are using partial cluster passing feature.

 

The following items are Bug Fixes in TestStand 2019 f2.

 

IDLegacy IDFixed IssueIssue Details
220503544646Error -17313 or -18005 occurs when passing a .NET refnum constant in a cluster from newer versions of LabVIEW into TestStandIf a LabVIEW VI with a cluster that contains a .NET refnum is passed into TestStand, then error -17313 or -18005 may occur. An example of this type of refnum would be when you create a constant from a .NET terminal in LabVIEW.
305866733179Override settings tab causes hang when running LabVIEW UI from development environmentFor a LabVIEW code module step, selecting the Override Settings tab in the LabVIEW module settings dialog causes a hang when running the LabVIEW User Interface from the LabVIEW Development Environment

 

The following items are Bug Fixes in TestStand 2019 f3.

 

IDLegacy IDFixed IssueIssue Details
1270788981523Could Not Load File or Assembly Error when Using Switching on TestStand StepsConfigure Switching settings for a Step causes the following error to appear: Could not Load File or assembly 'NationalInstruments.SessionMgr.Interop, Version=20.0.0.108, Culture=neutral, PublicKeyToken=ad9244eb3b825cd8' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT 0x80131040)
12708051106039Updating Packed Project Library Causes Missing or Prototype Changed Issues in TestStandUpdating a Packed Project Library in LabVIEW while the LabVIEW adapter is set to Run-Time Engine can cause strange behavior when you return to TestStand. For example, updated VIs in the PPL do not appear when browsing, or existing steps referencing updated PPLs display "File Not Found" or "Prototype Change" messages.

 

The following items are Bug Fixes in TestStand 2019 f4.

 

IDLegacy IDFixed IssueIssue Details
12708041172679Using TestStand Sequence Hierarchy View Causes Error and TestStand CloseOpening the TestStand Sequence Hierarchy View causes an error referencing an expired or invalid license, causing TestStand to close.

 

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).