That means your SFTP server does not support checksums. And you also do not have a shell access, so WinSCP cannot use a fallback mechanism of calculating checksums using shell commands.
- martin
Post a reply
Topic review
- geek569
Got
Synchronization error: Server refused to start a shell/command
- martin
- geek569
I'm using NuGet but the v6.4 not published yet.
I tried to overwrite WinSCP.exe and WinSCPnet.dll but I got:
I tried to overwrite WinSCP.exe and WinSCPnet.dll but I got:
Method not found: 'Void System.Threading.EventWaitHandle..ctor(Boolean, System.Threading.EventResetMode, System.String, Boolean ByRef, System.Security.AccessControl.EventWaitHandleSecurity)'.
- martin
Re: "Invalid access to memory" with SynchronizationCriteria.Checksum
I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.
- martin
Re: "Invalid access to memory" with SynchronizationCriteria.Checksum
Thanks for your report.
I have added this issue to the tracker:
Issue 2291 – Failure when trying to automate file synchronization by checksum on an SFTP server that does not support it natively
I'll contact you shortly.
I have added this issue to the tracker:
Issue 2291 – Failure when trying to automate file synchronization by checksum on an SFTP server that does not support it natively
I'll contact you shortly.
- geek569
the log file
- martin
Re: "Invalid access to memory" with SynchronizationCriteria.Checksum
Please attach a full session log file showing the problem (using the latest version of WinSCP).
To generate the session log file, set
Session.SessionLogPath. 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.- geek569
"Invalid access to memory" with SynchronizationCriteria.Checksum
session.SynchronizeDirectories(SynchronizationMode.Remote, @"D:\test\", "/test", true, mirror: true, criteria: SynchronizationCriteria.Checksum);
this above code throws:
Error: WinSCP.SessionRemoteException: Invalid access to memory. at WinSCP.OperationResultBase.Check()
the exception is gone by removing
criteria: SynchronizationCriteria.Checksum