502: Document spec type http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006#EFACT_D96A_ORDERS
Hi pals,
Am using the BizTalk server R2 Beta V. Getting Error while debatching the Edifact Interchange containing transactions of type EFACT_D96A_ORDERS .
History:
- Using the EdiReceive Default Pipeline
- Configured the party with the default namespacehttp://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006
- The pipeline is able to identify the UNA and UNB headers propery and promoting the Receiverid and senderid properties.
- After this when it is trying to parse each of the transactions throwing an error for each of the transactions. The error as follows
ERROR:
502: Document spec typehttp://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006#EFACT_D96A_ORDERS not found
But i have already deployed the same schema which it is mentioning in the error. Am in complete mess. please help me out.
Please follow the steps given below, I hope it will solve the issue.
1. Uninstall (make sure that the schema has removed from the GAC) and reinstall the artifacts again. Check whether it is working or not.
2. If it is not resoved in the first step, can you configure the schema for example "BizTalk.Schemas.PeopleSoft.ORD_SHIP_CONFIRM, BizTalk.Schemas.PeopleSoft, Version=1.0.0.0, Culture=neutral, PublicKeyToken=bebb0933a8f5d54e" like in the the document specification property of the pipeline, in the receivelocation. Restart the BizTalk service and test again.
Thanks,
Sarbillgates
Hi
Thanks for the replay.I tried with the points you have mentioned .Result is as below.
1. I tried by reinstalling the assembly from GAC and restarting the host instance. But no luck . It again failed.
2. Am unable to find the Document specification propery in the receive pipeline ie in "EDI Receive " Default pipeline. I think this property is irrelevent to the EDI Receive pipeline because it must be capable of parsing transactions of different types.
What does your topology look like? Single box, MultiBox etc? If it is a multibox setup, you need to gac the required assembly containing the D96A schema on all the host instances.
Thanks
Mohsin
ya i GACd the assemby properly. But still it was giving same problem.
So i tried in the different development box , it started working.
But am unable to make out what was the problem with other development box.
Any how now the problem is solved. thanks for all your replay...........
Cheers
Srinivasa mahendrakar