SystemLink 2021 R2 Known Issues

Overview

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

1531598

Systems Browser - Build Query slide out becomes unresponsive after removing blank query item

When using the Build Query slide out to create a filter from the Systems Browser, it is possible to get into a partially unresponsive state. One way to get into this state is via the following actions:
  1. From the Systems Management -> Systems page, click the filter icon to open the Build Query slide out
  2. Press the blue "+" button to add a new query item
  3. Delete the new item via the "x" button on its right
  4. Click into a field in a query item and note that it no longer auto-populates and the rest of the item becomes unresponsive
To confirm this is the behavior you're seeing, open your browser's development tools and navigate to the console tab. Repeat the steps that caused the failure and you should see the following output:
Error TypeError: Cannot read property 'dataValue' of undefined
at HTMLElement._openEditorByFieldType (main.767261e...js:106)
at HTMLElement._openEditor (main.767261e...js:106)
at HTMLElement._clickHandlerFilterButton (main.767261e...js:106)
at HTMLElement._clickHandler (main.767261e...js:106)
at HTMLElement._documentDownHandler (main.767261e...js:106)
at HTMLDocument.d (main.767261e...js:106)
at f.dispatch (main.767261e...js:106)
at l.invodeTask (polyfills.af259fe...js:1)
at Object.onInvodeTask (main.767261e...js:106)
at l.invokeTask (polyfills.af259fe...js:1)

Workaround:

option 1: Press the blue "+" button again to add a new item. All items in the query should become responsive again. Delete any unused query items once you've configured the query fully.
option 2: Press the "Cancel" button on the slide out and recreate the desired filter, avoiding the steps that caused the failure.

Reported Version:

SystemLink 2021 R2

Resolved Version:

N/A

Added:

Jul 19, 2021

1523458

The 'Edit Grid' slide-out is empty when a non-existent property is selected

When the Systems grid is configured to group by a custom property that is not present on any visible system, the 'Edit Grid' slide-out can become empty and un-configurable. This can happen by deleting a custom property or by applying a filter that excludes all systems with the property being used for grouping.

Workaround:

To resolve the issue, update to SystemLink 2021 R2.1

Alternatively, you can identify the property in the grid that no longer exists, and ensure it is present on a visible system. This will allow you to edit the grid configuration and remove that grouping from the configuration.

Reported Version:

SystemLink 2021 R2

Resolved Version:

SystemLink 2021 R2.1

Added:

Aug 13, 2021

1706828

DataFinder stopped because SL TDM Database Service crashed

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R2

Resolved Version:

SystemLink 2021 R2.2

Added:

Nov 24, 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

2054336

Writing NaN to a Tag Can Cause a Tag Historian Service Crash

Applications writing to double tags with history enable can cause the Tag Historian Service to crash if the value written is not a number (NaN).

Workaround:

In your application writing tag values, include additional logic to filter NaN values prior to writing to the tag service.

Reported Version:

SystemLink 2021 R1

Resolved Version:

SystemLink 2022 Q1 Patch 3

Added:

Oct 28, 2022

2266174

SystemLink Client performance degradation over time

The SystemLink TrayApp on the client system starts a tcp-server in order to get job notifications. This mechanism enables pop-up notifications informing the current user that a job started/completed. This has to work for any user that can login to that system and for Windows Server we have to support the use-case of multiple users being logged-in simultaneously; each user has their own tcp-server on its own port.

The ports are persisted on the disk in this location: C:\ProgramData\National Instruments\Systems Management\NIMinionConfig\ports

Over time, this list may grow and will include users that are no longer active on the system. For each port that fails to connect, there is a 2 second timeout when attempting to connect. This results in delays of 2 seconds multiplied by the number of inaccessible ports for each job.

Knowledge Article associated with this issue: 

    Workaround:

    Manually delete the files corresponding to the users that are no longer logged in to that system.

    Reported Version:

    SystemLink Client 2020 R1

    Resolved Version:

    SystemLink Client 2022 Q1 Patch 4, SystemLink Client 2023 Q1

    Added:

    Mar 7, 2023

    2395617, 2435241

    TDM DataFinder Optimize Database function does not reduce database footprint when run after data is deleted from MariaDB

    In version of DataFinder Server Editions prior to 2014, executing the TDM DataFinder Optimize Database function would reduce the database footprint roughly proportional to the volume of records deleted from the database. This function could be used to help cleanup database after archiving old data. This does not function as expected when run after data is deleted from MariaDB

    Workaround:

    Setup multiple DataFinder instances and archive the entirety of the oldest database at a time, cycling through several instances to achieve desired volume of historical data storage.

    Reported Version:

    SystemLink: 19.5

    Resolved Version:

    N/A

    Added:

    Jul 27, 2023

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