[ISS Support Case] MES 2017 to 2020 Migration Errors
Last updated: March 7th, 2025Description
Successfully got galaxy and MES migrated from 2014R2SP1P02 to 2017U3 on an AVEVA Integration Studio intermediate image. No warning or errors. Then tried to create a CAB file from that galaxy and bring into 2020R2 (yuck-no go, still hundreds of errors) Then tried to export all of the objects and graphics that are needed and then create a clean image import 3 sLIB files o aaFactMES.aaSLIB o aaMES.aaSLIB o FactMES.Controls.Utilization.aaSLIB Then import the graphics (including MES DT and button bar controls from the 2017 U3 objects) Then import the bulk of the objects last This process produces the least amount of errors, but still produces them. Some questions: 1. Should I get new sLIB files instead of bringing the ones over from 2017? a. If so, where do I get them? 2. Same questions as above with the MES graphics a. The MES component graphics seem to be problematic b. Should I replace the graphics in 2017 intermediate with new MES graphics? c. When I bring the exported graphic objects into the new 2020R2 galaxy, there are multiple errors and the eventual objects are blank (no graphics) 3. Then when I bring in the big object import, it has problems with the missing graphics from step 2 Going to try a clean, new galaxy this morning and then wait to do step 1 until we communicate further. Do I need to send you a copy of the errors from the first time? What to do next MES database updated successfully, building a galaxy import linking objects On the initial upgrade from 2014 R2 SP1 - 2017 UN . - Graphics - Symbols Exported - Objects Instances as an All Object Export Following the same process with 2017 - 2020
- Author: Kevin Modlin
- Published: March 7th, 2025
Details:
| Product: Application Server |
| Version: 2020 R2 |
| Solution: [Solution is visible below when you're logged in and have a current subscription] |
| Date Created: | 02/02/2023 |
| Case: | 83237 |
Give feedback about this article
Recommended articles
[ISS Support Case] Synchronize Views is not working correctly in the IDE
Read More[ISS Support Case] Historian Data Gap On Appengine Failover In SP Version 2023 R2 P1
I am seeing an issue with SP2023 R2 P1 related to appengine failovers. When I cause an appengine failover, data (primarily analog) has a gap in the trend until the data changes. Sometimes the gap stays but sometimes the gap is "filled" in for some reason. I'm having a bit of a consistency issue trying to replicate this problem. Every time I cause a failover, the results are slightly different but I do see bad results. To demonstrate this, I created two videos to show what I'm seeing. If someone can create a problem ticket and reach out to me, I can forward the videos to InSource to show what I'm seeing.
Read More[ISS Support Case] MQTT setup crashes OCMC
MQTT server - CDP 2023 check encryption/validate security - no issue port validates enable user identity/try to bring certs in shuts down OCMC nothing in OCMC logs event viewer shows an app crash for mmc with cfg_mqtt_plctype1.dll as the faulting module advised repair after conferring with aveva - called client to discuss and confirm New SR960455477 (requesting) Log file Config Files Do Not upgrade Stay @ the same version of CDP Call in on 9/12/2024 No success on the MQTT server with the antivirus turned off, and it was even worse this time. Could not hook to AWS server. Proceeded to step 2, entered certificate in case it needed to log in to AWS server, but the OCMC shut down. Restarted OCMC acted strange, restarted computer. OCMC behaved normally after, but still no success with MQTT. Wants a call back whenever you're available, doesn't have to be tonight. CDP shows 2023
Read More