BizTalk - Most possible reason for “is Delimiters are not unique” in EDI transaction
2009-02-17 19:03
501 查看
I have one EDI to IDOC map deployed on BizTalk2006, and after I dropped an EDI file into the receive location, I got the following error.
Fatal error encountered in EDI Disassembler, error information is Delimiters are not unique, field and component seperator are the same
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
From the error description, I thought there were multiple delimiters within the input data, After I double checked my input data, I realized that’s not the reason.After comparing with other data files which can pass the schema validation, I found any field level violation in envelop can cause this type of error. E.g. ISA09 is a date format, but the value here is seven digitals, in my case the ISA06 field has extra white spaces and max length exceeds 15.
Fatal error encountered in EDI Disassembler, error information is Delimiters are not unique, field and component seperator are the same
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
From the error description, I thought there were multiple delimiters within the input data, After I double checked my input data, I realized that’s not the reason.After comparing with other data files which can pass the schema validation, I found any field level violation in envelop can cause this type of error. E.g. ISA09 is a date format, but the value here is seven digitals, in my case the ISA06 field has extra white spaces and max length exceeds 15.
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- MYSQL:Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
- 使用cocapods报错 [!] Your Podfile has had smart quotes sanitised. To avoid issues in the future, you should not use TextEdit for editing it. If you are not using TextEdit, you should turn off smart quotes
- The method replace(int, Fragment, String) in the type FragmentTransaction is not applicable for the
- [真理永垂不朽]The method XXX in the type FragmentTransaction is not applicable for the arguments XXX
- ERROR 1598 (HY000): Binary Logging not Possible. Message: Transaction Level READ-COMMITTED in InnoDB
- Traincascade Error: Bad argument (Can not get new positive sample. The most possible reason is insuf
- The method add(int, Fragment) in the type FragmentTransaction is not applicable for the arguments (i
- Could not store transport type data for Receive Location 'Recv.Loc' to config store. Primary SSO Server 'Sql-server' failed. The external credentials in the SSO database are more recent.
- 错误：The method replace(int, Fragment) in the type FragmentTransaction is not applicable for the argum
- Jira的 Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'错误的解决
- The method replace(int, Fragment) in the type FragmentTransaction is not applicable for the argument
- 错误：The method replace(int, Fragment) in the type FragmentTransaction is not applicable for the arguments (int, MyFragment)
- One reason for not able to show chinese correctly in installation
- Traincascade Error: Bad argument (Can not get new positive sample. The most possible reason is insuf
- CO-doc. number assignment not possible for bus.trans. COIN in CO area 1800 Message no. KC101
- Can't create a new thread (errno 11); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug
- Why most large-scale Web sites are not written in Java
- The method replace(int, Fragment, String) in the type FragmentTransaction is not applicable for the arguments (int, SettingFragment, String)
- Traincascade Error: Bad argument (Can not get new positive sample. Themost possible reason is insuff
- Binary Logging not Possible. Message: Transaction Level READ-COMMITTED in InnoDB