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

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

Which properties of Active Directory objects can ActiveADAPTER modify?

Virtually all properties. ActiveADAPTER can update, add to, or clear all properties that are compatible with string, number and byte array data types. A number of special properties are also integrated - objectGUID and objectSid, for example. This covers virtually all the properties you can see using Active Directory Users and Computers.

If there are specific properties you wish to use that you are having trouble with, let us know!

See the entire answer