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

116010

ClearChangeTablesDays can now be set in the agent configuration file appsettings.json under PIAssetFrameworkServerNames. This new setting corresponds to the ClearChangeTables setting that can be configured in C:\Program Files\PIPC\AF\AFService.exe.config. By default, both ClearChangeTablesDays (in appsettings.json) and ClearChangeTables (in AFService.exe.config) are 7 days. If the user updates ClearChangeTables, users can now manually adjust ClearChangeTablesDays to be the same. Keeping them in synch does not change agent behavior other than messaging. For example, if the user changes ClearChangeTables to 1, then the user can also change ClearChangeTablesDays to 1 so that the agent will log a warning message in the event that the agent cannot retrieve change notifications for AF Elements for more than 1 day, indicating that some AF Element changes may be missing from the transfer.

116301

When performing data recovery (called Streaming Backfilling), the agent would transfer the same data multiple times, provided that the recovery period spanned multiple archives. For example, if the streaming backfill period had spanned 3 archives, the agent would send data for the first archive 3 times, the second archive 2 times, and so on. If the agent fell too many archives behind, it would never recover. This problem was more likely to occur when the agent encountered periodic disconnections from Data Archive combined with frequent archive shifts (1 per day) and high data rates (100K/sec). This problem has been fixed.

117894

Connectivity issues to Data Archive during the historical transfer step could result in data loss during the transfer. Customers who were affected by this problem noticed that the transfer progress appeared to be stuck on a particular archive. Eventually, the current activity of the agent transitioned to "Streaming only", indicating that the historical transfer step was complete, but the progress continued to indicate that the agent was still "processing archive x of y". When examining the actual data that was transferred to CONNECT, the customer might notice that most streams have all data transferred, as only a handful of streams would be affected over narrow time windows. This is because the same connectivity issues that caused the data loss also caused the built-in retry mechanisms of the agent to kick in shortly after the connectivity problems occurred. This problem has been fixed.

115912

The transfer could stop with an "Uncategorized Error" if error -11106 (Failed to lock archive-cache point) occurred while trying to get the archive file list Data Archive. This problem is fixed.

118022

Elements with templates would fail to be transferred when the description on an attribute was different than the description on its corresponding attribute template. This problem was due to a restriction in the assets service in CONNECT data services that required that the descriptions on assets and asset types must be the same, apart from the description on the resource itself. For example, the asset would be successfully created if merely the asset description was different than the description on the asset type, but if an asset metadata item had a description that differed from the corresponding description on its asset type, the asset would fail to be created. This same limitation applied to stream references and their corresponding type references. This problem is now fixed in CONNECT data services.

PI to CONNECT Agent Installation

2.4.2520