Home Support Documentation Bugs

SystemLink 2022 Q1 Bug Fixes

Created Jun 22, 2023

Overview

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

DataFinder may timeout or display incomplete data due to problematic queries in the DataFinder Hierarchy (.dfh) file.

In case a User-defined DataFinder Hierarchy (*.dfh file) has been added to a DataFinder configuration, it can happen that the navigation experience shows low performance and in some cases even existing data is not presented to the user when navigating the tree.
This happens with inconsistent data when not the same spelling (case sensitivity) of data defining the hierarchy is being used.
It is needed to re-apply the User-defined DataFinder Hierarchy (*.dfh file) by the administrative user to address this issue.

Workaround:

Please contact NI support for a workaround for this issue.

Reported Version:

SystemLink 2020 R1

Resolved Version:

SystemLink 2022 Q1

Added:

N/A
1812554

TestStand fails to generate PDF report when the SystemLink client is disconnected

PDF report generation fails when using SystemLink Test Monitor with TestStand if the client HTTP connection status is disconnected or partially connected.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R3

Resolved Version:

SystemLink Client 2022 Q1 Patch 1

Added:

N/A
1828584

DIAdem cannot connect to DataFinder if user is in too many Windows Groups

When authenticating a connection from DIAdem or the LabVIEW DataFinder Toolkit to a DataFinder instance, if the JSON response containing the Windows Group IDs a user is a part of exceeds 8Kb, the connection fails with the following message.

"error":{"args":[],"code":-254851,"innerErrors":[],"message":"'windowsGroupSids' is required","name":"Auth.ValidationError"}

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2021 R3, SystemLink 2022 Q1

Resolved Version:

SystemLink 2022 Q1 Patch 1

Added:

N/A
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
1976719

TestMonitor error when creating step with 1D Array (I32) parameter

The following errors will occur when running a sequence file that has a LabVIEW step with a "1D Array (I32)" parameter (input or output).

Exception in TestStand: 
An exception occurred inside the call to .NET member 'ProcessResultData':
NationalInstruments.SystemLink.Clients.Core.ApiException: Error handling request.
   at NationalInstruments.SystemLink.Clients.TestMonitor.Swagger.Api.StepsApi.CreateStepsV2WithHttpInfo(TestStepCreateOrUpdateRequestObject requestBody)
   at NationalInstruments.SystemLink.Clients.TestMonitor.Swagger.Api.StepsApi.CreateStepsV2(TestStepCreateOrUpdateRequestObject requestBody)
   at NationalInstruments.SystemLink.Clients.TestMonitor.StepWriter.CreateSteps(IEnumerable`1 creationDefinitions, Boolean updateResultTotalTime)
   at NationalInstruments.Skyline.TestMonitorClient.Api.TestMonitorHttpApi.CreateTestSteps(List`1 requests) in C:\Dev\Skyline\TestMonitorClient\Api\TestMonitorHttpApi.cs:line 163
   at NationalInstruments.Skyline.TestMonitorClient.Api.WeaklyOrderedTestMonitorDecorator.CreateTestSteps(List`1 requests) in C:\Dev\Skyline\TestMonitorClient\Api\WeaklyOrderedTestMonitorDecorator.cs:line 100
   at NationalInstruments.Skyline.TestMonitorClient.Reporter.ProcessResultData(PropertyObject deltaResults, PropertyObject parentIds, PropertyObject moduleParameters, PropertyObject stepDataElements, Boolean& errorOccurred, Int32& errorCode, String& errorMessage) in C:\Dev\Skyline\TestMonitorClient\Reporter.cs:line 427
Exception logged on the SystemLink Server: 
2022-05-19--15:39:52.20086 | TestMonitor.Http | ERROR - Request 807: handler CreateStepsV2 threw exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> AutoMapper.AutoMapperMappingException: Error mapping types.

Mapping types:
Object -> IEnumerable`1
System.Object -> System.Collections.Generic.IEnumerable`1[[NationalInstruments.Skyline.TestMonitor.Domain.Step, NationalInstruments.TestMonitor, Version=21.5.1.0, Culture=neutral, PublicKeyToken=2eaa5af0834e221d]] ---> AutoMapper.AutoMapperMappingException: Error mapping types.

Mapping types:
CreateStepDomainRequest -> Step
NationalInstruments.Skyline.TestMonitor.Domain.CreateStepDomainRequest -> NationalInstruments.Skyline.TestMonitor.Domain.Step

Type Map configuration:
CreateStepDomainRequest -> Step
NationalInstruments.Skyline.TestMonitor.Domain.CreateStepDomainRequest -> NationalInstruments.Skyline.TestMonitor.Domain.Step

Destination Member:
Outputs
 ---> AutoMapper.AutoMapperMappingException: Error mapping types.

Mapping types:
DomainNamedValue -> NamedValueModel
NationalInstruments.Skyline.TestMonitor.Domain.DomainNamedValue -> NationalInstruments.Skyline.TestMonitor.Model.NamedValueModel

Type Map configuration:
DomainNamedValue -> NamedValueModel
NationalInstruments.Skyline.TestMonitor.Domain.DomainNamedValue -> NationalInstruments.Skyline.TestMonitor.Model.NamedValueModel

Destination Member:
NationalInstruments.Skyline.TestMonitor.Model.NamedValueModel.Void .ctor(System.String, MongoDB.Bson.BsonValue).parameter value
 ---> AutoMapper.AutoMapperMappingException: Error mapping types.

Mapping types:
Object -> BsonValue
System.Object -> MongoDB.Bson.BsonValue ---> System.ArgumentException: Cannot create an instance of abstract type MongoDB.Bson.BsonValue.
Parameter name: type
   at lambda_method(Closure , Object , BsonValue , ResolutionContext )
   --- End of inner exception stack trace ---
   at lambda_method(Closure , Object , BsonValue , ResolutionContext )
   at AutoMapper.Mapper.MapCore[TSource,TDestination](TSource source, TDestination destination, ResolutionContext context, Type sourceType, Type destinationType, IMemberMap memberMap)
   at AutoMapper.ResolutionContext.Map[TSource,TDestination](TSource source, TDestination destination, IMemberMap memberMap)
   at lambda_method(Closure , Object , IEnumerable`1 , ResolutionContext )
   --- End of inner exception stack trace ---
   at lambda_method(Closure , Object , IEnumerable`1 , ResolutionContext )
   --- End of inner exception stack trace ---
   at lambda_method(Closure , Object , IEnumerable`1 , ResolutionContext )
   --- End of inner exception stack trace ---
   at lambda_method(Closure , Object , IEnumerable`1 , ResolutionContext )
   at AutoMapper.Mapper.MapCore[TSource,TDestination](TSource source, TDestination destination, ResolutionContext context, Type sourceType, Type destinationType, IMemberMap memberMap)
   at AutoMapper.Mapper.Map[TSource,TDestination](TSource source, TDestination destination)
   at AutoMapper.Mapper.Map[TDestination](Object source)
   at NationalInstruments.Skyline.TestMonitor.Infrastructure.Persistence.Postgres.PostgresStepRepository.CreateSteps(IEnumerable`1 createRequests, IRequestResultBuilder`2 builder) in C:\agent\_work\14\s\TestMonitorService\TestMonitor\Infrastructure\Persistence\Postgres\PostgresStepRepository.cs:line 40
   at NationalInstruments.Skyline.TestMonitor.Domain.StepService.CreateSteps(IEnumerable`1 requests, Boolean updateResultTotalTime, AuthResult authResult, BatchOperationResultBuilder`2 builder) in C:\agent\_work\14\s\TestMonitorService\TestMonitor\Domain\StepService.cs:line 56
   at NationalInstruments.Skyline.TestMonitor.Domain.StepServiceResultAdapter.CreateSteps(IStepService service, IEnumerable`1 requests, Boolean updateResultTotalTime, AuthResult authResult) in C:\agent\_work\14\s\TestMonitorService\TestMonitor\Domain\StepServiceResultAdapter.cs:line 17
   at NationalInstruments.Skyline.TestMonitor.Http.V2.StepsCollection.CreateSteps(IHttpRequest request, TestStepCreateOrUpdateRequestObject requestBody) in C:\agent\_work\14\s\TestMonitorService\TestMonitor\Http\V2\StepsCollection.cs:line 228
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at NationalInstruments.Skyline.SkylineUtilities.WebServices.HttpHandler.RunRequest(Object state)

Workaround:

If the parameter does not need to be logged, the Log checkbox can be unchecked in the step settings parameter list.

Reported Version:

SystemLink Client 2022 Q1

Resolved Version:

SystemLink 2022 Q1 Patch 3

Added:

Oct 28, 2022
1951222

System Alias not shown in Results view for users with insufficient privileges

For users who do not have sufficient Systems Management privileges, the System ID cannot be resolved into the System Alias when viewing test results, and the ID is shown instead.

Include relevant system information, steps to reproduce, and any workarounds.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

SystemLink 2022 Q1

Resolved Version:

SystemLink 2022 Q1 Patch 3

Added:

Oct 28, 2022
2054336

Writing NaN to a Tag Can Cause a Tag Historian Service Crash

Applications writing to double tags with history enable can cause the Tag Historian Service to crash if the value written is not a number (NaN).

Workaround:

In your application writing tag values, include additional logic to filter NaN values prior to writing to the tag service.

Reported Version:

SystemLink 2021 R1

Resolved Version:

SystemLink 2022 Q1 Patch 3

Added:

Oct 28, 2022
2266174

SystemLink Client performance degradation over time

The 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

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