[ISS Support Case] Logger Messages Couldn't get platform name maybe the platform info is not available hr = 80040405
Last updated: October 17th, 2025Description
We started getting the logger flooded with an info message. I've uploaded a filtered log file. In SMC Couldn't get platform name - maybe the platform info is not available at this time. IPlatformInformationClerk2::GetPlatformIdentity2(PlatformID = 5), hr = 80040405 History: After backing and restoring the customers application at our office, I noticed the logger getting flooded with NotificationDistributorRuntime info messages. The messages are on both app servers and 1 view server. The other view server platform and its engines are undeployed. I would like to know what that message is referring to. I see where the messages say, Couldnt get platform name and Unable to parse alarm client message. It looks like we are getting all alarms. Im uncertain if the customer is getting the message on their system. I will be on site next week and can check. If there is any other information you need, please let me know.
- Author: Kevin Modlin
- Published: October 17th, 2025
Details:
| Product: Application Server |
| Version: 11.5 |
| Solution: [Solution is visible below when you're logged in and have a current subscription] |
| Date Created: | 06/21/2022 |
| Case: | 81925 |
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