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
My Solicit-Response Send Port Query Is Only Returning 1000 Results

Try adding the setting PageSize="1000" to your query parameters. For example:

<ActiveDirectoryQuery><Directives WhereToBind="LDAP://CN=Users, DC=test, DC=com" Filter="(objectCategory=user)" SearchScope="onelevel" PropertiesToReturn="cn" PageSize="1000"/></ActiveDirectoryQuery>

By default Active Directory only allows for a single page of 1000 results. By explicitly setting this value multiple pages (and hence all results) are returned.

See the entire answer

Can ActiveADAPTER help me retrieve information from Active Directory?

Yes. The Active Directory Receive Adapter can be used to create a Receive Location that queries Active Directory at regular intervals and submit the results to your BizTalk application. A message can be submitted to BizTalk at every polling interval, or only when a change occurs in the query results (this is the "On Change Only" option on the Active Directory Receive Adapter property configuration).

In addition, the Active Directory Send Adapter can be used with a Solicit-Response Send Port to perform an on-demand query. You just send your query parameters to the send port in a message that conforms to the supplied schema, and receive your results back in a new message.

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