Hi Olaf;

  My guess is that this issue might be related to the "External Files" mapping or maybe the remote Web Server mapping - and thus, an FTP issue. Just my 1st guess.

  Does it work OK using a local Web Server like IIS?

Regards ... Chris

Hi Olaf,

When you started PowerBuilder did you select "Run as Administrator" option?  PowerClient deployment process requires that you explicitly tell Windows 10 to execute PB as admin.

Also, when you click "Server Configuration" in your screenshot is the FTP connection to your remote server testing successfully?

Lastly, have you tried first deploying to your IIS on your local machine and get that working before going to remote server?  That's a great way to isolate if problem is with your machine or the problem is the remote server.

Best regards,
Armeen

Hi Armeen, 

Thank you for your quick reply. 

I did not run PB as an administrator, but it did not resolve the issue as I now tested with that option.

Testing of both FTP and file path was successful.

Changed the deployment to local IIS, but the issue persists.

To me this seems not be related to the server it's being deployed to, but to an local issue while generating files getting ready to deploy.

See screenshot where it looks for a 'en' folder, which does not exists. A 'em' folder exists at the local folder (it is empty).

Hi Olaf,

According to the log, you are deploying your application via 'Deploy PowerClient Project' on the right-click menu. In this case, please make sure you have successfully deployed your application using 'Build & Deploy PowerClient Project' before this deployment, and the deployed files are not deleted. The error message is indicating that the path doesn’t exist, so please go to the path in the deploy log to check if it exists. If not, please execute 'Build & Deploy PowerClient Project' instead.

Please refer to the article below for building and deploying a PowerClient project.
https://docs.appeon.com/pb2019r3/pbug/ch07s03.html#d0e60276

Regards,
ZhaoKai