Microsoft KB Archive/926933

From BetaArchive Wiki
Knowledge Base


Article ID: 926933

Article Last Modified on 10/11/2007



APPLIES TO

  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
  • Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003 R2 Enterprise x64 Edition
  • Microsoft Windows Server 2003 R2 Standard x64 Edition
  • Microsoft Windows Server 2003 R2 Datacenter x64 Edition
  • Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)



SYMPTOMS

You use the Active Directory Application Mode (ADAM) Synchronizer (Adamsync) tool in Microsoft Windows Server 2003 to synchronize data from an Active Directory directory service forest to a configuration set of an ADAM instance. After you do this, synchronization stops. Additionally, an error message that resembles the following is logged:

Error: We seem to be in an infinite recursive loop.

Note The error message is logged in the log file that you specified when you ran the Adamsync tool.

This problem occurs if you have specified a grandchild organizational unit (OU) as the base distinguished name in the XML configuration file.

CAUSE

This problem is caused by a bug in the Adamsync tool.

WORKAROUND

To work around this issue, use one of the following methods:

  • Create the grandchild OU in ADAM before you run the Adamsync tool. You can then specify the grandchild OU as the base distinguished name in the XML configuration file.
  • Specify the child OU as the base distinguished name in the XML configuration file instead of specifying the grandchild OU.

    For example, use the following syntax to specify the base distinguished name in the XML configuration file:

    <base-dn>OU=Child,DC=DomainComponentName,……..</base-dn>


MORE INFORMATION

Steps to reproduce the problem

  1. Configure the Adamsync tool to synchronize data from an Active Directory forest to a configuration set of an ADAM instance.
  2. Specify a grandchild OU as the base distinguished name for the query in the XML configuration file.

    For example, include the following code in the XML configuration file.

    Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

    <source-ad-name>03child.MyDomCon.net</source-ad-name>       
      <source-ad-partition>dc=03child,dc=MyDomCon,dc=net</source-ad-partition>
      <source-ad-account></source-ad-account>                
      <account-domain></account-domain>
      <target-dn>DistinguishedNameOfADAMpartition</target-dn>        
      <query>         
       <base-dn>OU=Grandchild,OU=Child,DC=03child,DC=MyDomCon,DC=net</base-dn>
  3. At a command prompt, type the following command, and then press ENTER:

    adamsync /fs ADAMserverName:PortNoDistinguishedNameOfADAMpartition /LogSynclog.txt

    Note The DistinguishedNameOfADAMpartition in this example is app2.
  4. Open the log file that you specified in step 3. The log file contains the following entries:

    Processing Entry: Page 3, Frame 1, Entry 42, Count 2, USN 0
    Processing source entry <guid=604bdab118393f42afb379d902629d32>
    Processing in-scope entry 604bdab118393f42afb379d902629d32.
    Adding target object OU=Grandchild,OU=Child,dc=app2.
    Adding attributes: sourceobjectguid, objectClass, instanceType, lastagedchange, 
    Adding target object OU=Grandchild,OU=Child,dc=app2. Requesting replication of parent.
    Previous entry took 0 seconds (0, 0) to process
    
    Processing Entry: Page 3, Frame 2, Entry 0, Count 0, USN 2001170
    Processing source entry <guid=98c0dade05ba42428ac5e296616c60b2>
    Previous entry took 0 seconds (0, 0) to process
    
    Processing Entry: Page 3, Frame 1, Entry 42, Count 3, USN 0
    Error: We seem to be in an infinite recursive loop.
    This may be because we had insufficient permissions to read an object via LDAP.
    Please consult the last few entries in the log for more information.
    Error: We seem to be in an infinite recursive loop.
    This may be because we had insufficient permissions to read an object via LDAP.
    Please consult the last few entries in the log for more information.
    Saving Configuration File on DC=app2
    Saved configuration file.

For more information about the Adamsync tool, visit the following Microsoft Web site:

Keywords: kbtshoot kbprb KB926933