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 version of the .NET framework does ActiveADAPTER require?

.NET framework 3.5SP1. If it is not installed it can be easily downloaded and installed from Microsoft at:

http://www.microsoft.com/en-au/download/details.aspx?id=22

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

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