The deployment client service is running, but the status of the computer shows "Offline"

[mony990999]

The deployment cannot get any response to the deployment server, but it worked one week ago.

I know that this means the deployment server cannot be reached by the deployment server. This can be caused by:

• A firewall is present on the deployment client service blocking inbound connections. Check the firewall settings and allow inbound connections.
• A firewall on the deployment server may be restricting an outbound connection. Check the firewall settings and allow outbound connections.
• A proxy setting may be present on the deployment server. Check the proxy setting on the computer and confirm that the deployment client can be contacted.
• The DNS (Domain Name System) did not recognize the deployment client by machine name, or the IP does not match the machine name with the DNS record on the deployment server. This may be due to an IP change as the deployment client was not in contact with DNS server for a period of time.

• A trusted connection cannot be established between deployment server and client. To repair the connection, you need the original authentication file that was generated when the deployment server was configured. Use the Configurator to reconfigure deployment client using the original authentication file.

But the firewalls and proxy settings have not changed and we're not on a domain, so it must be the last one - authentication surely.

So I want to ask about the detailed step of reconfiguring the deployment client using the original authentication file.

I have deleted the .config file of the Deployment client in the folder (AVEVA Plant SCADA 2023/Config) then setup again at the configurator. However, the exception message is found at the server side - Exception Message: Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details. HttpResponseException.Response:[StatusCode: 401, ReasonPhrase: 'Unauthorized', Version: 1.1.

Do anyone have any thought about this issue?

[olivier_vallee]

What version of Citect/Plant SCADA are you using? Can you confirm the clock time on Server/Client is the same?

Normally re-configuring the Deployment Client would resolve this issue. I'd recommend reaching out to AVEVA Customer Support to troubleshoot this further.

[mony990999 · Accepted solution]

Thanks, Oly, the problem is solved by synchronising the time between the server and the client.

[idersukh]

hi 

How to solved by synchronising the time between the server and the client.

[olivier_vallee]

Hi @idersukh,

This is probably an IT question, how to synchronise time across machines.

If the machines are part of a domain, time sync is usually handled that way. There are also 3rd party solutions, which can sync your machines time. Or you can do it the old fashioned way and just adjust the time manually (they will naturally drift over a long time).

I'd recommend you google for that answer and follow what suits your needs.