Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Same Error 206 bug using version 5.14.4 RC (Build 9136)

dklimoski2 wrote:

I get the same error using 5.14.4 RC (Build 9136) build over FTP. I thought this bug was addressed in previous version. Am I missing something? Also, can I skip over files/directories with this error to backup the rest of my files?

Here is the WinSCP log:

. 2019-02-19 21:47:33.242 File: '/[...]/Background Checks' [2014-01-01T10:55:11.000Z] [0]
* 2019-02-19 21:47:33.242 (EOSError) System Error. Code: 206.

* 2019-02-19 21:47:33.242 The filename or extension is too long

Thanks for your report.

This bug has been added to the tracker:
https://winscp.net/tracker/1725

Can you send me an email, so I can send you back a development version of WinSCP for testing? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

You will find my address (if you log in) in my forum profile.
dklimoski2

Same Error 206 bug using version 5.14.4 RC (Build 9136)

Hi,

I get the same error using 5.14.4 RC (Build 9136) build over FTP. I thought this bug was addressed in previous version. Am I missing something? Also, can I skip over files/directories with this error to backup the rest of my files?

Here is the WinSCP log:

. 2019-02-19 21:47:33.242 File: '/[...]/Background Checks' [2014-01-01T10:55:11.000Z] [0]
* 2019-02-19 21:47:33.242 (EOSError) System Error. Code: 206.

* 2019-02-19 21:47:33.242 The filename or extension is too long
. 2019-02-19 21:47:33.242 Asking user:
. 2019-02-19 21:47:33.242 Error creating folder 'E:\FTP_Box_Backup\[...]\Background Checks'. ("System Error. Code: 206.

. 2019-02-19 21:47:33.242 The filename or extension is too long")
< 2019-02-19 21:47:33.242 Script: Error creating folder 'E:\FTP_Box_Backup\[...]\Background Checks'.
< 2019-02-19 21:47:33.242 Script: System Error. Code: 206.

< 2019-02-19 21:47:33.242 The filename or extension is too long
* 2019-02-19 21:47:33.242 (ESkipFile) Error creating folder 'E:\FTP_Box_Backup\[...]\Background Checks'.
* 2019-02-19 21:47:33.242 System Error. Code: 206.
* 2019-02-19 21:47:33.242 The filename or extension is too long
. 2019-02-19 21:47:33.242 Script: Failed
. 2019-02-19 21:47:33.242 Script: Exit code: 1
. 2019-02-19 21:47:33.273 Disconnected from server
martin

Sent to both of you.
eine

Bug 1337

Thank you, thank you Martin for remembering about it! May I ask for pre-realase version too?
markusl

Registred

Hi,

thank you for your reply. Yes please, I would like to get the pre-relase!

Markus
martin

MarkusL wrote:

Any plans to support longer paths than 260 with FTP?

It's implemented already. It will be included into the next major release:
https://winscp.net/tracker/1337
I can send you a pre-release build, if you register.

Does more than 260 work with SFTP?

Yes.
MarkusL

The second error is probably because of a too long path. WinSCP does not support paths longer than 260 characters with FTP protocol:
https://winscp.net/tracker/821


Any plans to support longer paths than 260 with FTP? I tried with 5.13.3 and it still fails when it tries to transfer path+filename that is more than 260 characters. Does more than 260 work with SFTP?
eine

Anonymous wrote:

Just, CC, I've registered myself.


Sorry for double post, I've just found notifications, please delete it.
Michal Sokolowski

Plans fot implement it for FTP also.

martin wrote:

ckchinetworks wrote:

Sorry I got busy before I had a chance to reply, the directory with the issue is "share\public reports\reports"

That's caused by the second error in my previous post.


Hey, thank u for that great piece of software, I've successfully implemented it for lots of users. Do u have any plans to fix FTP deep path as well?
martin

ckchinetworks wrote:

Sorry I got busy before I had a chance to reply, the directory with the issue is "share\public reports\reports"

That's caused by the second error in my previous post.
ckchinetworks

Sorry I got busy before I had a chance to reply, the directory with the issue is "share\public reports\reports"
martin

I see you have 7 synchronize commands in your scripts.

Some do not find any change to synchronize.
Some find a change and do synchronize it.
And two of them fail for different reasons:

> 2014-10-07 00:09:34.563 CWD /HomeFolder/Robert.Meixner/Desktop/
< 2014-10-07 00:09:34.578 550 Access is denied.


. 2014-10-07 00:12:06.538 Can't open file 'G:\Share\Prior Sever appraiser and map.it\Software to install\Software for new Katrina machine 2011-10-28\Sharp MX-5001 Win 7 64-bit (2011 Oct 28)\CFSC-PCFAX-1010A-2KXPVISTAXPVISTAX64\CFSC-PCFAX-1010a-2kxpVistaXPVistax64\CFSC-PCFAX-1010a-2kxpVistaXPVistax64.txt'.
. 2014-10-07 00:12:06.538 Copying files from remote side failed.


The second error is probably because of a too long path. WinSCP does not support paths longer than 260 characters with FTP protocol:
https://winscp.net/tracker/821
ckchinetworks

part 2
ckchinetworks

OK, I manually split the files and created new rar files. It's in 2 parts again.
martin

Re: Files not copying

Sorry, but I do not know what to do with those files. The backup.zip.zip file is not a valid ZIP file. And the backup_part2.tar file also does not look like a valid TAR file.
ckchinetworks

part 2
ckchinetworks

The log is very large, it will be sent in 2 parts.
martin

Re: Files not copying

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate log file, use /log=path_to_log_file 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.
ckchinetworks

Files not copying

So I have a script and it runs great for the most part, there is a new issue though. I have the script run every night and finishes in 30 mins after going through 550+ GB of data. This has been running for about 3 weeks now, but lately I found the files are not being copied over. In the logs it identifies new and modified files but they are not making to the destination directory. There are no errors for reading the source or destination folder. Any ideas on what is going on?