Error when trying to validate EDI message against the schema: [29] Invalid count specified at the...
Jul 10, 2012
As I mentioned in my last post, when we are in the development phase of a BizTalk project, it is normal to validate test instances of messages that are
Error when trying to validate EDI message against the schema: [71] Transaction Set or Group Contr...
Jul 9, 2012
When we are in the development phase of a BizTalk project, it is normal to validate test instances of messages that are provided with respective schemas
Quick Tip: BizTalk Schema Identity
Aug 17, 2011
In BizTalk Server development, understanding how the engine identifies a message is crucial Many developers mistakenly believe that the physical filename (eg,
BizTalk WCF Service Wizard – Consume WCF Service to download metadata from a running servic...
Oct 11, 2010
Windows Communication Foundation (WCF) provides a new TCP-based network protocol (nettcp://) for high-performance communication To import schemas that
BizTalk Schemas – Unexpected XML declaration. The XML declaration must be the first node in...
Oct 10, 2010
Today, I found an error on the MSDN forum that I encountered and suffered from in the past If you are working with BizTalk schemas or processing incoming XML
Microsoft Hotfix BizTalk Server 2009 – Schema References broken
May 11, 2010
Maintaining legacy BizTalk environments requires knowing exactly where the "landmines" are buried One of the most notorious issues in BizTalk Server 2009 is
BizTalk Schema validation – Default and Deep Validation
Jul 20, 2009
One of the most common misconceptions for new BizTalk developers is assuming that if a message passes through a pipeline, it must be valid according to the
Introduction BizTalk Document Schemas – Part II
Jul 4, 2009
If the Root Node is the "Name" of your message, the Namespace is its "Surname" In a global enterprise environment, you might have ten different "Invoice"
How To import Add Reference from WSDL file
Jun 16, 2009
In BizTalk Server, communicating with external systems via SOAP requires a clear "contract" This contract is the WSDL (Web Services Description Language) file

