The following items are notable issues fixed between the release of SystemLink 2020 R3 and SystemLink 2020 R4, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of SystemLink.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1115039 |
Sporadic Data Navigator session timeout requires reconnectingIn some situations an API key for a connection to specific DataFinder instance can expire early and close the connection prematurely.
Workaround: Close concerned DataFinder in Data Navigator and than re-open to reconnect.
|
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 Added: Dec 14, 2020 |
|
| 1115699 |
DataFinder cannot index file completely when special characters are used in property nameIn case that certain special characters are used in a
property name, DataFinder cannot index that specific property. The name of a property must start with a
letter from the alphabet (a-z, A-Z). When indexing, special characters are now replaced by "_" (underscore).
Workaround: You must not use any of the following characters in a property name: ., :, ,, ;, ', \, @,
<, >, #, [, ], %, (, ), {, }, |, *, ?, =, !, ", ^, $, &, +, -, /, or a space. The name of a property must start with a letter from the alphabet (a-z, A-Z). |
Reported Version: SystemLink: 20.1 Resolved Version: SystemLink: 2020 R4 Added: Dec 14, 2020 |
|
| 1136757 |
In Data Analyzer, tasks cannot be expanded when DataCart is dockedWhen the DataCart window is docked and not floating, tasks cannot be expanded. Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 Added: Dec 14, 2020 |
|
| 1142046 |
Python DataPlugin crashes if a channelgroup or channel does not existIf a file has no channel groups, a group has no channel, or if the "Plugin" class doesn't exist, the Python DataPlugin crashes. Workaround: Use an empty array in case when there are no channel groups or channels. |
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 Added: Dec 14, 2020 |
|
| 1141961, 1151080 |
Duplicate license checkout in Data Preparation and Analysis Automation module blocks Web UIBoth the Data Preparation and Analysis Automation service and the according Web UI are checking out the same license instead of sharing a single license seat. This can cause additional instances to be blocked from opening because no licenses are available.
Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 Added: Dec 14, 2020 |
|
| 1161171 |
Wrong sorting of notifications in TDM modulesNotification, for instance as shown in the DataFinder>>Dashboard, are sorted alphabetically instead of in time order.
Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink: 2020 R2 Resolved Version: SystemLink: 2020 R4 Added: Dec 14, 2020 |
|
| 1137629 |
Asset Management service performance and scalabilitySystemLink Asset Management service uses excessive memory and CPU and the web interface may become unresponsive when managing 35,000+ asset.
Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 Added: Dec 10, 2020 |
|
| 1174220 |
Advanced Asset Utilization report gives incorrect results if an asset is in useIn some situations, the advanced asset report will show 0% utilization when there are assets actively in use. Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink: 2020 R2 Resolved Version: SystemLink: 2020 R4 Added: Dec 10, 2020 |
|
| 1172767 |
List of available software gets cut off and doesn't scrollIf you have a lot of versions for a single package in a feed the highest versions get cut off when you expand the list in available software.
Workaround: Create a state that includes the package and specific version you will to deploy. You can also click Install/Upgrade to install the package with the highest version.
|
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 Added: Dec 10, 2020 |
|
| 1137630 |
Some requests fail when an asset has quotes in model or vendor nameIf an asset has quotes in the model or vendor name it can cause some operations to fail including reports. Workaround: Remove any quotes in asset model or vendor name.
|
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 Added: Dec 10, 2020 |
|
| 1122983 |
Calibration due date should be hidden from asset details if the "Supports external calibration" is unchecked for an individual assetIf you enable supports external calibration and then add a calibration entry the Calibration due date will show up, however if you then uncheck supports external calibration it doesn't hide the calibration due date from the details. Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 Added: Dec 10, 2020 |
|
| 1108036 |
Adding a feed from ni.com to a state will fail to deploy if the product is already installedIf you manually add a feed to a state and then deploy it to a system that already has the product installed it may return an error in some cases. This issue applies to both Windows and Linux RT targets. Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 Added: Dec 10, 2020 |
|
| 1122119 |
Applying a state fails if the target doesn't have access to ni.comApplying a state to an RT system can fail if the target does not have access to ni.com, even if the state includes alternative feeds to ni.com that contains all of the packages. Workaround: Set "compressed: true" for feeds in raw editor (by default compressed is set to false) |
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 Added: Dec 10, 2020 |
|
| 1126780 |
Feeds failed to get configured from state when the URL is already configured on another feedFeeds failed to get configured from state when the URL is already configured on another feed.
Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink: 19.0 Resolved Version: SystemLink: 2020 R4 Added: Dec 10, 2020 |
|
| 1127305 |
Creating a state from a system should not check install recommendsCreating a state from a system checks install recommends by default. This could result in the target system having different software than the system it was created from. Workaround: Manually disable install recommends option in the state after creating it from a system. |
Reported Version: SystemLink: 20.0 Resolved Version: SystemLink: 2020 R4 Added: Dec 10, 2020 |
|
| 1204020 |
SystemLink Client may send excessive calibration and temperature updates.SystemLink 2020 R3 clients fail to publish calibration and temperature updates to the server and continuously retries every 15 ms.
Workaround: There is currently no known workaround for this issue. |
Reported Version: SystemLink: 2020 R3 Resolved Version: SystemLink: 2020 R4 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 |
|
| 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 |
Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.
These patches currently do not have any special instructions.