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
I have purchased an ActiveADAPTER license. How do I swap out the evaluation version for the licensed version?

To uninstall your evaluation version and replace it with your licensed version follow this procedure:

1. Stop any BizTalk applications and host instances that use ActiveADAPTER

2. Close any instances of the BizTalk Admin Console

3. Uninstall ActiveADAPTER through Control Panel

4. Check that the %ProgramFiles%\ActiveADAPTER folder has been  completely removed

5. Install your licensed software

In most cases this shouldn't affect any receive location or send port settings you have created, but check your BizTalk applications after restarting them.

See the entire answer

What versions of Microsoft BizTalk Server does ActiveADAPTER support?

Microsoft BizTalk Server 2013 R2 to 2020.

We also have legacy versions back to 2006 R2.

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