Aveva Plant Scada 2020 R2 update 6 run time manager error

It is a known issue that occurs when the node name (either IP or hostname) cannot be resolved within 10 seconds on start-up. As a result, Runtime Manager will pop up this error "Cannot connect to the runtime manager service...". In the command window, try to ping the hostname or IP in the "Address" field in Network Address table of Topology from your project. I suspect that Ping command would fail. Try to use 127.0.0.1 or localhost in the project.

Hi Jacky,

Thank you for the response. I am running the "ExampleSa" project which is by default having IP address as 127.0.0.1 and network name as 'localhost'.  I tried pinging those IP and hostname from command line and found ok.

That is interesting. Have you configured System Management Server? This may happen if Runtime manager is launched immediately after SMS is configured. Something went wrong on your machine. Review the settings in Configurator and maybe reboot the machine. Run Computer Setup Wizard and try to run the project again after reboot.

hii,

I have fully uninstalled the aveva plant scada and reinstalled the original setup 'aveva plant scada 2020 R2'. I compiled the project and found system all ok. no error of runtime manager.

after that i have updated the setup with update 6 patch step-wise i.e. first floating license manager updated to 2.8 then common platform service and thereafter update-6. which resulted into runtime error as mentioned earlier. also i noticed that "security roles" under plant scada tree displays message as "the plant scada security model could not be read". earlier without patch update-6 it was showing all the list of users group configured.

after update 6:

/resized-image/__size/640x480/__key/communityserver-discussions-components-files/1457/pastedimage1669628667928v1.png

before update 6 :

before update 6 :

Not sure if you rebooted the machine after Common Platform Service upgraded. Anyway, please check if AVEVA Data Store service is running. If not, manually start it up.

Your problem could be caused by ADS that failed to automatically start up. Without ADS running, Runtime Manager will fail to obtain any security info of the configured project and thus fail to launch the project.

yes, i did restart the system after installation of common platform service. i noticed that ADS is running but i also noticed that AIM token manager service is not running. i manually tried running the service but could not start.