sigilToNoise wrote:

I don't think so. When I manually upload the file (using the WinSCP GUI), it works fine. It's only when I try to upload with .NET that it fails.

You probably have have resume support disabled in the GUI, haven't you?

martin wrote:

sigilToNoise wrote:

It seems that this happens with any zip file that I try to send. If it makes a difference, these are zip files that were creating using the DotNetZip library.

It could be some antivirus (or similar) checking the uploaded file, locking it during the test.

I don't think so. When I manually upload the file (using the WinSCP GUI), it works fine. It's only when I try to upload with .NET that it fails.

But on the chance that it is a temporary lock, is there a way that I can check to see if the file is locked before attempting the rename?

sigilToNoise wrote:

It seems that this happens with any zip file that I try to send. If it makes a difference, these are zip files that were creating using the DotNetZip library.

It could be some antivirus (or similar) checking the uploaded file, locking it during the test.

What do you recommend as a workaround for this issue? Using C#, I'm getting the following error message from OperationResultBase.Check():

WinSCP.SessionRemoteException: Transfer was successfully finished, but temporary transfer file 'testfile.zip.filepart' could not be renamed to target file name 'testfile.zip'. If the problem persists, you may want to turn off transfer resume support.

It seems that this happens with any zip file that I try to send. If it makes a difference, these are zip files that were creating using the DotNetZip library.

Thank you!

martin wrote:

Not yet. Request is tracked here:
https://winscp.net/tracker/834

Not yet. Request is tracked here:
https://winscp.net/tracker/834

Is the "ResumeSupport" flag exposed in the WinSCP.dll .NET/COM library? How can I set up my .NET code to not break any file into .fileparts and send as one file?

Thanks