This document contains the SystemLink known issues that were discovered before and since the release of SystemLink 2020 R4. 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 |
|
| 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 |
|
| 1173892 |
Calibration support cannot be removed from 3rd party assetsIf you enable external calibration support for a 3rd party asset you cannot remove it later.
Workaround: Manually edit the JSON file storing the asset information C:\ProgramData\National Instruments\Skyline\Data\Assets\UserDefined\_server and remove the externalCalibration section.
|
Reported Version: SystemLink: 2020 R4 Resolved Version: N/A Added: Dec 10, 2020 |
|
| 1179296 |
There is no progress information when adding, updating, or removing an assetThere is no progress information displayed from the asset grid when adding, updating, or removing an asset in a system.
Workaround: Use the History tab in the system's detail view to monitor the asset job history. |
Reported Version: N/A Resolved Version: N/A Added: Dec 10, 2020 |
|
| 1181479 |
Asset details view doesn't automatically refreshThe asset details page only updates the when a change is made and does not poll in the background. Some of the information may be out of date if another process changed the asset.
Workaround: Refresh the browser to manually refresh the asset details or navigate to the asset grid and then back into the asset details again.
|
Reported Version: SystemLink: 2020 R4 Resolved Version: N/A Added: Dec 10, 2020 |
|
| 1077767 |
Deploying RT system images can periodically failUpdating RT system images can periodically fail with the following error in the job history details, because of a race condition. opkg_lock: Could not lock /run/opkg.lock: Resource temporarily unavailable.
Workaround: Retry the deployment.
|
Reported Version: SystemLink: 20.1 Resolved Version: N/A Added: Dec 10, 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 |
|
| 1137631 |
Background monitoring can cause tests to periodically failSystemLink periodically reads the calibration and temperature information for all NI assets every 5 minutes. If SystemLink is reading the temperature at the exact same time an automated test is run it can cause the test to fail if the driver reserves the device while in use.
Workaround: Lock your systems before running tests from SystemLink. This will prevent the background tasks from running.
|
Reported Version: SystemLink: 2020 R3 Resolved Version: N/A Added: Dec 10, 2020 |
|
| 1182308 |
Dashboard list is unresponsive with large number of documentsThe Dashboards web application may become slow or unresponsive when there are a large number of dashboards (1000+) created in a single workspace. Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink: 2020 R4 Resolved Version: N/A Added: Dec 14, 2020 |
|
| 1172750 |
Parametric data viewer hangs when many test results are selectedSelecting a large number of test results in the test result grid (1000+) and then clicking View > Parametric Data, the Parametric Data Viewer hangs and there is an exception in the console.
Workaround: Select fewer test results until the resulting URL length is less than the browser limit. There is no way to send 1000 results into the Parametric Data Viewer.
|
Reported Version: SystemLink: 2020 R1 Resolved Version: N/A Added: Dec 14, 2020 |
|
| 1038431 |
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 10, 2020 |
|
| 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 2020 R4 Resolved Version: SystemLink 2020 R4.4 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 2020 R4 Resolved Version: SystemLink 2020 R4.4 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 2020 R4 Resolved Version: SystemLink 2020 R4.4 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 2020 R4 Resolved Version: SystemLink 2020 R4.4 Added: Jun 10, 2022 |
|
| 1978945 |
Store & Forward cache file and id mappings file flushes are unsafeCurrently the file is cleared before we write to it, so an exception or other system failure that prevents writing will wipe the cache.
Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink 2020 R4 Resolved Version: SystemLink 2020 R4.4 Added: Jul 18, 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 2020 R4 Resolved Version: SystemLink 2020 R4.4 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 2020 R4 Resolved Version: SystemLink 2020 R4.4 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 2020 R4 Resolved Version: SystemLink 2020 R4.4 Added: Jun 10, 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 |
|
| 2581101 |
SystemLink report plugin for TestStand generates an Error at Report Data step when processing unwanted results.When a parent sequence call is disabled, sub-sequence calls throw run-time errors when processing results. Workaround: Fixed in 2020 R4.5 Patch |
Reported Version: SystemLink Client 2020 R4 Resolved Version: SystemLink Client 2020 R4.5 Added: Jan 16, 2024 |
|
| 2580885 |
SystemLink report plugin for TestStand - Error on 'Disable Result Recording for All Sequences' in Station OptionsWhen "Disable Result Recording for All Sequences" is enabled, an error occasionally would occur while finalizing the result with error code -2147467261. This would occurs because we try to get the status from a null step. Workaround: This issue is fixed in the SL Client 2020 R4.5 Patch |
Reported Version: SystemLink Client 2020 R4 Resolved Version: SystemLink Client 2020 R4.5 Added: Jan 16, 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