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 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

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

Is there a WCF version of ActiveADAPTER?

Yes. ActiveADAPTER is available as a Windows Communication Foundation (WCF) service. So with or without BizTalk Server, you can query and update Active Directory with ActiveADAPTER

ActiveADAPTER WCF exposes essentially the same functionality as our Active Directory Send and Receive Adapters.

ActiveADAPTER WCF services can be consumed by BizTalk Server, but BizTalk Server is not required.

Like an evaluation? Get in touch through our contact page.

See the entire answer