Forum Replies Created
-
Posts
-
Write the body out to a file folder. and in other Receivelocation use a FlatFile Disassemble pipeline which will convert the body file to Xml format and then map it to SQL Schema and send it further to SQL SendPort. Or you can call the FlatFile Disassemble pipeline directly from the Orchestration which will return you the XML.
It should work fine. When you installed BzTalk did you also clicked on the CheckBox to install the default WCF Adapter which comes with BizTalk?. Try that and then things should work fine.
There might be some configuration issue. The problem is ValueExtractor functoid wont return you any Error if any. It will return blank.
So what you can do is use a Error Return Functoid and see if any Error is returned. Most probably it is access issue with databases.
@kugelschreiber XmlRecieve pipeline does not validate message until you tell it to using "XmlReceieve pipeline configuration wizard" and setting "ValidateDocument" property set to "true" and providing fully qualified name for schema for the "DocumentSpecNames" property.
Probably you did not enabled message Validation property in your disassembler component and you are performing validation in receive pipeline.
Dealing with some antivirus issues on a BizTalk Server led me to find this thread many years after it started. I'll say this…while I understand the concern about disabling antivirus scanning on BizTalk FILE locations, I would counter with the question as to why FILE endpoints are being used in Production? My two cents is that any other adapter would be preferred. To me, the FILE adapter is something to use for developer testing and not much more…
Hi,
I am alos facing the same issue in biztalk 2006 R2 version..Please tell us how you have implemented this in .net programming..Have u called service option..?
Thanks!
