• Replies 5 replies
  • Subscribers 586 subscribers
  • Views 297 views
  • Users 0 members are here
Options
Related

Further deployment troubleshooting

Jason Sanders

Hi Everyone,

I'm having issues with deployment on Plant SCADA 8.4.

When attempting to deploy to a client, i get the error: There was a problem activating a project on a remote node. The project could not be activated.

I have followed the troubleshooting steps from Aveva and confirmed that Citect Runtime Manager is operating, and deployment is enabled on the Client.

When viewing the deployed files, it seems that not all of the files that are required to be copied between the Server and Client are being copied, a lot of them are being missed, however i am not getting an error stating the transfer was unsuccessful.

Are there further troubleshooting steps i can follow?

Thanks in Advance

    1. Check the version of both deployment server and client (from v8.40 onwards, both deployment server and client must be in the same version)
    2. Check Windows Updates on both nodes
    3. On the remote node,
      1. Ensure ADS (Aveva Data Store) service is running
      2. Delete the deployed project that wasn't completed or missing runtime files
      3. Rename SE.Asb.Deployment.Node.WindowsService.exe.config in C:\ProgramData\AVEVA Plant SCADA 2023\Config
      4. Launch Configurator
      5. Reconfigure the deployment client service
      6. Confirm if the service is started successfully
    4. On the server node
      1. Redeploy the compiled project to the remote node

    If the problem persists, please reach out the technical support for further troubleshooting.

  • Further information: I checked the logs on the deployment client and i found an error: Failed to notify the deployed project path to Connectivity server.

  • Oh, in that case, you need to start up Connectivity Service on the remote node. Then try to deploy the project again.

  • in reply to Jacky Lang

    Hi Jacky, the Connectivity Service is hung up on "Starting" when checking it on windows services, I'm unable to stop it or refresh it so it really is stuck. I have attempted rebooting the troubled machine that the client is on, and tried restarting the client multiple time, with no success.

    I have been contacted by Aveva Support, so will continue to keep this thread updated in case anyone else has the same issue that i have.

  • in reply to Jason Sanders

    Hi Jason,

    You should take a look at log file of tracelog.ConnectivityServer.dat in .\Logs folder or Operational Control Log on the target machine.

    Connectivity Service requires its IO connections in the encrypted mode. Check if your IO servers are running in the Mixed mode (accepting the encryption requests) or Encrypted mode. In general, server machines should be configured to run in the service mode for encryption. Launch Configurator on the server machines to confirm. 

    If Connectivity service is not required on this remote node, you could simply remove it and then restart Deployment Client service. The deployment service will not consider Connectivity Service as part of deployment.

    Regards,

    Jacky

© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.