Known Issues
- Last UpdatedJan 12, 2023
- 5 minute read
This section describes important known issues in MES 2023, and in System Platform that affect MES.
System Platform 2020 R2 SP1 and MES 2020 Patch 2 Upgrade Issues
If there are issues when upgrading from System Platform 2020 R2 SP1 and MES 2020 Patch 2 , first ensure that you follow the correct sequence to upgrade your system:
-
Upgrade System Platform to 2023; do not connect to the System Platform IDE.
-
Upgrade MES to 2023.
-
Start the System Platform IDE to migrate the galaxy.
-
Follow MES steps in the MES Installation Guide or help to import updated MES .NET Controls, application objects, and scripts.
-
Following completion of the upgrade, perform a reboot.
If there is still have 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:
-
In a command prompt, go to C:\Program Files (x86)\ArchestrA\Framework\Bin.
-
Run aaDCOMTransport.exe /REGSERVER.
Work Tasks 2023 Connector for System Platform
If the Work Tasks Connector for System Platform is installed in a Galaxy with any objects created from the Application Object Toolkit (AOT), then these objects will not show the Workflows tab in the System Platform IDE and will log an error in the OCMC Logger. All three of the MES application objects are created with the AOT and will not show the Workflows tab in the IDE.
The workaround is to use a standard user-defined object for configuring the Workflows tab.
The error message is:
UIThreadExceptionHandler: Object reference not set to an instance of an object
Additional errors might be logged related to ArchestrA.Workflow.IDEExtension.Extensibility.xxx.
This issue will be addressed in either an updated release of the Work Tasks Connector for System Platform or the next release of MES.
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.
|
IMS 1809089 |
Related to HF 152505: sp_BOM_Item_Oper_Link_Chk improvements when there are many BOM versions and items linked to a process. |
|
IMS 2147744 |
MES Web API for Utilization Grid does not populate some fields such as raw_reas_cd, failure, spares, and categories. |
|
IMS 2150752 |
Connection errors continue to be logged every few seconds when the MES Middleware is down and MES objects are undeployed. These will end when MES Middleware is restarted or the engine is undeployed. |
|
IMS 2156935 |
Reducing item consumption to zero should not remove the record until the ERP quantity is also reduced to zero. |
|
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 2175840 |
Continuation of IMS 2147744: Changing raw_reas_cd does not get recorded in the database. |
|
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. |
|
L00137118 |
During migration of the MES database from MES version 4.5 SP1 to 5.0 SP1, there is an error associated to conflict with check constraint CK_Sample_Size. MES 2014 (version 5.0) and above prohibit this invalid configuration. The user must correct the bad data in the database and then run the migration again. |
|
L00143414 |
Launching of the Operator following a fresh install fails with an error dialog that states Unable to load DLL 'PEGRP32C.DLL'. This is an intermittent issue that can be resolved by rebooting the machine after installation. |
Known Issues for System Platform and Common Components That Affect MES
The following table lists the known open change requests for System Platform that affect MES, listed by their change request number.
|
IMS 2178106 |
System Platform IDE 2023 becomes sluggish and unresponsive when creating many instances of the MES Operations Capability Object (OCO) with PEM enabled and when running Entity Model Builder. Will be fixed in SP 2023 R2. |
|
L00117794 |
Tooltip text on the MES Button Bar .NET control buttons is not shown when running the control in InTouch. This is an InTouch issue; fixed in OMI 2020. |
|
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. |
|
L00140001 |
On an OS using a comma separator instead of a period separator for numbers, when the System Platform IDE is first opened, the MES objects will display the period separator instead of the comma separator. If you open another editor, the MES objects will display correctly. This is a System Platform IDE issue. |
|
L00144202 |
After failover, selecting an OCO object with PEM enabled in the Object Viewer logs many error messages from the BaseRuntimeComponentServer component when reading a PEM extended attribute's data type property. This can be corrected by restarting the hosting engine of the object. |
|
L00153087 |
SampleViewer .NET control does not honor RequireEntityLogOn property when used in an InTouch Frame window. Request InTouch Hotfix L00153571 for InTouch 2017 Update 2 to be released for your version of InTouch. |
|
L00154309 |
Modifying a deployed OCO or SRO that adds or removes an object-generated attribute causes errors to be logged every scan (object reference not set) even though the object still functions correctly. Request AOT HF L00154664 for System Platform 2023. |
|
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. |