PI to CONNECT Agent 2.6.1 release notes
- Last UpdatedJul 31, 2026
- 4 minute read
- CONNECT
- PI to CONNECT Agent
- Agents
- PI Server
Version 2.6.1, released July 31, 2026, is a feature release with several fixes and enhancements.
Although PI to CONNECT Agent Version 2.6.1 is an optional upgrade, it is highly recommended for all customers. This release introduces support for multiple Data Archive transfers from a single PI to CONNECT Agent.
Another notable change is that the agent installation kit no longer includes the ASP.NET and .NET runtimes (for security purposes). These runtimes must be installed separately.
For a full list of changes in this release, please reference New features and enhancements and Resolved issues below.
For more information on product features and functions, including system requirements and installation/uninstallation instructions, refer to PI to CONNECT Agent documentation.
New features and enhancements
The following new features and enhancements were added:
|
Work Item |
Description |
|---|---|
|
120371, 120372, 120373, 120374, 120375 |
Added support for data transfer from multiple PI Data Archives simultaneously. This enables adding explicit PI Points from different Data Archives to the same transfer. PI Point references in AF elements added to the transfer are also automatically included for multiple Data Archives as soon as the Data Archive is added to the agent configuration. Note: For existing agent installations, adding a second Data Archive triggers AF indexing (to index all databases configured with the AF Server so the agent can automatically detect implicit points when a new Data Archive is added). This can delay data transfer from several minutes to several hours depending on AF size. |
|
130072 |
Added support for the Canada region. |
Resolved issues
The following issues were resolved:
|
Work Item |
Description |
|---|---|
|
127221 |
The agent could send the current snapshot value to CONNECT for PI Points with compression ON when the agent or a transfer was restarted, if that value had been written during the transfer inactivity window. This could lead to a mismatch between events in CONNECT and the PI Data Archive. This issue is fixed. |
|
127222 |
Extended point classes did not work properly for implicit points. The agent transferred them, but they were not shown in the portal. This issue is fixed. |
|
128809 |
A transfer could stop with an “Uncategorized Error” if the agent lost communication with the AF Server when Event Frame transfer was enabled. This issue is fixed. |
|
129255 |
History recovery could fail for PI Points of type string when historical events contained empty string values. In affected cases, transfer progress could appear stuck on a particular archive. This issue is fixed. |
|
130903 |
History recovery could fail for PI Points with an event timestamp within 160 ticks of the archive file end time. In affected cases, transfer progress could appear stuck on a particular archive. This issue is fixed. |
|
129918 |
A transfer could stop with an “Uncategorized Error” when a user moved an existing transfer’s start time past the transfer’s historical end time. This issue is fixed. |
|
130070 |
The agent detects when a target SDS stream has been deleted and begins recovery by recreating the stream and recovering all data from the historical start time to present. Under certain conditions, the stream was not marked as successfully recovered, causing the agent to resend data multiple times. This issue is fixed. |
|
130639 |
The agent detects type mismatches between a source PI Point and the target SDS stream (SDS stream types are immutable), stops data transfer for the stream, and reports health events so the user can resolve the mismatch. Previously: (1) restarting a transfer could clear mismatch health events and hide the issue; and (2) deleting the stream and restarting could lead to data gaps. These issues are fixed. Resolution options remain: (a) change PI Point type back to the original type (agent resumes transfer and performs history recovery from transfer start time), or (b) delete the target stream in CONNECT and restart the transfer (agent recreates the stream and recovers history from transfer start time). |
|
128967 |
A transfer could stop with an “Uncategorized Error” when the PI Data Archive server associated with the agent is rebooted. This issue is fixed. |
Third-party products and components
PI to CONNECT Agent requires the end user to install the following .NET runtimes on the host machine:
Important: We are committed to releasing secure products. In compliance with the European Union Cyber Resilience Act (CRA), AVEVA no longer redistributes third-party product components.
These runtimes can be kept up-to-date automatically through standard Windows update mechanisms.
Note: Third-party links are provided for information and convenience only and AVEVA has no control over and cannot therefore accept responsibility or liability for the content of any linked third-party website or for any loss or damage that may arise from your use of them.
Security information and guidance
We are committed to releasing secure products. This section is intended to provide relevant security-related information to guide your installation or upgrade decision.
We proactively disclose aggregate information about the number and severity of security vulnerabilities addressed in each release.
Distribution kit files
|
Product |
Software Version |
|---|---|
|
PI to CONNECT Agent Installation |
2.6.1 |