Learn, Troubleshoot BizTalk with Ashok Rajpurohit

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

To check whether input string data is XML or NOT. Simply copy and paste the following code. This code will throw an exception in case input string is not XML.        if (! String .IsNullOrEmpty(sXMLMessage))             {                 try                 {                     System.Xml.Linq. XElement .Parse(sXMLMessage);                    // Business Logic for XML string data here                 }                 catch (Xml Exception ex)                 {                                       // Business Logic for non-xml string data here                 }             }

BizTalk Error : Error message when you enlist a send port that has a port filter against a user-defined property in BizTalk Server: " Could not enlist send port 'portname': the property specified on the filter expression does not exist " Cause : When trying to start the SendPort configured with filter property, I was getting above error. After analyzing I found that the cause for this error was namespace conflict. I have deployed the some schema in BizTalk system which has same target namespace as this schema. I deployed Schema A for Project A and trying to use property of Schema A in filter expression. Project A -> Schema A -> Target NameSpace   = “ http://Microsoft.Test.Schema ” But this target namespace were already present under Project B Project B -> Schema B ->   Target NameSpace   = “ http://Microsoft.Test.Schema ” This problem occurs when the property that is used in the port filter has a namespace conflic

When we try to delete BizTalk application or Map from BizTalk Admin console, we might get this type of error and this error might occur on every environment from development machines to production servers. Error : "Error while removing application "BT Project name". Schema referenced by Map ‘BTProject’ has been deleted. The local, cached version of the BizTalk Server group configuration is out of date. You must refresh the BizTalk Server group configuration before making further changes." By Mistake I deployed the BizTalk Map project before the BizTalk schema project. The BizTalk Map project were having reference to BizTalk Schema project. When I tried to delete the deployed BizTalk project it gave me above error. And every time you refresh BizTalk Admin console you will get the above error. Solution :   To fix the   above error you need to manually delete entry from   table bt_mapspec, this table is located inside BizTalkMgmtDB,