Re: SynchronizeDirectories fails with "Item with the same name already exists"
No, it won't be ignored.
TransferOptions.FileMask
, when using SynchronizeDirectories
, will ">=<date>"
be ignored?
Session.SynchronizeDirectories
, and also to set Retry to automatic (not sure if that is the default). If these things can be done, please point me to the doc pages and I will continue my testing.
Timeout
setting for SessionOptions
(sorry, I thought that was for the initial log in process exclusively). I've set that to 60 seconds and have gotten two clean uploads - each using the same files/paths as my previous tests. I will continue to expand my testing from here.
Session.SynchronizeDirectories
via C# to Box. My app is failing at different points (meaning never on the same file or directory) due to the following:
WinSCP.SessionRemoteException: Error transferring file 'C:\Users\myuser\Documents\filetosave_files\Folder_1\Any_Subfolder\AnyFile-Filename.FilesExtension'.
Copying files to remote side failed.
Box: Item with the same name already exists (code=item_name_in_use, request_id=3pxua5gn1nlck6eu).
Any_Subfolder\AnyFile-Filename.FilesExtension
in the above mean the error has occurred on just about any file in any subfolder
string localPath = @"C:\Users\myuser\Documents\filetosave_files\Folder_1";
string remotePath = "/MyTargetFiles/MyTestSync/Folder_1";
session.Open(sessionOptions);
TransferOptions transOpts = new TransferOptions();
transOpts.FileMask = "| @Rec*; .DS_Store";
SynchronizationResult syncResult = session.SynchronizeDirectories(SynchronizationMode.Remote, localPath, remotePath, removeFiles: false, options: transOpts);