Runtime starts as Client only

[Alex_M1]

Hi All,

I have what is probably a super simple problem but I cannot seem to work out. I am running Aveva Plant SCADA 2023 setup on two Windows 10 computers. The computers are setup to automatically power up, login to Windows and start the runtime 1 minute after Windows is started. To do this Plant SCADA Runtime is located in the Start-up folder of windows.

For some reason each time the Runtime is automatically started the computers only attempt to start the client service. I then get stuck with #comms and hardware alarms reports not being able to reach each server (Trend, I/O, Report, Alarm) however it never tries to start them. If I manually close the runtime and then use the same shortcut to open it again all of the servers start with the client (Trend, I/O, Report, Alarm).

Does anyone know what I am missing? Is there something i require in the ini?

Issue never occurred while bench testing my computers/application, it was only once I connected the licence keys to these computers on deployment.

Thanks all!

Alex

[olivier_vallee]

Hi @Alex_M1,

I'm not sure what the root cause is, but can you take a look at the syslog.dat on the first login to see what is happening in the log?

Also, you could try enable Plant SCADA to run as a Service. This will mean that Plant SCADA runtime (Trend, Report, Alarm, IO) will all startup when the computer reboots and doesn't require any login.

But for the services to launch, the local IP on the machine (or Machine name) needs to match the one defined in the project. Otherwise, it will run as the Client only process. So I suspect there is some short period where the IP isn't available.

Also, double check that the computer role is as you expect when you first launch (see the "parameters" log for confirmation).

Let us know how you go, it sounds like an interesting problem to solve.

Kind regards

Olivier