SystemLink 2020 R2 Bug Fixes

Aperçu

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

972321

Querying TDM Reader for multiple files by ID may error on large requests

The 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:

SystemLink: 2020 R2

Added:

Feb 27, 2020

959907

Test results group by selection is ignored when a filter is changed

The 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:

SystemLink: 2020 R2

Added:

Feb 27, 2020

1000340

A limited number of variables may be visible in SystemLink OPC UA Connector

When creating a new session from OPC UA Connector it is only possible to see the first 100 OPC UA Variables published by certain servers.

Workaround:

Some OPC UA servers have a default number of variables to return if a number is not specified in the request.  If this value is configurable, increasing it will return more variables to SystemLink.

Reported Version:

SystemLink: 19.6

Resolved Version:

SystemLink: 2020 R2

Added:

Jul 16, 2020

1100438

Faulty system updates can cause multiple redundant refreshes

Client systems that send continuous property updates, often fan or temperature related, may cause the server to execute a refresh job for each update.  This may impact performance in extreme cases with multiple client systems.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink: 2020 R2

Resolved Version:

SystemLink: 2020 R2

Added:

Aug 11, 2020

1099076

Test Monitor LV API may pass null for parameters instead of empty array

LV API calls to the Update Step VI without setting the Parameters input, and under specific conditions, will incorrectly send a null parameter to the server rather than the correct empty array.

Workaround:

There are two potential workarounds.  

1) Set the Step Object Parameters to be non-empty, and then explicitly set the Parameters input to an empty array for each call of the Update Step VI.  
2) Always use a branch of the original Step Object reference wire instead of the Reference out wire of the Create/Update Step VIs.

Reported Version:

LabVIEW: 2018 | SystemLink: 2020 R2

Resolved Version:

SystemLink: 2020 R2

Added:

Aug 11, 2020

1094844

Asset API may record inconsistent timestamps

For certain utilization data, timestamps may be incorrectly recorded in a local timezone rather than the expected UTC. This may cause utilization calculations to give unexpected results.

Workaround:

Post process any utilization queries to check for timezone data, and convert as required.

Reported Version:

SystemLink: 2020 R2

Resolved Version:

SystemLink: 2020 R2

Added:

Aug 11, 2020

1123428

Webserver may accept requests with invalid basic auth credentials

Sending a request with Basic Auth headers which are invalid and `insecureAccess: true` causes the request to be forwarded to the affected service anyway.  This may result in malicious users accessing default workspace resources such as notebooks and reports.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink: 20.1

Resolved Version:

SystemLink: 2020 R2

Added:

Oct 20, 2020

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).