Some content on this site is available only to logged-in subscribers. Contact Us for information on becoming a subscriber.

InSource.Solutions | InSource Training | InSource Client Portal
InSource Solutions Logo
Log In Sign Up
InSource.Solutions InSource Training InSource Client Portal Log In Sign Up
  • Home
  • AVEVA Application Server
  • AVEVA Application Server Support Cases

[ISS Support Case] DIObjects on seperate engines question(s) High Availability TN000033362

Last updated: October 17th, 2025

Description

In TN000033362 High Availability (HA) Architecture TN, the architecture in part says create an app engine on each platform which is NOT redundant. Put one DI object under one engine and then put the other DI object under the second engine. Now, create an appengine with redundancy enabled which would host just the RDIObject. Does this help with communications? I'm hoping since the DI object will be connected to the PLC already (since there is one on each platform now) IO will subscribe quicker. Let me know what the thinking is on this.

  • 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: 05/05/2022
Case: 81620
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

[ISS Support Case] OMI Slow to update Values over OPCUA

Communications pack 2023.1 P02

Read More
Support Icon

CONTACT SUPPORT

How to reach us

10800 Midlothian Turnpike Tpke, Suite 209, Richmond, VA 23235

1.877.INSOURCE

Technical Support - 1.888.691.3858

Contact Us

  • InSource Solutions
  • InSource Training
  • InSource Client Portal
  • Log In
InSource Solutions Logo

© 2025 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand