.filepart extension staying on files after transfer

Advertisement

Glenn Simpson
Guest

.filepart extension staying on files after transfer

We are using WinSCP to transfer files to an FTP server via a script. On the other end, an automated process grabs the file and processes it. In some cases, the automated process finds that the file still has the .filepart extension. I know that on one of these times, all of the file had transferred over, but the .filepart was still on there.

There doesn't seem to be any pattern to which files this happens to - they vary in size, so it's not just the big ones. The guy on the other ends swears his process is not grabbing the file until it is finished, so it's not an issue of the file not being complete.

We are including option confirm off in the script, so resuming should take place as needed. There has not been any situations where both a partial and a complete file were at the destination.

Every indication is that the program is simply not dropping the .filepart extension when it is finished. Is that possible? I have just updated from 4.3.2 to 4.3.3 to see if that helps, but is there anything else we can look at? Let me know what additional info you need from me.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
27,253
Location:
Prague, Czechia

Re: .filepart extension staying on files after transfer

I haven't heared of the problem.

Btw, how does the remote process tell that the file is complete?

Reply with quote

SivaP
Guest

Re: .filepart extension staying on files after transfer

Hi Glenn,

Did you happen to resolve the issue. I am also facing the same issue. Please can you let me know if there is a work around for this?

thanks
Siva

Glenn Simpson wrote:

We are using WinSCP to transfer files to an FTP server via a script. On the other end, an automated process grabs the file and processes it. In some cases, the automated process finds that the file still has the .filepart extension. I know that on one of these times, all of the file had transferred over, but the .filepart was still on there.

There doesn't seem to be any pattern to which files this happens to - they vary in size, so it's not just the big ones. The guy on the other ends swears his process is not grabbing the file until it is finished, so it's not an issue of the file not being complete.

We are including option confirm off in the script, so resuming should take place as needed. There has not been any situations where both a partial and a complete file were at the destination.

Every indication is that the program is simply not dropping the .filepart extension when it is finished. Is that possible? I have just updated from 4.3.2 to 4.3.3 to see if that helps, but is there anything else we can look at? Let me know what additional info you need from me.

Reply with quote

Advertisement

You can post new topics in this forum