Deployment Client Problem - Invalid Path

Hello

the report file, where you have the report format, should be passed to the deployed project using Custom Files

Hi Miguel,

Thanks for the reply. I think you may have misunderstood my problem though.

I'm not using reports, I haven't configured any. I'm simply trying to deploy my project from my server to a client and run it on the client. The deployment appears to have worked ok as all the project files are on the client, I just can't run the project on the client as it gives the invalid path error.

Hello

Sorry... i cannot understand your issue.

In Picture bellow, is an example of client configuration from my project. 

From looking at your configuration mine looks the same in Citect.ini and Configurator>Computer setup.

My project is called SCADA_160B

Computer setup is set to "Run the project deployed from the deployment server" and points to "C:\ProgramData\Schneider Electric\Citect SCADA 2016\Deployment\Client\Projects".

In the image you will see the errors I get at runtime and via the computer setup wizard. I've also included a screenshot of the files that have been deployed from the server, they've been deployed to "C:\ProgramData\Schneider Electric\Citect SCADA 2016\Deployment\Client\Projects\SCADA_160B\1\23rd Aug 2018 160B".

It looks as though runtime is expecting to see the project in a different folder to the default deployment location.

The project is saved on the server in "C:\ProgramData\Schneider Electric\Citect SCADA 2016\User\23rd Aug 2018 160B"

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.

Hi Erik,

I'm gettng there, I've just tried setting [Deployment]PROJECT=23rd Aug 2018 160B, I still had the same issue. On the image below it shows the project name and path on the server.

I've also included CtEdit. It's strange because it defaults to:

C:\ProgramData\Schneider Electric\Citect SCADA 2016\Deployment\Client\Projects\23rd Aug 2018 160B\1\23rd Aug 2018 160B

Which is incorrect for where the project has been deployed, if I change the run path (by using the browse function) to the correct path:

C:\ProgramData\Schneider Electric\Citect SCADA 2016\Deployment\Client\Projects\SCADA_160B\1\23rd Aug 2018 160B

Runtime gives the error, then sets the run path back to the incorrect one.

Renaming the folder from "...\Projects\SCADA_160B\..." to "...\Projects\23rd Aug 2018 160B\..." fixes the issue and the project runs.

Question now is though why is my project being deployed with that path, I've tested it on 2 clients and it deployed to both the same way.

Hi Matt,

We did a few test and can reproduce.

The easiest way to get around this is to make sure that the project name on the deployment server is equal to the project folder name in the [User] directory.

I would propose to raise a case with support to get this addressed in a future release.

Thanks Erik, I must have changed the project name at some point then. Thanks for taking the time to test this and let me know.