[ISS Support Case] InTouch application is not updating
Last updated: March 7th, 2025Description
Customer has a development node that he is making changes to an in touch application, exporting that application transferring it to a NAS drive copying the application to the same path as an existing in touch application, thats running on a remote note, renaming the old application and naming the new application, the same name as the old application and launching the InTouch application. The application is not reflecting the changes made on the development note. This sounds like there may be an issue with the process hes using to back up the application on the NAS and that in touch isnt fully getting the new back up with the changes made on the development note I spoke with the customer and asked is the remote note not set up to receive the updates from the development note automatically he said no that that is not something theyre interested in doing. I recommended trying to place the old application in a new folder removing the path thats in the InTouch, application manager, and browsing for the new application with the development updates to see if those changes are reflected, when launching the application. The changes did not display. I requested a screen recording of the process hes taking and Ill be checking to see if this is way is supported by Aveva
- 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: | 12/06/2023 |
Case: | 85889 |
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