[ISS Support Case] Migration from 2014 R2 to 2023 R2 Sp1 Undetermined
Last updated: March 7th, 2025Description
Objective migrate an application from 2014 R2 - 2023 R2 Sp1 Performed transitional upgrade - 2020 Trying to migrate to 2023 R2 SP1 Gets to a certain point sees aaGR started (no more activity 73% in) found a TN - suggested applying a registry update. Applied with no impact. previously had an issue with batch objects (none of those objects were available) Fixed the problem got batch objects working. Migration process question: Does it need communication with batch server during the migration process or is the migration just about converting code and objects? I ask be cause I tested on 3 separate systems and had similar but varying results). At Client site ; experienced migration issues (lots of RED) the batch server is on separate machine. Tried internally with the difference being the batch server was installed locally) the migration 'worked' there (less RED). It was the best progress thus far. Plant: All Servers are running Microsoft Server 2022 and will be using: System Platform 2023 R2 SP1 Batch 2023 R2 Historian 2023 R2 Servers: Galaxy Server Batch Server Historian Server RDP Server The original Plant used System Platform 2014 R2 and InBatch 2014 R2.
- Author: Kevin Modlin
- Published: March 7th, 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: | 02/24/2025 |
| Case: | 88721 |
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