Workbench Flow:
1. Download files from Source FTP Server to an attribute in FTPCaller.
2. Upload these files from attribute to Destination FTP Server .
Files in destination getting corrupted. Attached is the workbench & FME log showing more data is uploaded that downloaded for that file. File type tested are .mdb & .zip
Please advise if someone came across such issue.Thanks.
Best answer by stalknecht
instead of using a download to an attribute try downloading as a file. Is that file also corrupt?
Maybe you use the wrong encoding(utf-8).
+19instead of using a download to an attribute try downloading as a file. Is that file also corrupt?
Maybe you use the wrong encoding(utf-8).
instead of using a download to an attribute try downloading as a file. Is that file also corrupt?
Maybe you use the wrong encoding(utf-8).
In case of Download to an attribute I could not find much info on Encoding in FME Help. Inside Source FTP Folder there can be several types of file such as .zip,.txt,.mdb how to know which Encoding needs to be applied to which file.
Thanks
+19instead of using a download to an attribute try downloading as a file. Is that file also corrupt?
Maybe you use the wrong encoding(utf-8).
So to summarize no issue in Download to a file & Upload from a file in FTPCaller.
Although we were planning to use Download To & Upload from Attribute so we dont have to save file on Staging server which would eliminate the disc space & Housekeeping Concerns. Thanks.
+14I bumped in the same issue.
Initially I generated the file content in PythonCaller. It is all right:
However the shortest way doesn't work. If I set the file contents to an attribute in PythonCaller and attempt to upload it from the attribute in the FTPCaller, the file size doubles on the FTP Server.
Alternatively the issue can be easily reproduced by 2 FTPCallers: one uploads a file directly, the other uploads the contents of the same file read by an AttributeFileReader. The the size of the file uploaded from the attribute is double as the file uploaded directly.
Now I write out the temporary file but I would prefer the attribute upload - without the extra file write/read.
I bumped in the same issue.
Initially I generated the file content in PythonCaller. It is all right:
However the shortest way doesn't work. If I set the file contents to an attribute in PythonCaller and attempt to upload it from the attribute in the FTPCaller, the file size doubles on the FTP Server.
Alternatively the issue can be easily reproduced by 2 FTPCallers: one uploads a file directly, the other uploads the contents of the same file read by an AttributeFileReader. The the size of the file uploaded from the attribute is double as the file uploaded directly.
Now I write out the temporary file but I would prefer the attribute upload - without the extra file write/read.
Yes.I also had to download to a File than upload from there.
It'll probably be that your source files are binary rather than text. I've got the same issue as I want to use an http caller to get remote files (eg pdf or xls) then ftp them up onto our servers (we're porting from a remote server).
Is it possible to ftp and create a binary file from attribute?
Thanks
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
