[ISS Support Case] Constant communication interruption The main message that I see as a issue :Platform 2 exceeds the number maximum of heartbeats
Last updated: October 17th, 2025Description
see also case 960151366 for cisco problems (every 20 minutes) 1. Who is the end customer? City of Titusville Osprey waste water treatment plant. 2. What is in the Aveva SMC Logs for the OMI and Historian Server (can you forward those logs with a filter for today only)? The SMC is kind of slow and is taking too long to export the logs. Once it completes I will forward it to you. The main message that I see as a issue :Platform 2 exceeds the number maximum of heartbeats 3. Does the Historian have its own communication server or is just historizing from application server? It has its own communication server 4. What is the communication driver you are using? DDESuiteLink There are several notes from Aveva that talk about exceed number maximum heartbeats. TN517 Platform X Exceed Maximum Heartbeats Timeouts https://softwaresupportsp.aveva.com/#/okmimarticle/docid/tn000022856 TN1273 Troubleshooting Platform X Exceeds Maximum Heartbeats Timeouts https://softwaresupportsp.aveva.com/#/okmimarticle/docid/tn000023558 Double check your network setup: binding order for the network has the Archestra network is first particular the subnet masks on all the PCs having a problem (GR, remote deployed OMI node, and Historian etc) and only one IP address listed for ArchestrA network instead of multiple Note: IPv6 should not be a problem if enable for 2020 so you should not have to disable it Is this a redundant App Server setup? If so: Configure the binding order for the two networks so that the Archestra network is first. The binding order can be accessed by the menu Advanced/Advanced Settings in the Network Connections of the computer. Make sure the Interface Metric is correct https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/automatic-metric-for-ipv4-routes#:~:text=A%20metric%20is%20a%20value,hop%20count%2C%20or%20time%20delay.
- Author: Kevin Modlin
- Published: October 17th, 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: | 04/04/2022 |
| Case: | 81280 |
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