This document contains the SystemLink 20.0 known issues that were discovered before and since the release of SystemLink 20.0. 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 |
|---|---|---|---|
| 966801 |
Asset self-calibration status does not update after unlocking a locked systemAttempting to start an asset self-calibration on a locked system will correctly show "System Locked (changes suspended)" under Status. If the system is subsequently unlocked, the status will change to "Self-Calibrating" but will not update further. This issue is cosmetic only, and the self-calibration completes correctly.
Workaround: Run the self-calibration again with the system unlocked to reset the status.
|
Reported Version: SystemLink: 20.0 Resolved Version: N/A Added: Feb 27, 2020 |
|
| 972321 |
Querying TDM Reader for multiple files by ID may error on large requestsThe Web Server logs shows the following error: Service for routing key [Skyline.TDMReader] did not respond within the timeout of 30000 milliseconds.
Workaround: Reduce the number of files requested in a single query to avoid a timeout.
|
Reported Version: SystemLink: 20.0 Resolved Version: N/A Added: Feb 27, 2020 |
|
| 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 |
|
| 959907 |
Test results group by selection is ignored when a filter is changedThe Test Monitor test results table allows grouping results by property. When a user selects a group by property and adds a filter, the group by behavior is incorrect. Results are shown separately instead of grouped.
Workaround: Select a different property to group by and then re-select the original property to reset the table.
|
Reported Version: SystemLink: 19.6 Resolved Version: N/A Added: Feb 27, 2020 |
|
| 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