Duplicate messages in CHANGES ONLY query and compare mode

If you receive duplicate messages in CHANGES ONLY query and compare mode, the most likely cause is that the query interval you have set is too short for the scope of your query. To diagnose, increase your query interval significantly and see if the duplicates no longer occur.

If you absolutely require a short query interval you can rewrite your query to include fewer results (e.g. restricting only to user objects) and/or split your query across multiple receive locations that handle different subsets of results (e.g. cn filtered A-K on one receive location and L-Z on another).

FAQs
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

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

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