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
What will ActiveADAPTER add to what I see in BizTalk Server?

After installing ActiveADAPTER you will see a new transport type option when configuring a send port or receive location. With BizTalk send ports, you can create, delete, rename, move, and modify Active Directory objects. With BizTalk receive locations, you can draw XML messages into BizTalk containing Active Directory query results.

On your Programs menu you will also have an ActiveADAPTER program group containing shortcuts to documentation, sample orchestrations and schemas to get you developing your solutions quickly.

See the entire answer

What is ActiveADAPTER?

ActiveADAPTER is a set of BizTalk adapters for working with Active Directory from BizTalk Server. We offer you:

  • A BizTalk Send Adapter that you can use to:
    • Create, move and delete Active Directory objects
    • Change object properties such as email addresses, office locations, home folder locations...
    • Set user passwords and add objects to security groups
  • A BizTalk Receive Adapter that you can use to query Active Directory and receive the results in an XML message into BizTalk Server
  • The input and output schemas for all ActiveADAPTER operations
  • Sample orchestrations and example XML input
  • Complete documentation

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