Sorry for the delay.
I was finally able to test a debug version and it working without errors.
Just in case I've tried fresh 5.7.5 version - it still fails.
Sent you the debug logs.

montonero

2015-07-20 22:48

Sorry, I will not be able to test it in a couple of weeks. :(

martin

Re: Weird issue with an uploading from a network mapped folder

2015-07-19

Thanks for the logs.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.

montonero

Re: Weird issue with an uploading from a network mapped folder

2015-07-15 21:20

prikrylAny news?

montonero

2015-07-10 20:27

Here's the logs. Also added sample command line and script.

martin

Re: Weird issue with an uploading from a network mapped folder

2015-07-10

Please attach a full log file showing the problem (using the latest version of WinSCP).
A log file from 4.3.2 for a comparison would help too.

To generate log file, use /log=path_to_log_filecommand-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

montonero

Weird issue with an uploading from a network mapped folder

2015-07-09 13:48

Hi,

I've got a weird issue with an uploading to FTP from a network mapped folder after upgrading WinSCP from version 4.3.2 to 5.7.4.

There is a network mapped folder "Q:\folder1\folder2\folder3\folder 4" with files "file1" and "file2" (names are example).

The command like this (executed through a script or manually in a console window):

put "Q:\folder1\folder2\folder3\folder 4" "./path_on_ftp/" -resume

works in a strange way: on first call it creates "folder 4" on the target FTP path then throws an error

File or folder 'Q:\folder1\folder2\folder3\folder 4\file1' does not exist.
A call to an OS function failed

On second call it uploads file1 and throws the similar error about file2. On third call it uploads file2.
The same errors shows in the log file (without any additional details).

Uploading of the same files and folders from a local drive works flawlessly.
This error didn't occur in 4.3.2.