SystemLink 2022 Q1 Known Issues

Overview

This document contains the SystemLink known issues that were discovered before and since the release of SystemLink 2022 Q1. 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

211182

Using the browser navigation buttons does not correctly change a query

On pages with a query panel (Assets, Calibrated Assets, Reports, etc.), the browser back button does not work as expected. When a user presses the back button, the URL in the browser changes, but the filters do not.

Workaround:

Remove the filter using the X button next to the property selection field instead.

Reported Version:

SystemLink 19.5

Resolved Version:

N/A

Added:

Feb 27, 2020

1077209

Packages disappear from grid when viewed in Safari full screen mode

Package Repository application fails to display packages in the feed's detail view when done from Safari in full screen mode.


Workaround:

Use a different browser such as Chrome or take Safari out of full screen mode.

Reported Version:

SystemLink 2020 R3

Resolved Version:

N/A

Added:

Dec 10, 2020

1038431, 1379439

Stored test results can be sent to the incorrect server when client registration is changed while forwarding is in progress

If the store & forward plugin is already loaded and forwarding steps, it continues to forward to the original server connection even if the server is changed.  It will not switch servers while there are current transactions on disk and still successfully forwarding them.  Since simply switching the master does not invalidate the old API key, then if the server is still accessible, the forwarding plugin does not know that it should switch to the new master.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2020 R2

Resolved Version:

N/A

Added:

Dec 11, 2020

1350133

Windows login account cannot be used as TDM User Account

Logging into the Windows SystemLink servers with different user accounts can create issues with TDM services like DataFinder in case when one of these login accounts is also being used as SystemLink TDM User Account.

Workaround:

Assign a specific user/account to SystemLink TDM services.

Reported Version:

SystemLink 2020 R4 | SystemLink 2021 R1

Resolved Version:

N/A

Added:

Apr 27, 2021

1586216

Installing "NI SystemLink TDM Analysis Add-On" can fail on Windows operating systems with non-western character sets

Especially on Windows operating systems with non-western character sets, the character length of the temp folder can be that long, such that files temporary extracted during (pip) installation can result in a full file path exceeding the max path limit of the operating system.


Workaround:

Change the temp path location to a folder with a shorter name, for instance C:\temp.
Or enable the Long path support for Windows as described here:
https://github.com/pypa/pip/issues/6279#issuecomment-526864501

Reported Version:

SystemLink 2021 R3

Resolved Version:

N/A

Added:

Oct 12, 2021

1360973

Transport Layer Security (TLS) negotiation of SCHANNEL-based SystemLink clients with NI Web Server fails intermittently

When the NI Web Server is configured with a self-signed certificate, some installations seem to have issues with SystemLink clients failing to send HTTPS requests. Clients fail with a generic Secure Socket Layer (SSL) error even though the self-signed certificate on the server is valid, and correctly installed on the client. The client's browser and HTTP clients like cpprest correctly trust NI Web Server. But any .NET-based HTTP client using SCHANNEL will exhibit this behavior. When this happens, all targets registered to the server will fail in all sorts of strange ways, resulting in strange client-side behavior product wide.

We have determined that the behavior above is attributed to unusual TLS version negotiation within .NET Framework 4.6.2 itself, which configures SCHANNEL with unusual version negotiation behavior. Here is the Microsoft documentation explaining the problem: https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#configuring-security-via-the-windows-registry. According to this documentation, the behavior was changed in .NET Framework 4.6.3, whereas NI SystemLink uses 4.6.2.

Workaround:

As per Microsoft documentation, there is a set of registry keys which force 4.6.2 version of .NET Framework to default to the OS-level TLS negotiation behavior. We have confirmted that applying the registry keys to affected targets fixes the problem. You can find the set of registry keys along with values to apply in this documentation from Microsoft - https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#configuring-security-via-the-windows-registry


Please contact NI if you have trouble with the registry keys.

Reported Version:

SystemLink 2021 R1

Resolved Version:

N/A

Added:

Feb 28, 2022

1812554

TestStand fails to generate PDF report when the SystemLink client is disconnected

PDF report generation fails when using SystemLink Test Monitor with TestStand if the client HTTP connection status is disconnected or partially connected.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R3

Resolved Version:

SystemLink Client 2022 Q1 Patch 1

Added:

N/A

1828584

DIAdem cannot connect to DataFinder if user is in too many Windows Groups

When authenticating a connection from DIAdem or the LabVIEW DataFinder Toolkit to a DataFinder instance, if the JSON response containing the Windows Group IDs a user is a part of exceeds 8Kb, the connection fails with the following message.

"error":{"args":[],"code":-254851,"innerErrors":[],"message":"'windowsGroupSids' is required","name":"Auth.ValidationError"}

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R3, SystemLink 2022 Q1

Resolved Version:

SystemLink 2022 Q1 Patch 1

Added:

N/A

1939802

Steps may incorrectly be marked as failed or timed out when using Store and Forward

Stored requests that do not have a unique timestamp can be incorrectly sorted and forwarded out of order. Depending on the order, different symptoms can occur:
  • If the Main sequence step occurs before the create result step, the step and all of its children fail to be created
  • If the Update step occurs before the create step, the update step will fail and the step will remain in the running stage and will eventually timeout

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R1

Resolved Version:

SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2

Added:

Jun 10, 2022

1958992

Store and Forward Service may crash when there are too many items in quarantine

Batch forwarding, a new feature added in the 21.5.1 SystemLink Client reads the entire store directory into memory before forwarding. When the store directory is too large, this results in significant memory consumption, which can crash the service or result in undesirable side effects.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R3

Resolved Version:

SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2

Added:

Jun 10, 2022

1939771, 1944740

Reports may not be attached to Test Results when using Store and Forward in the TestStand TestMonitorClient

XML, PDF, System Software, and Asset Reports may not be properly attached to the test result when store and forward is being used. This is caused by a race condition that may mark the result update as complete before the reports have been attached, or if the System does not currently have a connection to the SystemLink Server.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R3

Resolved Version:

SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2

Added:

Jun 10, 2022

1955444

Store and Forward files may not be removed from disk after forwarding is complete

If multiple store and forward files have CloseFile updates with the same timestamp, only one will be removed from disk. This may result in extra files remaining on disk unnecessarily. 

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R3

Resolved Version:

SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2

Added:

Jun 10, 2022

1953405

Steps and Results created by TestStand when Store and Forward is enabled may have an incorrect 'Started At' time

Steps and Results that are created by TestStand when Store and Forward is enabled will have a 'Started At' time that reflects when they are created on the server rather than when the test ran.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R3

Resolved Version:

SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2

Added:

Jun 10, 2022

1939944

Unhandled Exception in the TestMonitor plugin may cause the Store and Forward service to crash

If an unhandled exception occurs in the TestMonitor plugin for TestStand when Store and Forward is enabled, the backing service may crash when forwarding quarantined Step or Result data.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R3

Resolved Version:

SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2

Added:

Jun 10, 2022

1947039

Unstable network connection may cause Store and Forward to skip requests

If forwarding is interrupted due to poor network connectivity, items with the same timestamp may be skipped when forwarding is resumed.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R3

Resolved Version:

SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2

Added:

Jun 10, 2022

1986882

Memory leak in Test Monitor Client

The Test Monitor Client has a small memory leak, the severity of which varies based on the number of steps run and the amount of data stored.

Workaround:

Restart TestStand to clear the leaked memory.

Reported Version:

SystemLink 2021 R3

Resolved Version:

SystemLink 2021 R3.3, SystemLink 2022 Q1 Patch 2

Added:

Jun 10, 2022

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