PI to CONNECT Agent 2​.4​.2349 release notes

71702

The PI to CONNECT Agent now supports legacy Data Archive server IDs originating from Data Archive version 3.4.370 or earlier. Previously, the agent would exit when configuring a transfer against a Data Archive with a unique ID in the old format. The old format is now converted into a GUID in the same manner that the AFSDK converts a legacy ID into a GUID.

111198

The agent would terminate unexpectedly when PI Update Manager is unresponsive during data recovery operations. For example, if the agent receives a data loss notification from PI Update Manager, the agent will restart the transfer to backfill any data that may have been lost. When stopping the transfer, if the agent received a "[-10722] PINET: Timeout on PI RPC or System Call" from the Update Manager when removing a signup, that error is not properly handled and would result in the agent terminating. This problem has been fixed.

112269

An active PI to CONNECT transfer would stop, requiring manual intervention to restart the transfer, if error -10007 "Bad or Null Pointer" was returned when getting an archive list from the Data Archive server. This error can occur at any stage of the transfer (whether the historical step is active or not) when archives are being unregistered on Data Archive. This problem is likely to occur when archive files are unregistered on a regular basis. This problem has been fixed.

113002

After the PI to CONNECT Configuration Utility connects to CONNECT data services, the user is presented with a list of namespaces in a dropdown. Prior to this fix, the entries in the list would correspond to the namespace description instead of the namespace name. For most users this would not cause confusion because the name and description are the same by default. However, if a user renames folders in CONNECT, only the namespace name gets renamed. In this release, the namespace name is displayed instead of the description.  

113303

After a silent installation of the PI to CONNECT Agent, the configuration utility would exit unexpectedly the next time it was launched. This was because the silent installation did not include an AlternateDisplayName in the appsetting.json for the Data Archive or AF server. This problem has been fixed.

113925

The transfer would stop unexpectedly when no archives are registered corresponding to the time range of the historical transfer step. The probability of this happening would increase significantly when the historical transfer step was complete and when a customer was doing archive maintenance, such as unregistering and moving archives to a separate disk. Event ID 90 would appear in the PI to CONNECT Event Viewer log, with the following message text:
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')

This problem has been fixed.

114506

When CONNECT data services was unresponsive for over 10 minutes and when streaming updates had filled an internal agent queue, the transfer would stop, and an uncategorized error would be reported in the cloud, requiring manual intervention to restart the transfer. This problem has been fixed.  

PI to CONNECT Agent Installation

2.3.2349