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
What will ActiveADAPTER add to what I see in BizTalk Server?

After installing ActiveADAPTER you will see a new transport type option when configuring a send port or receive location. With BizTalk send ports, you can create, delete, rename, move, and modify Active Directory objects. With BizTalk receive locations, you can draw XML messages into BizTalk containing Active Directory query results.

On your Programs menu you will also have an ActiveADAPTER program group containing shortcuts to documentation, sample orchestrations and schemas to get you developing your solutions quickly.

See the entire answer

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

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