Home Support Documentation Bugs

TestStand 2020 Known Issues

Created Jun 20, 2023

Overview

This document contains the TestStand known issues that were discovered before and since the release of TestStand 2020. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.

Bug Number

Legacy ID

Description

Details
1058021

Unable to load DLL when using VisualStudio 2019 with the .NET adapter in 64-bit TestStand 2020

There is a problem with loading a DLL when creating code in VisualStudio 2019 using the .NET adapter in 64-bit TestStand. The following error occurs:


Could not load file or assembly '.Microsoft.VisualStudio.VCCodeModel.dll' or one of its dependencies. is not a valid Win32 application. (Exception from HRESULT: Ox800700C1) Error Code -18500, An error occurred during Visual Studio automation.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand 2020

Resolved Version:

N/A

Added:

N/A
959623

Some LabVIEW Classes cannot be found in vi.lib, user.lib, or instr.lib

When you create Action steps that call LabVIEW class members from classes located in vi.lib, user.lib, or instr.lib, TestStand returns edit time errors. The VI icons and parameters are not loaded when these errors occur. The errors may occur whether you select to use an absolute or relative path to the LabVIEW class.


After placing the step, the following error may occur:

LabVIEW: (Hex 0x7) File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.


When going back to step after clicking off of it, the following error may occur:
 
The parameters specified by the step do not match the controls and indicators of the VI, or the VI may be broken.

Click this icon to reload the prototype, which maps the current arguments to the controls and indicators wired to the VI connector pane.

If the error persists, open the VI in the LabVIEW development System and ensure it is not broken.

Workaround:

Open the class in LabVIEW and then TestStand will load them correctly.

Reported Version:

TestStand 2017 SP1 | TestStand 2019

Resolved Version:

N/A

Added:

N/A
1147098

Unexpected behavior while using old layout files in TS20

When TestStand loads a layout file, layout_current.bin, created from an earlier installation of TestStand, an unstable layout may occur. 


The toolbar may have extra icons and the tabs for Variables and Sequences may be below the panes instead of above. The title of the Insertion Palette may also be incorrect.

Workaround:

There is currently no known workaround for this issue. Select View > Reset UI Configuration... to reset the UI configuration. 

Reported Version:

TestStand 2020

Resolved Version:

N/A

Added:

N/A
1127168

The transparency mask in the new icons is not set or it is not correct

The new TestStand icons do not have their transparency information set correctly. Since the transparent color is not blended properly with the background, the icons look distorted when display in some controls like buttons.

Workaround:

There is currently no known workaround for this issue. You could use custom icons. 

Reported Version:

TestStand 2020

Resolved Version:

N/A

Added:

N/A
1141795

Cannot Redo inserting a sequence after undoing it in full-featured UIs

In the Full-Featured TestStand UI, when users undo inserting a sequence and then try to redo inserting a sequence, they will encounter the following error: "Index out of range. [Error Code: -17301]"

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand 2019

Resolved Version:

N/A

Added:

N/A
1144328

Doing 'SaveAs Previous' resets the values of Python and LV NXG adapter specific extended data types to default in the original file

When you create a sequence file in TestStand 2020 that has custom data types with non-default values, saving it in a previous version resets the values to default. This is an issue with the Python and LabVIEW NXG adapters.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand 2020

Resolved Version:

N/A

Added:

N/A

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

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