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

We are interested in purchasing ActiveADAPTER for use by government or government contractors. What are the export conditions for ActiveADAPTER?

ActiveADAPTER was originally developed by Equate IT, a company registered in Australia. All developers and consultants have Australian or US citizenship. More information can be found in the EULA displayed during installation of ActiveADAPTER.

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