Known issues
- Last UpdatedDec 11, 2025
- 2 minute read
The following table lists the known issues for this release of MES Cloud integration.
|
ID |
Description |
|---|---|
|
IMS 3039808 |
Even though the installation allows the user to select a custom installation folder, MES Cloud integration installs to the same folder where MES is installed. |
|
na |
The visualization widgets rely on the entity standard item to determine the asset's unit of measure (UOM). The UOM is then used for UOM conversions. This setting is available in the MES Web Portal and is added to MES Client in MES 2023 R2. |
|
na |
Deletes are reported to CONNECT data services first followed by updates to data and new data. If the frequency for data curation for a type is different from the frequency of data requests from the AVEVA Events to CONNECT agent it is possible that a record that is inserted (curated), then deleted (curated), and then requested will remain in CONNECT data services. |
|
na |
When configuring MES components using the Configurator, a runtime error may occur if multiple components depend on different versions of the System.Text.Json assembly. Specifically, if a component using a newer version is loaded first, it locks that version into the process. Subsequent components that rely on an older version will fail with a missing method implementation error (e.g., DisposeAsync not found). This is due to .NET’s restriction of loading only one version of an assembly per process. Note that this issue is more likely to occur when AVEVA Events to CONNECT is installed before PCS. If this error occurs, restart the Configurator and configure the components that depend on older versions of the assembly first. |
|
na |
Important: The AVEVA Events to CONNECT agent is currently only supported on systems configured with the English (United States) culture setting (en-US). Systems using non-English culture settings (e.g., fr-FR, de-DE, ja-JP) may experience issues such as:
|
|
na |
When configuring the AVEVA Events to CONNECT agent to publish history-only data from MES to CONNECT, the data is temporarily stored in the buffer folder configured for the agent. If there is a large amount of historical data to backfill, the size of the buffer will need to be increased to ensure all the data is transferred. The Events to CONNECT agent does not log an error when overwriting buffer files resulting in some data not being published. |