Upgrade AVEVA Real-Time System

Before you install the latest version of AVEVA Real-Time System (RTS), you should upgrade your work area.

Upgrade your work area for the latest version of RTS

1. If you have RTS installed as a service, stop the service and uninstall it by using the following command:

   rts uninstall-service

   See Uninstall the AVEVA Real-Time System service for more information.

2. Rename the RTS folder. For example, rename the C:\SimSci\RtsCore folder to C:\SimSci\RtsCore.old.

3. Run the RTS installer. During the install, choose to specify a custom path, and specify the original path, for example C:\SimSci\RtsCore.

4. Copy the specific sequences from your original folder (C:\SimSci\RtsCore.old) to the new location.

5. If you have modified the RtsSettings.json file in any way, such as added support for multiple AVEVA Process Simulation instances, copy those Scripthost sections to the new RtsSettings.json file located in the new <RTSInstall>\bin folder, where <RTSInstall> is the folder in which you installed RTS.

6. Although less common, if you have made any modifications to any other .json (InternalSettings.json) or .config file in the original <RTSInstall>\bin folder, make the same changes in the new <RTSInstall>\bin folder.

   Do not replace the new file with the old file. We recommend making changes manually.

7. If you are upgrading from RTS 2024 and do not need any old log files, delete the RTS log files from the \Logs folder for AVEVA Process Simulation.

   Otherwise, the Logging database (rts.db in the \Logs folder) may take a long time (about 10 minutes) to migrate to the new version when you start RTS for the first time after you upgrade. RTS Console cannot connect to the RTS server until the migration is complete. During the Logging database migration, you can check the .txt file in the \Logs\RtsWebUI_logFile folder for the "Migration started on" message followed by the "Migration completed on" message. If you do not see the "Migration completed on" message, the migration is not yet complete.

8. Any pending schedule runs or backfills will be lost, so you must restart them after the new system comes back up. However, since the completed.csv files located in the respective sequence folders were copied over in an earlier step, starting the backfill on those sequences will pick up where it had left off.