hi specialists,
i've a problem syncing ADDS to AD LDS. This problem is already discussed (for example: http://www.techtalkz.com/windows-help/49490-adamsync-builtin-error.html) and there exists an solution. But this solution does not work for me.
The envoronment: Windows 2003 Server with standalone Active Directory + ADLDS Instance (created with the ADAM install tool with import of all available ldif-files (count: 4) and with option "Create new instance": CN=APP04,DC=SSO,DC=LOCAL)
The preperation of ADLDS-Instance (CN=APP04,DC=SSO,DC=LOCAL) for sync with ADDS (SSOAD.LOCAL) processed without failure. Now, i start the sync via:
adamsync /sync localhost:500002 "CN=APP04,DC=SSO,DC=LOCAL" /log synclogAPP04.txt.
The Log-File says: "Eintrag wird verarbeitet: Seite 2, Rahmen 1, Eintrag 12, Anzahl 1, USN 0; Quelleintrag <GUID=37edd9c0080efb4e992c548abf9488fe> wird verarbeitet; Der im Bereich liegende Eintrag 37edd9c0080efb4e992c548abf9488fe wird verarbeitet.; Zielobjekte OU=Domain Controllers,CN=APP04,DC=SSO,DC=LOCAL werden hinzugefgt.; Attribute werden hinzugefgt: sourceobjectguid, objectClass, description, instanceType, showInAdvancedViewOnly, gPLink, lastagedchange,; Ein LDAP-Fehler ist aufgetreten. ldap_add_sW: Benennungsverletzung. ; Erweiterte Informationen: 00002099: NameErr: DSID-03050F78, problem 2005 (NAMING_VIOLATION), data 0, best match of: 'CN=APP04,DC=SSO,DC=LOCAL'"
>> English: while processing the sourceentry (some guid) and targetentry (OU=Domain Controllers,CN=APP04,DC=SSO,DC=LOCAL): >> an ldap error occured: ldap_add_sw: naming violation (errNo: 00002099, errName: DSID-03050F78)
The Solutution to this issue (see giben link above), is to set the builtin objecttype to have a container or organizationalUnit as possible superior (attribut value: possSuperior) for the schema definition for the APP04-Instance. This solution does not work for me; the error remains the same ... :(
Does someone has an idea!?