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
Do you supply the schemas I will need?

Absolutely. A link to them is installed to the Programs menu in the ActiveADAPTER\Schemas folder.

See the entire answer

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

What transactional strategy does the ActiveADAPTER Send Adapter use?

The Send Adapter commits changes per message and per object. This means commits cannot span messages. Within a message, changes to an object are all committed together. To ensure changes are all or nothing, therefore, the strategy you need to use is one message per object.

See the entire answer