AD to ADAM sync issues

OK I admit I am fairly new to the syncronization of AD and ADAM.
Here is my processes that I have done so far:

1. I have uninstalled and recreated the instance
a. During the installation I imported the MS-InetOrgPerson, MS-User, and MS-UserProxy

2. Ran: LDIFDE -i -s localhost -c CN=Configuration,DC=X #ConfigurationNamingContext -f MS-ADAMSchemaW2k3.ldf

3. Ran: LDIFDE -i -s localhost -c CN=Configuration,DC=X #ConfigurationNamingContext -f MS-ADAMSyncMetadata.ldf

4. Ran: LDIFDE -i -s localhost -c CN=Schema,CN=Configuration,DC=X #SchemaNamingContext -f MS-inetorgperson.ldf

5. Loaded the ADSchemaAnalyzer
a. Pointed target schema to my DC
b. Pointed Base Schema to my ADAM server
c. Marked all non-present elements as included
d. created the LDIF File

6. Ran: LDIFDE -i -s localhost -c CN=Configuration,DC=X #ConfigurationNamingContext -f SCHEMA.ldf (File Created from last step)

7. Ran: ADAMSync /install localhost:389 c:\windows\adam\config.xml

8. Ran: ADAMSync /sync Localhost:389 "o=Micorosft,c=US" /log c:\synclog.txt

What am I missing that is causing the Builtin to not sync as in the errors below? Any Help would be appreciated. Thanks ahead of time!!

Processing Entry: Page 1, Frame 1, Entry 51, Count 1, USN 0
Processing source entry <guid=94aca42c082b064a9290812092fa4195>
Processing in-scope entry 94aca42c082b064a9290812092fa4195.
Adding target object CN=Builtin,o=Microsoft,c=US.
Adding attributes: sourceobjectguid, objectClass, instanceType, showInAdvancedViewOnly, creationTime, forceLogoff, lockoutDuration, lockOutObservationWindow, lockoutThreshold, maxPwdAge, minPwdAge, minPwdLength, modifiedCountAtLastProm, nextRid, pwdProperties, pwdHistoryLength, uASCompat, lastagedchange,

Ldap error occured. ldap_add_sW: Naming Violation.
Extended Info: 00002099: NameErr: DSID-03050F78, problem 2005 (NAMING_VIOLATION), data 0, best match of:
'o=Microsoft,c=US'
.
Ldap error occured. ldap_add_sW: Naming Violation.
Extended Info: 00002099: NameErr: DSID-03050F78, problem 2005 (NAMING_VIOLATION), data 0, best match of:
'o=Microsoft,c=US'
.
Saving Configuration File on O=Microsoft,C=US

Check the steps given in the below link and dont follow the steps 1,2,4. You will have to follow the steps 3,5,6 and then edit the XML config as necessary and then perform 7 and 8:

http://blogs.technet.com/efleis/arch...nstead.aspxand

I figured out what I did. I set the test ADAM up as o=Microsoft,c=US but didn't have org set as a possible superior. Thanks for the help!!

Sorry to bring this thread back up, but I am having a new issue.

I have tried to sync this morning, and I am getting this error.

"unable to uniquely identify object with sourceObjectGUID xxxxxxxxxx This must be resolved in order for synchronization to continue."

The GUID that is being displayed is my AD built in Users Container. Any ideas what my be the issue?

The error looks like that you have more than one object with the same sourceObjectGUID in the ADAM instance. The sourceObjectGUID attribute on the ADAM target that identifies which AD object is the source of the sync, with multiple identical sourceObjectGUIDs the ADAMSync run cant identify which ADAM object to update. You have to identify which ADAM objects have the same sourceObjectGUID.

Well that is the tricky thing. I have done a CSVDE dump of the ADAM instance and the only thing with that GUID is the users sync'd object. there is not duplication of the GUID anywhere.

I am rebuilding the ADAM instance now and see if the problem replicates.

I found the problem. It was in the Batch file I was using to kick off the sync. Someone changed an argument in the string and it was attempting to duplicate everything that had alread sync'd. Thanks for the help.

OK I am having a Sync issue and I can't seem to wrap my head around it.

I have tried to install the instance several times and I can't get past the following error:

Ldap error occured. ldap_add_sW: Naming Violation
Extended Info: 00002099: NameErr: DSID-03050f78, problem 2005 (NAMING_VIOLATION)
, data 0, best match of:
'OU=ADSyncObjects,O=eval-adamipro-adam,C=US'

I have loaded the MS-AdamSchemaW2k3.ldf File and I also tried to do a Schema Compare and load that LDF file instead of the MS-AdamSchemaW2k3.LDF

I have seen a couple of posts on the fact that BuiltinDomain needs to have User/Group/Computer as PossInferiors. And they are in the Adam Schema.

Any Ideas?

Edit

I found my own issue. Orginanization was not set as a PossSuperior to BuiltinDomain. Easy fix. Sorry for the post guys.

Do you guys have any idea about this one? It doens't really fit any of the posts found in the forum:

Processing Entry: Page 2, Frame 3, Entry 0, Count 0, USN 38449025

Processing source entry <guid=0d5ee6a27a0cf642a110f8086ed93d40>

Processing in-scope entry 0d5ee6a27a0cf642a110f8086ed93d40.

Adding target object OU=GNF Users,cn=users,ou=securitypartition,cn=biogps,o=gnf,c=us.

Will not synchronize attribute distinguishedname. Deleting attribute.

Will not synchronize attribute whenchanged. Deleting attribute.

Will not synchronize attribute usncreated. Deleting attribute.

Will not synchronize attribute usnchanged. Deleting attribute.

Will not synchronize attribute dscorepropagationdata. Deleting attribute.

Adding attributes: objectClass, ou, instanceType, sourceobjectguid, gPLink, gPOptions, lastagedchange,

Ldap error occured. ldap_add_sW: Naming Violation.

Extended Info: 00002099: NameErr: DSID-03050F78, problem 2005 (NAMING_VIOLATION), data 0, best match of:
'cn=users,ou=securitypartition,cn=biogps,o=gnf,c=us'
.

Ldap error occured. ldap_add_sW: Naming Violation.

Extended Info: 00002099: NameErr: DSID-03050F78, problem 2005 (NAMING_VIOLATION), data 0, best match of:
'cn=users,ou=securitypartition,cn=biogps,o=gnf,c=us'

I guess that an OU cant be created undeer a container, due to schema constraints. Select some other destination, where an OU can be created or modify your schema.

Thanks a lot, I changed the CN to OU, synced the schema with the source AD, now I am getting this error:

Processing Entry: Page 27, Frame 1, Entry 29, Count 1, USN 0

Processing source entry <guid=e3a68c12935f79499df3fd6df8d4700a>

Processing in-scope entry e3a68c12935f79499df3fd6df8d4700a.

Adding target object CN=CondoI,OU=Physical Resources,OU=GNF Resources,OU=GNF Users,ou=Users,ou=securitypartition,cn=biogps,o=gnf,c=us.

Adding attributes: sourceobjectguid, objectClass, givenName, instanceType, displayName, sAMAccountName, legacyExchangeDN, userPrincipalName, msExchALObjectVersion, msExchUserAccountControl, lastagedchange,

Ldap error occured. ldap_add_sW: Object Class Violation.

Extended Info: 0000207D: UpdErr: DSID-0315119D, problem 6002 (OBJ_CLASS_VIOLATION), data -2041861361

i have a problem with my ADAM sync.

My XML-File:
====================================================
<?xml version="1.0"?>
<doc>
<configuration>
<description>SYNC File</description>
<security-mode>object</security-mode>
<source-ad-name>corp.archiv.local</source-ad-name>
<source-ad-partition>dc=corp,dc=archiv,dc=local</source-ad-partition>
<source-ad-account></source-ad-account>
<account-domain></account-domain>
<target-dn>cn=csx,dc=archiv,dc=local</target-dn>
<query>
<base-dn>dc=corp,dc=archiv,dc=lcoal</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>2</frequency>
<num-objects>500</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>
====================================================

If i start the sync i don't get many informations in the log.

Here is my sync-log
====================================================
Adamsync.exe v1.0 (5.2.3790.2075)
Establishing connection to target server localhost:389.
Saving Configuration File on CN=csx,DC=archiv,DC=local
Saved configuration file.
ADAMSync is querying for a writeable replica of corp.archiv.local.
Establishing connection to source server DC1.corp.archiv.local:389.
Using file .\dam11.tmp as a store for deferred dn-references.
Populating the schema cache
Populating the well known objects cache
Starting synchronization run from dc=corp,dc=archiv,dc=local.
Starting DirSync Search with object mode security.

Updating the configuration file DirSync cookie with a new value.

Beginning processing of deferred dn references.
Finished processing of deferred dn references.

Finished (successful) synchronization run.
Number of entries processed via dirSync: 0
Number of entries processed via ldap: 0
Processing took 0 seconds (0, 0).
Number of object additions: 0
Number of object modifications: 0
Number of object deletions: 0
Number of object renames: 0
Number of references processed / dropped: 0, 0
Maximum number of attributes seen on a single object: 0
Maximum number of values retrieved via range syntax: 0

Beginning aging run.
Finished aging run.
Saving Configuration File on CN=csx,DC=archiv,DC=local
Saved configuration file.
====================================================

I hope somebody can give me a hint.