on 02-22-2016 5:24 PM
Hi,
We have recently migrated one scenario(File to Proxy one) from PI 7.11 dual stack to PI 7.4 dual stack system.
After migration, we have observed that in PI 7.4 dual stack system, that file adapter is not able to pick the source file throwing error FTPEx: 550 Unexpected reply codeThe filename, directory name... Here the source file is having chinese characters in its filename(for ex:
吸入用复方异丙托溴铵溶液-84盒_20151116-005_8899666000056621-001_盒10支_2.txt). File pattern is mentioned as *.txt in channel.
So, we have switched back to PI 7.11 system, where the interface is running successfully with out any issue.
During migration, we have done just simple file export and import transport and didn't change configuration/design parameters as both are dual stack systems.
I have attached channel ping screen shot, please check for reference.
We have raised oss message to SAP, but SAP could not provide any solution to this bug till now.
Could you please let us know if you encountered any such issue or your valuable suggestions.
P.S: Scenario is not a complicated one. Just used simple FCC at the sender end, simple mapping to convert source to proxy message.
Regards
Vishnu
Hi Vishnu
I haven't encountered this myself before but maybe the FTP channel in PI 7.4 is unable to determine the encoding of the file name.
You can try setting a suitable encoding for the Chinese characters with file.encoding. Refer question 20 in SAP Note 821267.
Regards
Eng Swee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Eng,
Thanks for your reply.
Yes, I have tried with both options, keeping the file type as binary and text(with encoding options Big-5/Big5, ISO-8859-1 etc..), but didn't work, got the same error.
I have refered the file adapter FAQ note, but didn't get much help from it.
I am just wondering how come the same scenario has working in PI 7.11 system, since at the end both are dual stack systems.
Regards
Vishnu
Hi Vishnu
I'm refering to the encoding on the filename, not the file content. If you refer to the note, it provides instructions on how to configure the system property for the filename encoding.
I can't really answer why the difference in behavior, but might be a JRE thing based on the SAP Note.
Regards
Eng Swee
Hi Eng,
The encoding of the file name they are having is Big-5, and I have tried to give the same one in our PI channel, but still got the same error.
Does the issue is with the patch files present in PI dual stack 7.4 version since the same interface is running successfully in PI 7.11 version where the file type is mentioned as Binary in the channel configuration.
Regards
Vishnu
Hi Eng,
Just to update you that, I have tested the same file with NFS protocol(i.e. uploading into a dummy directory on PI app server), and it worked perfectly fine.
In the channel configuration, I used the encoding as ISO-8859-1.
So, for the time being, we are taking this as a workaround till SAP comes back with a solution..
Regards
Vishnu
Hi Vishnu,
Are you able to pick other files(non-Chinese characters) in this folder? if not you may check if your PI has read access of the files.
Regards,
Robert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vishnu,
what the configuration in the sender FTP channel, does it read the file as binary or text?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.