[ISS Support Case] How to Address TLS Registry Requirements In Existing Systems
Last updated: March 7th, 2025Description
In the 2020 R2 Sp1 readme is listed Important Information for Highly Secured Environments (TLS 1.2 Exclusively) I read that the update of these registry keys MUST be done before Application Server, or like software, is installed. 1. Is this true? Do we need to update these before we install Application Server? a. If so, what is the procedure if Application Server is already installed and functional in a live system on that node? In our current case, AVEVA Historian 2020 R2 is already installed on the machine we are trying to connect to Insight. 2. AVEVA Historian is installed on a different node than our GR Node, where Application Server is installed. The Historian node is where we are trying to connect Insight to the Historian. Do the registry edits need to be made before AVEVA Historian is installed on that node as well? a. If so, same question, what is the procedure here where the software is already installed, and system is already live?
- Author: Kevin Modlin
- Published: March 7th, 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: | 03/13/2023 |
| Case: | 83955 |
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