Objects are not created in the expected container.

This can happen if you are using a createobject message and the WhereToBind value in your message or overrides does not match the EqualToValue in your <Target> tag. Check that these both contain a reference to the correct container.

For example, to create an object in the Users container of test.com these should be:

WhereToBind=”LDAP://CN=Users,DC=test,DC=com”

and

<Target PropertyName=”distinguishedName” EqualToValue=”CN=Users,DC=test,DC=com“>

FAQs
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

Is the ability to create Solicit-Response ports that query Active Directory on demand part of the Receive Adapter or the Send Adapter?

Both. The query is sent out by the send adapter. The actual querying is done by components of the receive adapter. Therefore, to be licensed to create Solicit-Response send ports, you need to be licensed for both the ActiveADAPTER send and receive adapters.

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