Deployment Client Problem - Invalid Path

Hi all,

I'm running SCADA 2016 and have setup my deployment server and client. I've created a version of my project (SCADA_160B) and deployed it to my client, which appeared to be successful

When I try and run the project from the client the runtime manager reports "Deployment is enabled but no project has been deployed".

If I run the computer setup wizard on the project source page it has "Deployed" selected and shows the correct project name (SCADA_160B) and version (1), when I click next I get "C:\ProgramData\Schneider Electric\Citect SCADA 2016\Deployment\Client\Projects\SCADA_160B is invalid. Please ensure that the expression is legal and the path exists.

The path does exist and I can see all my project files in the version subfolder C:\ProgramData\Schneider Electric\Citect SCADA 2016\Deployment\Client\Projects\SCADA_160B\1\23rd Aug 2018 160B

I'm logged into the client (Win 10 v1803) on an admin user account.

I'm not sure if it's an issue with the deployment, the path or a permisions issue on the client, has anyone else had this problem?

Cheers

Matt

Parents
  • Looks like there is a mismatch between project names on the server / client or a mismatch between the Project name on the server (SCADA_160B) and the root folder name (23rd Aug 2018 160B).

    Can you also share the [CtEdit] Run parameter from the client?

    I reckon you can test:
    - Set [Deployment]PROJECT=23rd Aug 2018 160B
    to see if it runs, or rename the folder "1\23rd Aug 2018 160B" to "1\SCADA_160B"

    and investigate from there why the folders on the client are created as it is, you might want to share the project name and root folder name from the deployment server to check if anything is odd there.
Reply
  • Looks like there is a mismatch between project names on the server / client or a mismatch between the Project name on the server (SCADA_160B) and the root folder name (23rd Aug 2018 160B).

    Can you also share the [CtEdit] Run parameter from the client?

    I reckon you can test:
    - Set [Deployment]PROJECT=23rd Aug 2018 160B
    to see if it runs, or rename the folder "1\23rd Aug 2018 160B" to "1\SCADA_160B"

    and investigate from there why the folders on the client are created as it is, you might want to share the project name and root folder name from the deployment server to check if anything is odd there.
Children
No Data