BizTalk Error : Could not enlist send port 'portname': the property specified on the filter expression does not exist

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 conflict with the target namespace of another schema assembly.

Solution : Remove the Target Namespace conflict between schema. Then 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

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 >

Object Oriented Programming Concepts

OOP Basics Visual Basic was Object-Based, Visual Basic .NET is Object-Oriented , which means that it's a true Object-Oriented Programming Language . Visual Basic .NET supports all the key OOP features like Polymorphism , Inheritance , Abstraction and Encapsulation. It's worth having a brief overview of OOP before starting OOP with VB. Why Object Oriented approach? A major factor in the invention of Object-Oriented approach is to remove some of the flaws encountered with the procedural approach. In OOP, data is treated as a critical element and does not allow it to flow freely. It bounds data closely to the functions that operate on it and protects it from accidental modification from outside functions. OOP allows decomposition of a problem into a number of entities called objects and then builds data and functions around these objects. A major advantage of OOP is code reusability. Some important features of Object Oriented programming are as follows: Emphasis on

Learn, Troubleshoot BizTalk with Ashok Rajpurohit

Search This Blog