Remote folder 'is not file!' bug

umg
Guest

Remote folder 'is not file!' bug

Something seems to be going wrong with fetching a file to a remote folder where the file already exists. When I delete the file from the remote path the command works fine but when the file already exists it says "is not a file!" instead of overwriting it. I have option confirm set off. The user account has full permission to the remote location (I am running this as domain admin on server) Please see this snippet.

Regards,
Sem

martin
Joined:
Posts:
38,408
Location:
Prague, Czechia

Re: Remote folder 'is not file!' bug

To generate the session log file, use /log=C:\path\to\winscp.log command-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.

umg
Guest
Thanks I found a workaround. Please delete my post.

martin
Would you please rather share your workaround? Or do you really want me to delete the post?

umg
Guest
What I did was just download the files one folder above (where the files don't exist) and then move them to the subfolders at the end of the cmd batch script.

Nevin
Joined:
Posts:
2

Same issue happened with us also we use .NET client with WinSCP ver 5.15.1 – 'is not file!' bug

Attached the detailed log, this issue started happening all of a sudden in multiple environments.
What is the root cause of this issue?
• _Wnscp_SFTP_2022102616304354.txt (33.1 KB, Private file)
Description: detailed log

Nevin

"is not a file":

Is there any workaround to come out of this, this started happening all of a sudden from our PROD environment.

martin