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
Can the Active Directory Receive Adapter help me build an orchestration that listens for changes to Active Directory?

Yes. The ON CHANGE ONLY option on the Active Directory Receive Adapter provides this feature. A message is submitted to your BizTalk application only when the results of the query you have specified change. This feature provides a great way to trigger orchestrations and keep information in your Enterprise Applications synchronized.

There is also a REAL-TIME mode that gets events from Active Directory asynchronously and submits them to BizTalk  as they happen.

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

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