I've tried binary mode and this certainly does not strip out the carriage returns, but I do have the ".filepart" extension problem as well as the remaining files that do not get uploaded because their file names are alphabetically after the 4th file that gets the .filepart extension. Automatic Resume is enabled, although I don't think that my file transfers are being interrupted. The WinSCP log on the SFTP server only includes a lot of text, but the only error message I can see is "Sending special code: 12"
It seems like I've tried every configuration combination I could think of, as well as those hinted at by the help pages, but I'm still getting a ".filepart" extension to one of my files and I don't know why.
The page Transfer Modes is a little confusing. It states, "There are two options how to support text mode transfers," but the two options are not clarified. I was looking for "check this for that option, check the other for the other option," but all I see is "The second option is more universal, but it is supported only by SFTP-4 and newer and FTP1)," and "the first option is used by WinSCP for SCP and SFTP-3 and older protocols," but none of this helps me understand which config changes need to be made in order to ensure text files are copied as-is.
I removed "option batch on" from our sftp command text file and I see that I'm prompted for confirmations. With this, I was successful in getting the remaining files to get SFTP'd, but the file with ".filepart" file extension does not get fixed.
Transfer was successfully finished, but temporary transfer file 'myfilename.txt.filepart' could not be renamed to target file name 'myfilename.txt'. If the problem persists, you may try to turn off transfer resume support.
No such file or directory.
Error code: 2
Error message from server <en>: File not found
Request code: 18
(A)bort, (R)etry, (S)kip all:
Choosing "Retry" gets the same error message over and over. Choosing "Skip all" gets the remaining files uploaded, but does not remove the .filepart file extension.
Am I closer? The login that AWE uses has full permissions on the folder the files are being copied to, so I don't understand why it's unable to rename a file it just created.
Thanks for your help,
Reply with quote