This document contains the SystemLink known issues that were discovered before and since the release of SystemLink 2024 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; see Additional Resources.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 211182 |
Using the browser navigation buttons does not correctly change a queryOn 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 modePackage 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: Jul 19, 2023 |
|
| 1038431, 1379439 |
Stored test results can be sent to the incorrect server when client registration is changed while forwarding is in progressIf 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 AccountLogging 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 |
|
| 1360973 |
Transport Layer Security (TLS) negotiation of SCHANNEL-based SystemLink clients with NI Web Server fails intermittentlyWhen 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 |
|
| 1586216 |
Installing "NI SystemLink TDM Analysis Add-On" can fail on Windows operating systems with non-western character setsEspecially 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 |
|
| 2395617, 2435241 |
TDM DataFinder Optimize Database function does not reduce database footprint when run after data is deleted from MariaDBIn 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 |
|
| 2677018 |
TDM Data Navigator - Export, Add to Data Cart, Downloads are all disabled and grayed outInstalling SystemLink Server TDM 2023 Q3 Patch 3 results in the TDM Data Navigator UI having the Export and Add to Data Cart options, as well as the Downloads button disabled and grayed out. Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2023 Q3 Resolved Version: SystemLink 2023 Q3 Patch 4 Added: Apr 30, 2024 |
|
| 2805992 |
SystemLink Test Monitor service fails to start after upgrading the serverUpgrading Systemlink Server 23Q3 Patch 2 (or greater) to 24Q1 Patch 2 (or lesser) causes the Test Monitor service to fail to start. The service fails to load and reports an error with no details. To confirm if you are impacted by this issue, inspect the "C:\Program Files\National Instruments\Shared\Skyline\TestMonitor" directory and confirm that "NationalInstruments.TestMonitor.dll" is not present. Workaround: This issue can be resolved by repairing the Test Monitor installation. Back up any configuration files before executing the repair. |
Reported Version: SystemLink 2024 Q1 Resolved Version: SystemLink 2024 Q1 Patch 3 Added: Oct 14, 2024 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
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