SystemLink 2021 R3 Bug Fixes

Overview

The following items are notable issues fixed between the release of SystemLink 2021 R2 and SystemLink 2021 R3, 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

1531598

Systems Browser - Build Query slide out becomes unresponsive after removing blank query item

When using the Build Query slide out to create a filter from the Systems Browser, it is possible to get into a partially unresponsive state. One way to get into this state is via the following actions:
  1. From the Systems Management -> Systems page, click the filter icon to open the Build Query slide out
  2. Press the blue "+" button to add a new query item
  3. Delete the new item via the "x" button on its right
  4. Click into a field in a query item and note that it no longer auto-populates and the rest of the item becomes unresponsive
To confirm this is the behavior you're seeing, open your browser's development tools and navigate to the console tab. Repeat the steps that caused the failure and you should see the following output:
Error TypeError: Cannot read property 'dataValue' of undefined
at HTMLElement._openEditorByFieldType (main.767261e...js:106)
at HTMLElement._openEditor (main.767261e...js:106)
at HTMLElement._clickHandlerFilterButton (main.767261e...js:106)
at HTMLElement._clickHandler (main.767261e...js:106)
at HTMLElement._documentDownHandler (main.767261e...js:106)
at HTMLDocument.d (main.767261e...js:106)
at f.dispatch (main.767261e...js:106)
at l.invodeTask (polyfills.af259fe...js:1)
at Object.onInvodeTask (main.767261e...js:106)
at l.invokeTask (polyfills.af259fe...js:1)

Workaround:

option 1: Press the blue "+" button again to add a new item. All items in the query should become responsive again. Delete any unused query items once you've configured the query fully.
option 2: Press the "Cancel" button on the slide out and recreate the desired filter, avoiding the steps that caused the failure.

Reported Version:

SystemLink 2021 R2

Resolved Version:

SystemLink 2021 R3

Added:

Jul 19, 2021

1706828

DataFinder stopped because SL TDM Database Service crashed

Workaround:

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 work

Workaround:

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

1939802

Steps may incorrectly be marked as failed or timed out when using Store and Forward

Stored 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:
  • If the Main sequence step occurs before the create result step, the step and all of its children fail to be created
  • If the Update step occurs before the create step, the update step will fail and the step will remain in the running stage and will eventually timeout

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 quarantine

Batch 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 TestMonitorClient

XML, 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 complete

If 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' time

Steps 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 crash

If 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 requests

If 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 Client

The 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

Additional Patch Information

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.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).