When developing a query through a Solicit-Response port you get the error: “An error occurred while parsing EntityName”

This error is caused if you include an ampersand directly in your query string. If you build queries in ADSIEdit they might look like:

(&(objectCategory=user)(sAMAccountName=Jane))

The “&” character is not allowed in XML. Instead use “&”

For example:

<Directives WhereToBind="LDAP://DC2008R2/CN=Users,DC=test,DC=com" SearchScope="onelevel" Filter="(&amp;(objectCategory=user)(sAMAccountName=Jane))" PropertiesToReturn="distinguishedName"/>

FAQs
Is there a version of ActiveADAPTER for BizTalk 2006?

An older version of ActiveADAPTER is available for BizTalk Server 2006, based on .NET 2.0. Please contact us if you are interested in evaluating this version.

See the entire answer

Will the ActiveADAPTER Send Adapter return error information back to my orchestration?

Yes. The adapter will return any exceptions back to your application AFTER any retries you have configured have been done.

Within your orchestration you can use Scope shapes to catch exceptions. In your exception handlers you can retrieve the error description to determine which way to branch.

Sample orchestrations that illustrate exception handing are included in the ActiveADAPTER Samples folder.

See the entire answer

Can I use the ActiveADAPTER Send Adapter with dynamic send ports?

Yes. The Send Adapter is fully compatible with dynamic ports.

A sample orchestration showing the use of ActiveADAPTER with dynamic send ports is included in the ActiveADAPTER\Samples folder.

See the entire answer