The process cannot access the file because it is being used by another process.

WinSCP v 6.3.5, Windows 11, v 23H2, Upload to GoDaddy using FTP - SFTP does not work. This is an install package just built by InstallShield v 24 r1. All recent attempts at uploading failed with the subject error message except one which, on another computer (same details) had a failed message but the file was intact after closing the message. The file is the latest version of ccScan, Release #66, 3.8.66.5554, Oct 17, 2024 from this link:
https://www.CaptureComponents.com/updates/Setup_ccScan.exe
I can copy the file freely among 4 computers on same intranet. But always fails when uploading to to Godaddy.
Do you have any ideas about how to prevent this?

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

Hi,
Followed your instructions and attached log. The uploaded file link was in the previous post yesterday if you want to test it.

New Info: Yesterday late afternoon I tried uploading the same file on the second computer, same properties and details. The subject error still appeared, but twice the file was auccessfully uploaded.

please keep URLs private
Thanks for your help.

Can you upload any other file to that server? Or any other file of approximately the same size? Did you try setting a longer timeout?

Good idea. I just tried that with a similar file from last December, when it uploaded with WinSCP without error. Now the same error exists with the older file. I downloaded FileZilla to try at GoDaddys suggestion, and it reported the the same error with the new and old file. Godaddy FTP support confirmed that permissions for folders were OK and no process could be affecting the uploaded files.

Now I am wondering if my anti-virus/firewall BitDefender is causing this. I turned the firewall off but still have the problem.

Hi,
I uninstalled OneDrive, Dropbox and Bitdefender. Rebooted. Tried an upload of the file from last December. Internet was very slow at this time 5-6 PM PST (cable) but after 1:45h,the file was 99% complete with no issues. Then the upload stopped, ststus said connecting, and file was complete without error. now to find thr culprit.
Thanks for your help. Looks like WinSCP was not the problem, although I will retest in the morning.

@cefegCC: Imo, it's rather their antivirus (on the server) that might be causing this.

You might be right, Martin. I spoke to the GoDaddy hosting support but they said nothing on their end should be affecting uploads, but I question their knowledge. I will call the site security people tomorrow. I know they do site AV/malware scans.

Turns out the successful upload was not because AntiVirus was removed. Today I uploaded from another computer, same error, but rather than aborting right away I let it continue. Then I aborted and the file was fully uploaded. Repeated this twice.

Now I am wondering if the new code signing process could be affecting the upload. This process uses a secure USB Token from Thales Safenet to hold the certificate information. Installshield uses a custom process to sign Setup ccScan and the msi package. It uses the Microsoft signtool.exe and asks for the USB Token password several times during the build. The secure token was mandated by the This is the only New thing in the whole build and upload process.

Here is the file if you want to try uploading it to a site with WinSCP.
https://www.CaptureComponents.com/updates/Setup_ccScan.exe

As expected, I have no problems uploading your file, with FTP nor with SFTP.
A new signature/certificate can indeed be a reason an antivirus might find your file suspicious (worth deeper/longer testing).
I've also noticed that you are using a proxy. The proxy might be also doing some tests.