Deployment Troubleshooting

The suggested solutions described here are organized into the following sections:

1. The Configurator

2. Deployment Activity

3. Status Column Messages

4. System Management Server

The Configurator

When you try to configure a deployment server or deployment client with the Configurator, the Configuration Messages panel may display a message with a red background.

This indicates that the task you were attempting has not been successful. For a suggested solution, select the relevant message from those listed below.

Note: If you double-click on a message in the Configuration Messages panel, a dialog box will appear that provides more details about the message you have selected.

An existing database has been detected and it is password protected.

The Configurator stores the deployment database password to the ArchestraA™ Data Store (ADS) service. This message appears when the Configurator is unable to access the deployment database using the stored password provided by the ADS service (or a stored password does not exist).

This could be the result of manually restoring another deployment database, or the removal of the password data from the ADS service. To repair the deployment server:

5. Enter the last known password that can access the password-protected database.

   Or

6. Delete the deployment database and reconfigure the deployment system.

Configuration of the Deployment Server was unsuccessful.

The Configurator stores the deployment database password in the ArchestraA™ Data Store (ADS) service. This message appears when the Configurator cannot establish communication with the ADS service.

To repair the deployment server:

7. Ensure the ADS service is running via Windows™ Services console.

   Or

8. Check the ArchestrA System Management Console for any error messages.

Failed to access the System Management Server due to invalid user name or password.

Confirm that the user specified on the Authorize page is a member of either the "aaAdministrators" or "Administrators" Windows group on the System Management Server.

Deployment Client registration was unsuccessful.

There are a few solutions to consider when this message appears:

9. Deployment server administrator credentials — If the action suggested in the detailed configuration message tells you to check the "Deployment Server Administrator credentials", it indicates that the User Name and Password entered on the AUTHORIZE page of the Configurator were not valid. Confirm that valid user credentials have been entered. For more information, see Provide Deployment Access to Additional Users.

10. SSL/TLS exception — If the detailed configuration message indicates that an SSL/TLS exception occurred, it means the deployment certificate is not available in the expected location on the local workstation (Trusted Root Certification Authorities). The certificate is required to establish https communication between the computer running the Configurator and the deployment server.

11. Server refuses connection — If the detailed configuration message indicates that the target server "actively refused" a connection or "failed to respond", try the following solutions:

    • The Plant SCADA Deployment Server Service may not be running, or is not running on the designated network port. Check the deployment server service is running and is bound to the correct network port.

    • A firewall on the deployment server service may be blocking inbound connections. Check the firewall settings and allow the network inbound connection for the deployment server service.

    • A firewall on the workstation running the Configurator may be restricting an outbound connection. Allow the outbound connection.

    • A proxy setting may present on the workstation running the Configurator. Check the proxy setting on the workstation and confirm that the deployment server can be contacted.

    • The DNS (Domain Name System) did not recognize the deployment server by machine name, or the IP does not match the machine name with the DNS record. This may be due to an IP address change, as the deployment server was not in contact with DNS server for a period of time. The deployment server/client address uses a full computer name address convention; Host name + DNS suffix (for example, " https://computer_name.example.com"). If the deployment server is not recognized by its computer name, try to restart the deployment server and wait a period of time (this may take up to 15 minute or depending on your network infrastructure). If you are still unable to resolve the machine name, contact your network administrator.

Note: If you want your system to use secured features such as encryption or deployment, you should not install Plant SCADA on the computer that acts as the domain controller within your Windows® domain.

The "DeploymentClient" could not be started

You will see this error if the authentication details to access the Deployment Server have changed since the previous login.

Delete the Deployment Client configuration file located in "%PROGRAMDATA%\AVEVA Plant SCADA <VersionNumber>\Config". Re-configure the Deployment client. For more information, see Configure a Deployment Client.

The system cannot find the file specified.

Any Windows™ 10 computer that has upgraded to Version 1511 (and Build 10586.420) will have this issue.

This is caused by missing registry entries ("RegisteredOwner" and "RegisteredOrganization") in:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion

Add the registry keys, restart the Configurator, and try to configure the deployment server again.

Deployment Activity

Review the descriptions below.

Unable to deploy projects following upgrade to Plant SCADA 2023

The deployment architecture installed with Plant SCADA 2023 is not compatible with deployment servers running an earlier version. If you are trying to deploy a 2023 project to a computer that has not been upgraded to 2023, the following limitations will apply.

• You cannot use Plant SCADA Studio to add projects to a deployment server that is running a different version of Plant SCADA.

• You cannot deploy a project from a deployment server to a deployment client if they are running different versions of Plant SCADA.

If you have a distributed system that includes some computers on an earlier version of Plant SCADA, you should reinstate your existing deployment server to distribute projects to these computer until the roll out of 2023 is complete. You will also need to configure a new deployment server to deploy 2023 projects to your upgraded computers.

If you upgraded from version 2020 R2, you can uninstall 2023 and reinstate a 2020 R2 deployment server. You can use your existing configuration files to connect with any deployment clients that are still running 2020 R2.

If you upgraded from version 2018 R2, you can uninstall 2023 and reinstate the 2018 R2 deployment server. You will need to generate new certificates to reconfigure the deployment client connections.

Unable to log into deployment server: "Service Unavailable"

When you attempt to log in to a deployment server, a popup with the following message appears:

"A problem occurred while performing 'LOG IN'. Service Unavailable (503)"

This means the deployment server cannot be reached by Plant SCADA Studio. This can be caused by:

• A firewall is present on the deployment server service blocking inbound connections. Check the firewall settings and allow inbound connections.

• A firewall on the computer running Plant SCADA Studio may be restricting an outbound connection. Check the firewall settings and allow outbound connections.

• The deployment server service may not be running, or is not running on the designated network port. Check that the deployment server service is running and is bound to the correct network port.

• A proxy setting may present on the computer running Plant SCADA Studio. Check the proxy setting on the computer and confirm that the deployment server can be pinged.

• The DNS (Domain Name System) did not recognize the deployment server by machine name, or the IP does not match the machine name with the DNS record on the workstation running Plant SCADA Studio. This may be due to an IP change as the deployment server was not in contact with DNS server for a period of time.

  The deployment server address uses a full computer name address convention; Host name + DNS suffix (for example, " https://computer_name.example.com"). If the deployment server is not recognized by the computer name, try to restart the deployment server and wait a period of time (this may take up to 15 minute or depending on your network infrastructure). If you are still unable to resolve the machine name, contact your network administrator.

  Note: If you want your system to use secured features such as encryption or deployment, you should not install Plant SCADA on the computer that acts as the domain controller within your Windows® domain.

Unable to log into deployment server: "The underlying connection was closed."

When you attempt to log in to a deployment server, a popup with the following message appears:

"An error occurred while sending the request. The underlying connection was closed. Could not establish trust relationship for the SSL/TLS secure channel."

Plant SCADA Studio connects with the deployment server via an encrypted connection to perform deployment operations. The System Management Server is used to establish a trust relationship between the computer running Plant SCADA Studio and the deployment server.

The above error may be shown when the connection between the computer hosting Plant SCADA Studio and a remote deployment server is not encrypted.

To resolve this, you need to connect the development workstation running Plant SCADA to the System Management Server used by the deployment server (see Connect a Computer to a System Management Server).

You will also need to confirm that your Windows user has appropriate access to the deployment server (see Provide Deployment Access to Additional Users).

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

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.

  The deployment client address uses a full computer name address convention; Host name + DNS suffix (for example, " https://computer_name.example.com"). If the deployment client is not recognized by the computer name, try to restart the deployment client and wait a period of time (this may take up to 15 minute or depending on your network infrastructure). If you are still unable to resolve the machine name, contact your network administrator.

  Note: If you want your system to use secured features such as encryption or deployment, you should not install Plant SCADA on the computer that acts as the domain controller within your Windows® domain.

• 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.

Deployment is enabled on a client, but the status of the computer shows "Disabled"

If you use the Configurator to change a deployment client's Project Run Path from "Run the project selected in Plant SCADA Studio" to "Run the project deployed from the Deployment Server", it should enable deployment on the computer. However, the status of the computer may still show "Disabled" in Plant SCADA Studio.

Selecting the "Run the project deployed from the Deployment Server" option sets the [Deployment]Enabled INI parameter to 1. However, you need to restart the running Plant SCADA processes for the change to take effect.

• If any Plant SCADA processes, AVEVA Plant SCADA Runtime Manager or AVEVA Plant SCADA Connectivity Server are not running, restart the Plant SCADA Deployment Client Service or start AVEVA Plant SCADA Runtime Manager and AVEVA Plant SCADA Connectivity Server on the deployment client machine.

• If any Plant SCADA processes are running, restart all the processes via AVEVA Plant SCADA Runtime Manager and AVEVA Plant SCADA Connectivity Server.

• If there are no Plant SCADA processes listed in AVEVA Plant SCADA Runtime Manager, restart AVEVA Plant SCADA Runtime Manager (or the AVEVA Plant SCADA Runtime Manager Service) and AVEVA Plant SCADA Connectivity Server.

Status Column Messages

The Status column on the Computers view may display a notification icon. It will typically appear when you attempt to deploy a project version.

This indicates that runtime is not operating as expected on the deployment client. To view a message describing the circumstances, click the arrow to the right of the icon.

For a suggested solution, select from the messages listed below.

One or more Plant SCADA processes are stopped.

One or more Plant SCADA processes in AVEVA Plant SCADA Runtime Manager and/or AVEVA Plant SCADA Connectivity Server are not running. Start these processes, or restart AVEVA Plant SCADA Runtime Manager and AVEVA Plant SCADA Connectivity Server on the deployment client to complete deployment.

An unexpected error occurred in one or more Plant SCADA processes.

One or more Plant SCADA processes in AVEVA Plant SCADA Runtime Manager and/or AVEVA Plant SCADA Connectivity Server are not operating as expected. Restart AVEVA Plant SCADA Runtime Manager and AVEVA Plant SCADA Connectivity Server on the deployment client.

One or more Plant SCADA processes are not responding.

One or more Plant SCADA processes in AVEVA Plant SCADA Runtime Manager and/or AVEVA Plant SCADA Connectivity Server are not operating as expected. Restart AVEVA Plant SCADA Runtime Manager and AVEVA Plant SCADA Connectivity Server on the deployment client.

There was problem transferring a project version onto a remote node. The transfer did not finish successfully.

This message can indicate:

• The connection between the deployment server and deployment client is not working.

  Or

• There is not enough disk space on the deployment client to download the project version.

To resolve this:

• Check that the connection between deployment server and deployment client is functional and stable.

• Confirm that there is enough disk space available for the project version.

  The default location of the cache folder that stores downloaded versions is:

  %PROGRAMDATA%\AVEVA Plant SCADA <VersionNumber>\Deployment\Client\Cache

  This is defined as a value of "DeploymentNode.BaseStoragePath" under the "appSettings" section of SE.ASb.Deployment.Node.Windows.Service.exe.config.

  If you manually change this value, you need to restart the Plant SCADA Deployment Client Service.

There was a problem activating a project on a remote node. The project could not be activated.

This message can indicate:

• AVEVA Plant SCADA Runtime Manager (or the AVEVA Plant SCADA Runtime Manager Service) is not running.

  Or

• AVEVA Plant SCADA Connectivity Server is not running.

  Or

• Deployment is disabled on the deployment client.

To resolve this, first confirm that AVEVA Plant SCADA Runtime Manager (or the AVEVA Plant SCADA Runtime Manager Service) and AVEVA Plant SCADA Connectivity Server are running.

To enable deployment on the deployment client:

12. Launch the Configurator.

13. Select Plant SCADA | Computer Setup in the left panel.

14. Select Run the project deployed from the Deployment Server under Project Run Path.

15. Click Configure.

When resolved, you can try to deploy the version again.

An internal error occurred while deploying a project version onto a remote node. The deployment did not finish successfully.

This message can indicate:

• There is not enough disk space on the deployment client to unpack the version.

• The Deployment Client Service is running as a Network Service user, and the following has occurred:

  • The Network Service user does not have full control permission to the Cache folder.

  • The Network Service user does not have full control permission to the Deployment folder.

• The system time on the deployment server and the deployment client are different.

Firstly, confirm that there is enough space on the disk for the version. The deployment folder path is defined as value of [CtEdit]Deploy in Citect.ini. To change deployment folder path:

16. Launch the Configurator.

17. Select Plant SCADA | Deployment Client in the left panel. The START page appears.

18. Check that the radio button Update the configuration of the current Deployment client is selected. Click Next. The SETTINGS page appears.

19. Enter a valid path in the field under Deployed project location.

20. Click Configure.

When resolved, you can try to deploy the version again.

To resolve the Network Service user issue:

• Confirm that the Network Service user has full control permission to the cache folder.

  The default location of the cache folder that stores downloaded versions is:

  %PROGRAMDATA%\AVEVA Plant SCADA <VersionNumber>\Deployment\Client\Cache

  This is defined as a value of "DeploymentNode.BaseStoragePath" under the "appSettings" section of SE.ASb.Deployment.Node.Windows.Service.exe.config.

• Confirm that the Network Service user has full control permission to the deployment folder.

  The deployment folder path is defined as value of [CtEdit]Deploy in Citect.ini.

When resolved, you can try to deploy the version again.

To resolve the time synchronization issue, use the Time Synchronization Configuration tool (see Time Synchronization).

When resolved, you can try to deploy the version again.

System Management Server

Changing the System Management Server port after a Deployment Server and Client have been configured

The Deployment Client, Deployment Server and the System Management Server use port sharing. This allows all these services to use the same default https port number (443).

After configuring these services, we recommend that you do not to change the port. If you need to do this, perform the following steps:

21. On the Advanced Settings page of Configurator’s System Management Server plugin, change the port number on the Ports tab.

22. Click on Configure button to configure the SMS with the new port.

23. Restart Configurator.

24. Stop the Deployment Server and Deployment Client services.

25. Delete the following files from the default location “%PROGRAMDATA%\AVEVA Plant SCADA <VersionNumber>\Config", or from the location specified during installation.

    • SE.Asb.Deployment.Node.WindowsService.exe.config

    • SE.Asb.Deployment.Server.WindowsService.exe.config

26. Launch the Configurator.

27. Reconfigure the Deployment Server and Deployment Client using the “Configure…” option. The Deployment Server and Deployment Client services will start up without any error messages.

28. If you have also changed the HTTP port, then restart the connectivity service.

29. Launch Plant SCADA Studio.

30. In the Settings view of the Deployment activity, add a Deployment Server with the new port number and make it active.

31. Log in to the Deployment Server and delete the computer that belongs to the old port. The status of that computer will be "Offline".

All deployment activities will now work with the new System Management Server port.