Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

TABLE OF CONTENTS

Known issues

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedOct 09, 2025
  • 7 minute read

This section describes important known issues in MES 2023 R2, and in System Platform that affect MES.

System Platform 2020 and MES 2020 upgrade issues

If you are upgrading to MES 2023 R2 from a system running MES 2020 with System Platform (SP) 2020, a direct upgrade from SP 2020 to SP 2023 R2 SP1 Patch 2 will prevent successful migration of your MES SP Galaxy (Known issue: 3878221).

To upgrade a system setup that implements MES 2020 and SP 2020 to MES 2023 R2 and SP 2023 R2 SP1 Patch 2, do the following:

  1. Upgrade SP 2020 to SP 2020 R2 SP1; do not launch or connect to the SP IDE.

  2. Upgrade SP 2020 R2 SP1 to SP 2023 R2 SP1 Patch 2; do not launch or connect to the System Platform IDE.

  3. Upgrade MES 2020 to MES 2023 R2.

  4. Configure MES components, as required.

  5. Restart the machine.

  6. Launch the SP IDE, and open the SP Galaxy you wish to migrate.

  7. When prompted, select Yes to proceed with Galaxy migration.

System Platform 2020 R2 SP1 and MES 2020 Patch 2 upgrade issues

If there are issues when upgrading from System Platform 2020 R2 SP1 Patch 2 and MES 2020 Patch 2 , first ensure that you follow the correct sequence to upgrade your system:

  1. Upgrade System Platform to 2023 R2 SP1 Patch 2; do not connect to the System Platform IDE.

  2. Upgrade MES to 2023 R2.

  3. Start the System Platform IDE to migrate the galaxy.

  4. Follow MES steps in the MES Installation Guide or help to import updated MES .NET Controls, application objects, and scripts.

  5. Following completion of the upgrade, perform a reboot.

    If there is still an issue with deploying the objects or View app with errors related to the ArchestrA.Visualization components, try restarting the AVEVA Service Manager service.

    Regarding IMS 2075532 (Unable to deploy the remote Windows platform once System Platform 2020 R2 SP1 is upgraded to System Platform 2023): If, during deployment, an error stating that the remote node's user ID or password doesn't match the GR node, try re-registering the transport component on the remote node as described below:

    1. In a command prompt, go to C:\Program Files (x86)\ArchestrA\Framework\Bin.

    2. Run aaDCOMTransport.exe /REGSERVER.

      MES BI Gateway Reports: Detection of utilization event deletion or modification

      The MES BI Gateway Reports model cannot detect utilization event deletion or duration modification. The BI Gateway service is dependent upon a detection method for notification of changes to records. The MES model uses the last_edit_at field in the MES database for its detection method. When a utilization event is deleted by modifying an existing event's duration or inserting a new event to cover an existing event, there is no option to notify the BI Gateway Service. Similarly, if an event's duration is changed but not its start time, the last_edit_at column is not modified since the duration is not stored in the new Util_History table, resulting in no notification to the BI Gateway Service. There is no workaround for this issue.

      Known issues for MES

      The following table lists the known open change requests for MES, listed by their change request number.

      ID

      Description

      Bug 3837303

      If either AVEVA Historian or AVEVA OPC UA SERVER is selected as the SSL Certificate, the MES Web Portal component cannot be successfully configured. To configure the MES Web Portal component, select either the ASB certificate or a custom (FQDN) certificate.

      Bug 3767661

      Uninstalling the last AVEVA product from Control Panel does not remove the suite level GUID causing a reinstall to show the modify/repair option. To address this issue, use setup.exe to uninstall AVEVA products.

      IMS 2173510

      When MES is installed in a system with System Platform, running the MES Repair operation will cause you to be prompted to specify the location of the installation media. Use the Browse button to navigate to and select the MES setup.exe file in the MES installation software.

      IMS 2517970

      No records are purged from Lot table if expiry_date is NULL.

      IMS 3882730

      Random duplicate calendar frequency samples.

      IMS 3933505

      MES Web Portal shows "Error Occurred" in the UI but no error at the back end and needs page refresh to see the update.

      IMS 4105744

      Create Work Order from Process has inconsistency in job and work order quantities when quantity has 2 decimals and item configured for 1 decimal (API called with x.43 yields wo.reqd_qty = X.4 while job.reqd_qty = X.5).

      L00131983

      Trying to start a job on more than one machine causes an error inserting into the Prod_Rate_History table on very specific scenarios.

      L00132902

      If multiple items to be produced in a process have a common sub-item to be produced in BOM #1 and BOM #2, then every time that common sub-item is marked as "Set as Produced Item" on BOM #1 for an operation, the same sub-item will be marked as produced on that operation for BOM #2.

      L00135404

      With the OS language set to Russian, the Entity OEE targets set in MES Client will generate a validation error but still save correctly.

      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.

      Known issues for System Platform and common components that affect MES

      The following table lists the known issues for System Platform that affect MES, listed by their identifier.

      ID

      Description

      Bug 3703022

      If you repair MES from the Windows Control Panel Add or Remove Programs (ARP) dialog, the Operations Control Management Console (OCMC) log viewer is also repaired. During this repair, the registry permissions are removed and not replaced. After the repair, the registry values appear without the required permissions, and MES messages no longer display in the log viewer.

      To address this issue, do one of the following when repairing MES:

      • Perform MES repairs using Setup.exe.

      • If you repair MES using the ARP dialog, also repair the OCMC log viewer.

      Bug 3878221

      If you are upgrading from MES 2020 with System Platform (SP) 2020 to MES 2023 R2, a direct upgrade from SP 2020 to SP 2023 R2 SP1 Patch 2 will prevent successful migration of MES SP Galaxies.

      To address this issue, upgrade to SP 2020 R2 SP1 from SP 2020 first, and then from SP 2020 R2 SP1 to SP 2023 R2 SP1 Patch 2. Next, upgrade MES 2020 to MES 2023 R2, configuring applicable MES components. Finally, restart the machine and launch the SP IDE. Open the galaxy, and confirm that you want to migrate the SP Galaxy when prompted.

      Bug 3923466

      When installing MES 2023 R2 on a system that has System Platform 2023 R2 SP1 Patch 2 and Platform Common Services (PCS) (version 8.1.2), the MES installer will behave as though the MES install is an upgrade and not a new installation. As a result, the MES installation Select Roles dialog will not be displayed.

      To address this issue, continue with the MES installation, using the Features and Components dialog to manually select the specific MES components to install.

      Bug 4300311

      For systems where System Platform (SP) 2023 R2 SP1 Patch 3 is installed, the silent configuration will log 'missing assembly' errors similar to the following and subsequently fail.

      Could not load file or assembly 'file:///C:\Program Files (x86)\Wonderware\MES\ConfiguratorPlugins\ PCS.Extensions.Configuration.Registry.dll' or one of its dependencies. The system cannot find the file specified.

      To address this issue, complete the following procedure before performing the silent configuration:

      1. Back up the configurator.exe.config file from the C:\Program Files (x86)\Common Files\ArchestrA location1.

      2. Copy the provided version of the configurator.exe.config file from C:\Program Files (x86)\Common Files\ArchestrA\MESConfigBackup1 to the location noted in step 1.

      3. Proceed with the silent configuration.

      4. Once configuration is successfully completed, restore the backed up configurator.exe.config file to the location noted in step 1.

        1If the Program Files(x86) is installed to a non-default drive, make sure to use the correct drive/path.

        Bug 4300331

        For systems where System Platform (SP) 2023 R2 SP1 Patch 3 is installed, the MES uninstallation will log 'missing assembly' errors similar to the following.

        Could not load file or assembly 'file:///C:\Program Files (x86)\Wonderware\MES\ConfiguratorPlugins\ PCS.Extensions.Configuration.Registry.dll' or one of its dependencies. The system cannot find the file specified.

        To address this issue, complete the following procedure before performing the uninstallation:

        1. Back up the configurator.exe.config file from the C:\Program Files (x86)\Common Files\ArchestrA location1.

        2. Copy the provided version of the configurator.exe.config file from C:\Program Files (x86)\Common Files\ArchestrA\MESConfigBackup1 to the location noted in step 1.

        3. Proceed with the uninstallation.

        4. Once uninstallation is successfully completed, restore the backed up configurator.exe.config file to the location noted in step 1.

          1If the Program Files(x86) is installed to a non-default drive, make sure to use the correct drive/path.

          IMS 3527443

          In SP 2023 R2 SP1, Entity Model Builder fails to create an entity with a long name (up to 128 characters) when the first 80 characters match another already exported object. The MES entity name limit is 80 characters. Work around is to ensure the first 80 characters are unique.

          IMS 3926774

          During failover, if PEM status is in BUSY state, then it will be stuck in BUSY state on secondary node until a redeploy.

          IMS 3983816

          UCO Editor is slow with 90K utilization reasons.

          L00138837

          AppEngine can crash due to the calls made to the FactMES API dlls even when using try/catch. Specific to Nullable data types. Will not be fixed in System Platform, so recommendation is to continue using the wrapped MES API DLLs in System Platform scripting.

          L00158082

          Importing of the MES folder for OMI can generate a warning during the import and log a message that it was unable to find referenced file system.windows.forms. Instead of importing the folder, MES 2023 includes an MESOMIControls.aapkg file that does not generate any warnings.

          In This Topic
          TitleResults for “How to create a CRG?”Also Available in