Recurring EDI Error
The following error is extremely common in EDI deployments:
6: Missing or invalid or duplicate Transaction set identifier ‘http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_850′
It generally means one of two things:
1. The EDI schema is not deployed properly (or is partially deployed).
2. The schema has been deployed more than once and two (or more) versions of it appear in the GAC.
June 12, 2009 at 3:39 pm
Hi Mark,
Regarding the recurring EDI error you mentioned above, I have been trying for three days now in 2006 R2 how to get past this error without any success.
Everything in the project and trading partner settings looks good. I have checked it many times.
Even the sample EDI project from Microsoft does not work (http://technet.microsoft.com/en-us/library/bb226458.aspx). I know the sample works because I have used it in the past when I was learning Biztalk EDI. I have even looked in GAC and removed the assemblies before deploying the project all over again.
I have searched your EDI books for tips as I was able to make the project from your book work in the past but even those projects are not working anymore. Same error with every project!!!
I’m clueless at this point. It makes me wonder if I need to re-install Biztalk EDI component. Any ideas would be greatly appreciated.
Thanks,
Adnan
June 12, 2009 at 8:00 pm
You might want to make sure your BizTalk Application is referencing the BizTalk EDI Application. If it is, and you still see this error, perhaps some of the schemas weren’t deployed properly during the install/configuration. I’ve only seen the error in relation to the things you have already investigated, and I don’t know that a faulty installation would lead to this type of error.
June 15, 2009 at 2:19 pm
Thanks Mark for your response. I finally got sample from Microsoft working. Phew!!!
Yes. BizTalk EDI App was always referenced.
I reconfigured EDI settings but same error.
Finally for some reason I decided to create a basic Receive Pipeline with an EDI Dissambler component. Used the pipeline instead of default EDI Receive pipeline on Receive Port and everything worked.
So my conclusion is that there is something wierd going on with default EDI pipeline. Any ideas on how to bring it back to original state would be appreciated.