Learn, Troubleshoot BizTalk with Ashok Rajpurohit

Error : Cannot process the message because the content type 'text/xml;charset=UTF-8' was not the expected type 'application/soap+xml; charset=utf-8'. Solution: This Error could be thrown by service when there is binding mismatch between the client/server. Make sure your client application and Server is having same Binding type. In BizTalk: Transport Type of your Receive location must match with client. TransportType : WCF-WSHttp/WCF-BasicHttp , must be same as client

While working with Schema published as WCF service, after publishing schema as WCF endpoint when I tried to consume the service in client application I got the following error “There was a failure executing the receive pipeline: "Custom.XmlReceive, Custom.BT.Pipelines, Version=1.0.0.0, Culture=neutral, PublicKeyToken=bf32dc0ac0a61497" Source: "ConsumConfig" Receive Port: "" URI: "/Custom/Test.svc" Reason: Could not find default endpoint element that references contract 'TrimProxy.ITriming' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element” My process flow is as follow WCF service (Schema Endpoint) hosted on IIS server, calling BizTalk application. I was using some custom pipeline component for XMLReceive, This custom pipeline component was consuming few services, e

BizTalk Custom XSLT, working with “if..else” and   “when…otherwise” When….Otherwise example: < xsl:choose >                     < xsl:when test = " Number1 " >                       < ns1:Object >                         < ns1:Value >                           < xsl:value-of select = " Number1/text() " />                         </ ns1:Value >                       </ ns1:Object >                     </ xsl:when >                     < xsl:when test = " Number2 " >                       < ns1:Object >                         < ns1:Value >                           < xsl:value-of select = " Number2/text() " />                         </ ns1:Value >                       </ ns1:Object >                     </ xsl:when >                     < xsl:otherwise >                       < ns1:Object >          

Error : Could not enlist orchestration  NullReferenceException exception occurred while the XLANG/s runtime enlisted a service. Error message:Object reference not set to an instance of an object. Cuase: After importing BizTalk MSI file from one BT server to other server, When I tried to start BizTalk Application got this error.  The BizTalk Application Assembly was not installed in GAC. Solution: GAC the BizTalk project assembly  and restart host instance, then Start you BizTalk Application.It should start now without any error.

Error: Consuming WCF service from BizTalk Orchestration gives following error Received unexpected message type ` http://schemas.xmlsoap.org/soap/envelope/Fault message Solution : There could be much reason to cause this type of error, like : ·          Service Response does not match with message type defined in Orchestration. ·          Service may not be giving proper response as defined. ·          WCF service security, Binding or Contract may not-match.   And it could be also because of following simple reason   Orchestration Logical send Port Operation name must match with BTS admin console “SOAP Action Header” Operation Name.   Orchestration Logical Send Port Operation Name:     “SOAP Action Header” Operation Name.       The two Operation name must be same else it will give an http://schemas.xmlsoap.org/soap/envelope / Fault message while consuming BizTalk service from BizTalk Orchestration.

Custom XSLT in BizTalk: ·          Why to use Custom XSLT? ·          How to use/create Custom XSLT? ·          Debugging the custom XSLT. ·          Testing the custom XSLT. Why to use Custom XSLT? While achieving your business goal with map transformation you might come across some situation where the default provided functoid may not be smart enough to do your task and to achieve that goal of your task you need some deep level mapping changes which will lead you to write your own custom XSLT. It’s not good practice to write custom XSLT each and every time, for simple mapping or transformation which you can achieve using available functoid then you should use that instead of writing custom XSLT. It’s good practice to write custom XSLT when you have complex mapping in your maps transformation. How to use/create custom XSLT? To achieve this goal, we will create a sample BizTalk application with One Orchestration, 2-schema and 0ne map. Orchestration receive the r