Scan failed, then copy proceeds without error

[pokeefe]

I'm setting up a new task to do a mirror copy from a Synology NAS to Windows folder using SFTP. The copy immediately throws an error:

Error: Scan failed (-1): Server returned an error: (30031): Server returned an error: Permission denied (30031)

but then runs without error, copying and deleting as expected. Rerunning the copy gives the same error but correctly determines that the source and destination are identical so nothing is copied.

This error does not seem to be causing any problems but SyncBackPro flags the copy with "Failure" so I'd rather get this fixed.

• SyncBackPro V12.0.8.0 (64-bit) (Elevated)
  Window 25H2 (Build 26200.9.168)
  Synology DSM 7.4.1-90080

I run many SyncBackPro tasks without this error but this is the first involving this particular NAS.

I thought I would ask about this in the forum before opening a support ticket ... just in case this is a common problem with an easy fix.

[mmullins_98]

Maybe check this:

Temporary File Creation / Rename Restrictions:
• Some FTP/SFTP clients upload a temporary file first and then attempt to rename it. If the server configuration or security policy blocks the rename or delete operation, error 30031 triggers.

Verify the Destination Directory Path
• The scanner may be attempting to write to a folder that does not exist or has a typo in the path.
• Avoid using absolute local paths (like C:\ScannedFiles). Instead, use the network path format (e.g., \\ComputerName\ScannedFiles or \\IP_Address\ScannedFiles).

[pokeefe]

Sorry for my delay in responding.

Temporary File Creation / Rename Restrictions:
• Some FTP/SFTP clients upload a temporary file first and then attempt to rename it. If the server configuration or security policy blocks the rename or delete operation, error 30031 triggers.

I suppose the SyncBackPro FTP client (WeOnlyDo) might do this, but the NAS credentials I'm using for the copy gives read/write authority for the target share and has permission to use all functions that Synology allows accounts to use.

Verify the Destination Directory Path
• The scanner may be attempting to write to a folder that does not exist or has a typo in the path.
• Avoid using absolute local paths (like C:\ScannedFiles). Instead, use the network path format (e.g., \\ComputerName\ScannedFiles or \\IP_Address\ScannedFiles).

The path is valid. And your admonition against using local (mapped) paths to the FTP server really doesn't apply. This is FTP, not SMB. As far as I know, I have to use the full network path.

I watched this run attended and the error comes up at the end of the copy. Strange.

I've given up on this for now. FTP (rather than SFTP) works without problem and I really have no need for security on this connection.