Automatically Resume Failed Upload

[doubleJ]

Hello...
I saw in another thread about a guy wanting to disable automatic resuming of failed file transfers.
I'm guessing that it is supposed to work, but I've never been able to automatically resume failed transfers.
I spend a good portion of my Monday mornings (every bloody week) trying to overwrite a couple MP3s that I've added ID3 tags to.

Status: Starting upload of \\audioserver01\audio1\mp3\Sermon\2013\130127Audio.mp3
Command: PASV
Response: 227 Entering Passive Mode (66,119,8,175,229,246).
Command: STOR 130127Audio.mp3
Response: 550 The process cannot access the file because it is being used by another process.
Error: Critical file transfer error
Status: Disconnected from server

It's a constant cycle of Reset/Reque - Process.
Is this actually supposed to work or am I missing something?
JJ

[botg]

Error codes starting with 5 are permanent errors that will not resolve on its own and require human intervention.

[doubleJ]

Error codes starting with 5 are permanent errors that will not resolve on its own and require human intervention.

Hmmm...
So, would automatic resumption only happen if there was a network connection issue?
I'm not sure when else a file transfer would fail.
JJ

[botg]

Network errors yes, also errors with a code starting with a 4.

[boco]

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

The error text says it all. Usually occurs on Windows FTP servers only. Some process locks that specific file's handle and thus the server software cannot access it. Prime suspects are realtime antivirus processes trying to scan the file as soon as it arrives. Or it could be open in a player, still.
A tool like Unlocker, used on the server file copy could reveal the process locking it.

[doubleJ]

It's definately open because someone is downloading it.
It is a Windows FTP server, also (IIS7).
I was hoping that there would be some means of automating the task.
It's quite a pain in my butt.
Are there any other FTP programs that would automatically resume a 550 or could an option be included in FileZilla to do so?
JJ

[boco]

FileZilla will automatically resume or retry, but only for 4xx errors, where this makes sense.

4xx=Temporary error, will probably resolve if you wait. Retrying makes sense.


However, your server returns a 5xx error. The FTP specs say FTP clients are bound to not retry any action where a 5xx error has been received.

5xx=Permanent error, will not resolve without human interaction on the server.

It's definately open because someone is downloading it.

Nope. FTP servers allow multiple downloads of the same file and do not throw errors. Your server's error message explicitly tells you the file is in use/locked by a different process (with a different PID). If you check the server file with the Unlocker or Lockhunter tool you will probably learn the name of the process locking the file. It's not unheard that files are locked (and not released) by Explorer.exe just because of their icons having been retrieved and displayed once.

[doubleJ]

However, your server returns a 5xx error. The FTP specs say FTP clients are bound to not retry any action where a 5xx error has been received.

Well, then, this particular error really shouldn't be a 5xx error.
Hehehe...
It's is, very specifically, a temporary error.

Nope. FTP servers allow multiple downloads of the same file and do not throw errors. Your server's error message explicitly tells you the file is in use/locked by a different process (with a different PID). If you check the server file with the Unlocker or Lockhunter tool you will probably learn the name of the process locking the file. It's not unheard that files are locked (and not released) by Explorer.exe just because of their icons having been retrieved and displayed once.

It's not a download issue.
I'm trying to upload/overwrite the file that someone is trying to download.
This happens every Monday morning.
Files that people are less interested in usually will upload the first try.
Files that people are very interested in will, sometimes, be locked until Tuesday.
Both files that I tried, yesterday morning, were uploaded by lunch.
A file that I tried, yesterday afternoon, still hasn't uploaded (oops, it uploaded while typing this post).
I'm not trying to sound obstinate, it's just not a perminent error.

I think, at the end of the day, we can agree that FileZilla isn't the problem (although it would be nice for an option to go against the spec IF the user wants it to).
JJ

[boco]

Wouldn't a synchronizing software fit your situation better, then? Especially one that retries until it is successful?

In your case the webserver seems to lock the file and thus the FTP server fails to access it.

[doubleJ]

Wouldn't a synchronizing software fit your situation better, then? Especially one that retries until it is successful?

Is there synchronization software that works over the internet?
I'm assuming that specific ports would also have to be opened, on the routers, to allow those accesses.
JJ

[boco]

Is there synchronization software that works over the internet?

I'm quite sure, though, personally I never used any. Thus I cannot recommend one.

I'm assuming that specific ports would also have to be opened, on the routers, to allow those accesses.

When using FTP for sync, that software wouldn't be any different than an FTP client.

[doubleJ]

I'm assuming that specific ports would also have to be opened, on the routers, to allow those accesses.

When using FTP for sync, that software wouldn't be any different than an FTP client.

I assumed that you were referring to synchronization software like SyncToy (not FTP).
If the software used FTP, wouldn't it be bound by the same rules as FileZilla?
JJ

[boco]

Correct, and these sync software apps usually use Passive mode for FTP. Passive mode requires no port forwarding at the client side.