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:

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

Or

• Delete the deployment database and reconfigure the deployment system.

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:

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

Or

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

The designated port (443 by default) needs to be shared so that the Deployment Server Service can use it to host its service. If the port is occupied by another process (or sharing is not allowed), then the service will not be able to start.

To resolve this:

• Use another available port on the system.
• Check that the port is free. The service log may include information that will identify a conflicting application.
• Enable sharing of the port on the system.

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

• 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.
• 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.
• If you selected the option "Create unique security certificates for me" when configuring the deployment server, import the authentication file again using the TRUST page on the Configurator. You can use the Windows™ Certificates MMC snap-in to search for the "Citect Deployment CA" certificate. Confirm that the certificate is correctly located under Trusted Root Certification Authorities. You can also delete any certificates named "Citect Deployment CA" before you try to import the authentication file again.
• If you selected the "I have my own installed certificates" option on the deployment server, confirm that the required certificate public key is available on the deployment server. Your system administrator (or the person who manages your organization's certificates) may need to assist you with this.
• 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 Citect 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.

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.

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

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

Citect Studio connects with the deployment server via https to perform deployment operations. Communication via an https channel requires an SSL/TLS trust relationship to exist between the computer running Citect Studio for the Windows user currently logged in and the deployment server.

The above error may be shown when the deployment server certificate is not present in the expected location (Trusted Root Certification Authorities) on the computer running Citect Studio. It can happen when current Windows user is different to the user who added the deployment server to Citect Studio.

To resolve this:

• Launch Citect Studio, and go to the Deployment activity Settings view.
• Remove the deployment server (see Remove a Deployment Server).
• Add the server again (see Add a Deployment Server). This will install the certificates for the current user.

You should now be able to log in to the deployment server.

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.

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

If you use the Configurator to change a deployment client's Project Run Path from “Run the project selected in Citect 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 Citect 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 Citect SCADA processes for the change to take effect.

• If any Citect SCADA processes or Runtime Manager are not running, restart the Citect Deployment Client Service or start Runtime Manager on the deployment client machine.
• If any Citect SCADA processes are running, restart all the processes via Runtime Manager.
• If there are no Citect SCADA processes listed in Runtime Manager, restart Runtime Manager (or the Runtime Manager Service).

One or more Citect SCADA processes in Runtime Manager are not running. Start these processes, or restart Runtime Manager on the deployment client to complete deployment.

One or more Citect SCADA processes in Runtime Manager are not operating as expected. Restart Runtime Manager on the deployment client.

One or more Citect SCADA processes in Runtime Manager are not operating as expected. Restart Runtime Manager on the deployment client.

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]\Schneider Electric\Citect SCADA 2018\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 Citect Deployment Client Service.

This message can indicate:

• Citect Runtime Manager (or the Citect Runtime Manager Service) is not running.

Or

• Deployment is disabled on the deployment client.

To resolve this, firstly confirm that Citect Runtime Manager (or the Citect Runtime Manager Service) is running.

To enable deployment on the deployment client:

1. Launch the Configurator.
2. Select Citect SCADA 2018 | Computer Setup in the left panel.
3. Select Run the project deployed from the Deployment Server under Project Run Path.
4. Click Configure.

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

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.

To resolve this, 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:

1. Launch the Configurator.
2. Select Citect SCADA2018 | Computer Setup in the left panel.
3. Enter a valid path in the field under Run the project deployed from the Deployment Server.
4. 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]\Schneider Electric\Citect SCADA2018\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.