[ISS Support Case] Galaxy Migration Best Practices
Last updated: October 17th, 2025Description
ref case 98001: Client is actively migrating from 2020 from 2023 R2 Sp1 and is seeking ballpark migration time estimate and migration best practice details. Im currently migrating the restored Galaxy to the latest version of SP. BTW, how long should that take? Its not a huge Galaxy, but the server is currently at 20 minutes. I created a new galaxy from a working system. I then migrated it to the newer version. I am now in the process of deleting all instances of objects from the copied galaxy as those instances dont exist in this other clients system. Or, should I just run with it and see what happens? I also another issue with one my other installs. The GR log file is filled with errors due to unencrypted messages or something of that order. It has been working for a few months s but I would like to get to the bottom of it.
- Author: Kevin Modlin
- Published: October 17th, 2025
Details:
| Product: Application Server |
| Version: 2023 R2 |
| Solution: [Solution is visible below when you're logged in and have a current subscription] |
| Date Created: | 05/22/2025 |
| Case: | 98009 |
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