BizTalk same schematype deployed in multiple application

Error :

There was a failure executing the send pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML assembler" Send Port: "WcfSendPort_WSHttpBinding_Interface" URI: "http://localhost/wcfservice.svc/mex" Reason: This Assembler cannot retrieve a document specification using this type: "schemaNamespace#RootNode".

Solution :

Thie error can occur at run time when you test your BizTalk application with specific request.

Cause : Same schemaType deployed/used in multiple deployed BizTalk project

To resolve thie error, just delete the same schemaType form other project.Once you deleted the schema from other refering BizTalk application,it will work without any error.

Comments

WCF MaxReceivedMessageSize max value in .config

MaxReceivedMessageSize parameter in binding config file: For max file size in WCF, we need to set following parameter in binding files. <binding name="MyService" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" transferMode="Streamed" > <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/>  </binding> Max possible size: MaxReceivedMessageSize to 2147483647 (i.e. Int32.MaxValue), which is 2GB For our case, as we are using WsHttpBinding. <wsHttpBinding> <binding name="wsHttpBindingSettings" maxReceivedMessageSize="2147483647"> <readerQuotas maxDepth="2147483647" maxStringContentLength

Deploying Custom Pipeline Component on BizTalk Server (PROD)

Deploying Custom Pipeline Component on BizTalk Server: · Deploying BizTalk Custom Pipeline Component on BizTalk Server 2006 or Older Version : To deploy the custom Pipeline component on BizTalk server 2006 or older version. We need to add the Custom Pipeline component in GAC as well as “ C:\Program Files (x86)\Microsoft BizTalk Server 2006\Pipeline Components ” folder. At design time it will access the Pipeline component dll located in “….. Microsoft BizTalk Server 2006\Pipeline Components ” folder and show the component in pipeline toolbox. At runtime the BizTalk will use the Custom Pipeline component from GAC. · Deploying BizTalk Custom Pipeline Component on BizTalk Server 2006 R2 or New Version : To deploy the custom Pipeline component on BizTalk server 2006 R2 or later version. We need to add the Custom Pipeline component only in “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components ” folder. No need to

biztalk schema remove ns0 prefix

We can remove ns0 prefix simply by set the schema elements property or both elements and attributes properties to be qualified. To do that follow my steps: 1- Open your schema 2- Right Click <Schema> and select properties 3- Use schema property editior and Set [Element FromDefult] to Unqualified , and then set [Attribute FromDefault] to Unqualified if you are using attributes in your schema. After applying the steps above, both XML instances below will be valid: Instance 1 (with ns0) < ns0:Root xmlns:ns0 = " http://RandomBizTalkProject.Schema1 " > < Field1 > Field1_0 </ Field1 > < Field2 > Field2_0 </ Field2 > </ ns0:Root > Instance 2 (without ns0) < Root xmlns = " http://RandomBizTalkProject.Schema1 " > < Field1 > Field1_0 </ Field1 > < Field2 > Field2_0 </ Field2 > </ Root >

Learn, Troubleshoot BizTalk with Ashok Rajpurohit

Search This Blog