[ISS Support Case] Shutting down a node with redundant app engine resulted in communication Alarms
Last updated: March 7th, 2025Description
Everything seemed to be working fine. Had to shut down a server, once back up it was unable to communicate with other nodes. Platform manager of itself and the GR node it appeared as a redundant app engine. To the other nodes it appeared as a regular engine. Results was a ton of communication alarms. To fix it we undeployed and redeployed the engine and forced a failover. Resolved communication errors. SMS warnings in the logs. ongoing issues, seeking self help type documentation. The documentation is good at telling you how to configure in a vacuum but no good troubleshooting guidance exists aside from forums. NMX used for inter object communication issues what (domain) users need to belong to what ArchestrA groups. They use redundant app engines and MUST USE SMS it's hyper critical that this be resolved before the next shut down (next Tuesday 8hr plant shut down) limping along atm. If they encounter another issue they will be dead in the water.
- 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/27/2025 |
| Case: | 88810 |
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