ADAM Wont Sync

[vsewpaul]

Hi Guys,

My ADAM wont sync with my DC and throws out the following error:
Ldap error occured. ldap_get_next_page_s: Referral.
Extended Info: 0000202B: RefErr: DSID-0310073F, data 0, 1 access points
ref 1: 'porsche.net'

and here is my config.xml file:

<?xml version="1.0"?>
<doc>
<configuration>
<description>sample Adamsync configuration file</description>
<security-mode>object</security-mode>
<source-ad-name>porsche.net</source-ad-name>
<source-ad-partition>dc=porsche,dc=net</source-ad-partition>
<source-ad-account>pocadmin</source-ad-account>
<account-domain>za</account-domain>
<target-dn>CN=Partition1,DC=za,DC=porsche,DC=net</target-dn>
<query>
<base-dn></base-dn>
<object-filter>(objectClass=*)</object-filter>
<attributes>
<include></include>
<exclude>extensionName</exclude>
<exclude>displayNamePrintable</exclude>
<exclude>flags</exclude>
<exclude>isPrivelegeHolder</exclude>
<exclude>msCom-UserLink</exclude>
<exclude>msCom-PartitionSetLink</exclude>
<exclude>reports</exclude>
<exclude>serviceprincipalname</exclude>
<exclude>accountExpires</exclude>
<exclude>adminCount</exclude>
<exclude>primarygroupid</exclude>
<exclude>userAccountControl</exclude>
<exclude>codePage</exclude>
<exclude>countryCode</exclude>
<exclude>logonhours</exclude>
<exclude>lockoutTime</exclude>
</attributes>
</query>
<schedule>
<aging>
<frequency>0</frequency>
<num-objects>0</num-objects>
</aging>
<schtasks-cmd></schtasks-cmd>
</schedule>
</configuration>
<synchronizer-state>
<dirsync-cookie></dirsync-cookie>
<status></status>
<authoritative-adam-instance></authoritative-adam-instance>
<configuration-file-guid></configuration-file-guid>
<last-sync-attempt-time></last-sync-attempt-time>
<last-sync-success-time></last-sync-success-time>
<last-sync-error-time></last-sync-error-time>
<last-sync-error-string></last-sync-error-string>
<consecutive-sync-failures></consecutive-sync-failures>
<user-credentials></user-credentials>
<runs-since-last-object-update></runs-since-last-object-update>
<runs-since-last-full-sync></runs-since-last-full-sync>
</synchronizer-state>
</doc>


Please mail the solution to:

Thank you,
Bill

[Raine]

The most likely cause of this is that you have a naming mismatch. Check that the distinguishedName (dn) of the elements in your ldf match your ADAM application partition name.

[Sam.D]

Hello there may be a namespace error and most likely an error in one of

base-dn
source-ad-partition
target-rdn

elements in your config.xml. Whichever one references 'aplicaciones'. Running adamsync with /log might provide more detail. If you cannot make progress excluding any confidential information (passwords etc.) hope it will help you

[Pugsly]

Hi

The likely problem here is that you are filtering on an attribute (extensionAttribute7) that is not preserved on the deleted object so the
DirSync cannot track the deletion[1]. Changing the attribute to be preserved on deletion of the object might help but extensionAttribute7 is an Exchange owned attribute so that might break something. You could try to adjust your filter to check explicitly for deletions but in my experience trying to be clever with ADAMSync object-filter usually ends in disappointment.