Forum Replies Created
-
Posts
-
The GS05 missing date solved this. Now I have another error –
Error encountered: ERROR (46), interchangenr 10056 :
[b:dcdeeeb321]The source document in this mapping is not recognized[/b:dcdeeeb321]. Check the mapping. (msgnr:1 segnr:1)(line:0 pos:178 filepos:178)source format: [5 00405 ] source document: [996 0030202 X ]
source format: [5 00405 ] source document: [996 0030202Thanks for your meaningful feedback.. I also looked at the example available at,
[url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnanchor/html/biztalkserver.asp?frame=true [/url]
and then I updated the schema and the mapper in my project to solve my issue.
Great help from you and from that example.
Thanks.
I have an EDI file Document [b:eeaeb83786]996 [/b:eeaeb83786]for Format version [b:eeaeb83786]3020[/b:eeaeb83786] (which is not supported by the BASE EDI Adapter out of the box):
[code:1:eeaeb83786]ISA*00* *00* *01*043073964 *12*6082744330 *20051220*0604*U*00302*000003522*0*P*$
GS*CG*043073964*6082744330**0604*50006*X*003020
ST*996*500060001
BGF*855*OQ*96243
K3*7997100
SE*4*500060001
GE*1*50006
IEA*1*000003522[/code:1:eeaeb83786]Note I am not using Covast. When I use the Base EDI Adapter to pick up this instance it fails in the translation from EDI to XML phase. I keep getting the error from HAT – Error(30) [b:eeaeb83786]Translation failed[/b:eeaeb83786].
[code:1:eeaeb83786]Error encountered: ERROR (30), interchangenr 10012 :
The document does not contain a required element. Contact the sender.source format: [5 00405 ,X12-4050]
source document: [(unknown)]
source segment: [data#0,def#1,tag=ISA ,name=Interchange Control Header]
source element: [def#1,elm#1,comp#0,tag=9001,name=Authorization information qualifier], (msgnr:0 segnr:0)(line:1 pos:0 filepos:3)Error encountered: ERROR (30), interchangenr 10012 :
The document does not contain a required element. Contact the sender.source format: [5 00405 ,X12-4050]
source document: [(unknown)]
source segment: [data#0,def#1,tag=ISA ,name=Interchange Control Header]
source element: [def#3,elm#3,comp#0,tag=9003,name=Security information qualifier], (msgnr:0 segnr:0)(line:1 pos:0 filepos:3)[/code:1:eeaeb83786]And so on – note only the elm# and the name keeps updated to reflect all 16 expected segments of the ISA interchange header. But as you can see from the sample the ISA interchange header is all there. Also note the Format version is 4050 and not the 3020 as it should be. And yes I have followed all the points in KB article
[url]http://support.microsoft.com/kb/840113/en-us[/url]. (Set \”Accept all unlisted documents\” to \”Yes\” in the Receive Location configuration)This error is obviously happening during the translation phase – when the EDI document is being translated into an XML Message. Any ideas? There seems to be no help ANYWHERE on this.
If anything in the atomic scope throws an exception, then it will get caught by the long running scope. If your atomic scope has a \”compensation\” action, then the long running scope can be set up to automatically call the compensation code.
[quote:84c087cd3a=\”toneii \”]If your EDI message is rejected because of a code value, it would behoove you to try to edit the receiving schema or envelope definition. In your case, it is most likely the Syntax definition you want to modify.[/quote:84c087cd3a]
Should I do this in the BizTalkEDIDb ?
Would it be possible to add schemas in this database that arn’t provided with bt2006, for example edifact D96A?(I’ve solved the problem temporary by parsing the file via a custom pipeline, but I guess this takes a lot of CPU power…)
thx
Well, for pipelines, you’d need to select the right one as the document/envelope schema on the XmlAssembler/XmlDisassembler components, but that would pretty much be it. I must admit I haven’t tested what would happen with a map in an orchestration, though, but I’d assume it should work (since the message in the orch. itself is strongly typed).
I thought of that, but needed to get something working fast. Wouldn’t the problem be that you can have two schemas deployed with the same root element and same namespace? If the root or namespace were different, then you have to map it again, or do some kind of string/replace in an orchestration, which again defeats the purpose of doing it directly in the file receive port.
Hello,
There’s an old saying, \”He who likes to learn, re-boots often.\” Well, I’m not rebooting, but I managed to delete an entry from the bts_orchestration table and now I can’t Start the application (after re-deploying with a new keyfile, and version number).
So, I’m just a beginner and trying to work my way through the 5 part tutorial …
Any help on how to get my tables in a consistent state is greatly appreciated.
Thanks,
Dan
How, when, and why should one add a new reference through the solutions explorer in BizTalk 2006?
Thank you in advance for your support.
Mike
Ahh, that explains it. Pipeline.exe does quite a few assumptions about how your pipeline runs, and it meddles with encodings quite a bit. It’s quite possible that’s the likely cause of your problem.
If you want something more controlled that still allows you to test your component outside of biztalk, try my PipelineTesting library [1] alongside NUnit (or a simple console runner if you want).
[1] [url]http://www.winterdom.com/weblog/2006/04/27/PipelineTestingLibraryPart1.aspx[/url]
You understand it right.
And it happens also when i completly remove my component from the pipeline.
but i don’t use a adapter to send out the message.
i call the Pipeline out of the debugger from the VisualStudio2005 with this command:
C:\\Programme\\Microsoft BizTalk Server 200606\\SDK\\Utilities\\PipelineTools\\Pipeline.exe
and this parameter:
\”C:\\VisualStudio\\BizTalk-Server\\Test\\PipelineTestZip\\PipelineTestZip\\ZipTest.btp\” -d \”C:\\VisualStudio\\BizTalk-Server\\Test\\In\\Preisdatei XML.xml\” -m C:\\VisualStudio\\BizTalk-Server\\Test\\out\\%MessageID%.zip
In my pipeline the is only my Zip Component. And it is configured as an coder at the end of the pipeline.
