If I upload a file to an ftp server from a UNC path it creates the full path and file to the server.

\\SERVER\share\folder\file.txt will create the following when uploading:
/ftproot/SERVER/share/folder/file.txt

But if uploading from a local drive:
C:\folder1\folder2\file.txt ,it ends up as expected:
/ftproot/file.txt.

Anyone else seen this? Running version 8.2.7

I have the exact same issue.

Work around by copying to a local disk first, but if anyone has a fix that could eliminate that additional step, that would be great.

We cannot directly reproduce this. Can you send screenshots of;

1. upload settings showing source and destination folder
2. the Connection Explorer browsing inside the destination folder

---

Sorry, we found the error and the cause..

One of our variables had a trailing backslash for the UNC path on the Folder setting in the File filter for upload.

\\server\share\folder -> works

\\server\share\folder\ -> creates the additional folder structure.

Sorry, we found the error and the cause..

One of our variables had a trailing backslash for the UNC path on the Folder setting in the File filter for upload.

\\server\share\folder -> works

\\server\share\folder\ -> creates the additional folder structure.

Great, thanks!

---

Hi

I know this is an old thread but I am experiencing the erroniously path creation remotely when using a semicolon separated list of two unc paths under [File filter]/[Location]/[Folder]. Ie. the UNC paths are created on the SFTP site. If I use a defined path instead the task fails because it cannot create a folder named S: on the FTP site.

It works if separated into two commands in the SFTP task.

Thank you.