This document contains the SystemLink known issues that were discovered before and since the release of SystemLink 2021 R3. 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 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: Dec 10, 2020 |
|
| 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 |
|
| 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 |
|
| 1706828 |
DataFinder stopped because SL TDM Database Service crashedWorkaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.1 Added: Nov 24, 2021 |
|
| 1703771 |
Analysis Automation quick action "Go to task definition" does not workWorkaround: Click Refresh in your browser and then use "Tasks" tab to navigate to task definition.
|
Reported Version: SystemLink 2021 R3 Resolved Version: SystemLink 2021 R3.1 Added: Nov 24, 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 |
|
| 1812554 |
TestStand fails to generate PDF report when the SystemLink client is disconnectedPDF 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"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 ForwardStored 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:
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 quarantineBatch 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 TestMonitorClientXML, 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 completeIf 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' timeSteps 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 crashIf 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 requestsIf 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 ClientThe 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 |
|
| 2054336 |
Writing NaN to a Tag Can Cause a Tag Historian Service CrashApplications 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 timeThe 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 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 |
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