PI to Data Hub Agent 2.2.2174 release notes
- Last UpdatedMar 18, 2026
- 3 minute read
- CONNECT
- PI to CONNECT Agent
- Agents
- PI Server
Overview
Version 2.2.2174, released November 7, 2024, is a maintenance release.
This release enhances how the PI to Data Hub Agent transfers AF elements and AF element templates to the cloud. Specifically, this release contains the following two enhancements:
-
When an AF element template is transferred to the cloud, the asset type that is created or updated in CONNECT data services now includes both type references and metadata. Prior to this release, the resultant asset type would contain only metadata.
-
Users can now edit assets and asset types that have been transferred to the cloud, while the agent continues to transfer subsequent changes to these same AF elements and AF element templates. Prior to this release, any user edits made to assets and asset types would be removed the next time the corresponding AF element or AF element template was edited in the on-premises AF database.
These enhancements enable full support of expected features in CONNECT visualization. Type references are used for asset relative displays for assets of the same asset type, and the preservation of user edits is expected to help fine-tune these displays.
For a full list of changes in this release, please reference Fixes and Enhancements below.
For more information on product features and functions, including system requirements and installation/uninstallation instructions, refer to PI to CONNECT Agents documentation.
Enhancements
|
Work Item |
Description |
|---|---|
|
111668 |
When transferring AF element templates to CONNECT data services both dynamic and static AF attributes are now included in the transfer, allowing both type references and metadata, respectively, to be included in the resultant asset type. Previously only static AF attributes were included in the transfer, which resulted in asset types that included only static metadata values. |
|
111398 |
Support was added to the PI to Data Hub Agent service to enable asset/asset type PATCH operations. This enhancement allows a user to edit asset and asset types in CONNECT data services without losing their edits when the corresponding AF elements or AF element templates are re-transferred because of on-premises changes to the AF database. This means that on-premises changes will continue to be synchronized while also preserving additional independent changes that are applied in CONNECT data services. |
|
105315 |
The streaming step can stop due to an unexpected exception. These unexpected exceptions cause the transfer to stop and will not restart automatically. In this release, additional log messages were added to track down the source of these errors. |
Fixes
|
Work Item |
Description |
|---|---|
|
110973 |
If a user enabled verbose logging for PI points or AF elements in the CONNECT data services portal, the agent would continue logging verbose messages for these points/elements even after disabling verbose logging in the portal, until the original expiration date that was set for verbose logging expires. This problem has been fixed. Disabling verbose logging in the portal now causes verbose logging to stop immediately. |
Known issue when upgrading to 2.2.2174
After upgrading the PI to Data Hub Agent to version 2.2.2174, it may fail to connect to PI Data Archive 2023 and greater when TLS is enabled on the Data Archive server and the PI to Data Hub agent computer does not trust the Data Archive certificate. If you are affected by this problem, the agent will report the error "The certificate chain was issued by an authority that is not trusted" in the PI to Data Hub Agent Windows Event Viewer log. Testing the connection with the PI to Data Hub Configuration Utility also fails with this same error.
This error will occur when the following conditions are met:
-
The PI to Data Hub Agent is on a remote computer from Data Archive
-
The PI Data Archive is version 2023 or later
-
TLS is configured for PI Data Archive 2023
-
The TLS certificate configured for the Data Archive is not trusted on the agent computer. This can occur if a self-signed certificate was used to configure TLS for Data Archive, which is not recommended in production environments. It may also occur if an AVEVA Platform Common Service SMS-generated certificate is utilized by the Data Archive but the root authority established by SMS is not present on the agent computer.
To address this issue, the certificate used by the Data Archive must be trusted on the agent computer. More information about troubleshooting the certificate can be found in the knowledge base article "The certificate chain was issued by an authority that is not trusted." | Data Archive and Asset Framework 2023.
Security information and guidance
We are committed to releasing secure products.
We proactively disclose aggregate information about the number and severity of security vulnerabilities addressed in each release.
Distribution Kits
|
Product |
Software Version |
|---|---|
|
PI to Data Hub Agent Installation |
2.2.2174 |