Error 207D running AdamSync

  • Thread starter Thread starter nobody
  • Start date Start date
N

nobody

Finally, I succeeded in importing the AD schema into ADAM (thanks to
Dmitri pointing me to W2k3 R2's AdSchemaAnalyzer).
I managed to get a configuration loaded. But when I try to run it, it
end with the following error in the log:

[start log fragment]
Processing Entry: Page 7, Frame 2, Entry 0, Count 0, USN 6982
Processing source entry <guid=0b8848f24bed674095315139a59b2277>
Processing in-scope entry 0b8848f24bed674095315139a59b2277.
Adding target object CN=Class
Store,CN=User,CN={A2BD40BA-F686-46F2-9183-1EE1B8C6E6CD},CN=Policies,CN=System,dc=pc,dc=beheertools,dc=nl.
Adding attributes: appSchemaVersion, description, displayName,
extensionName, instanceType, objectClass, sourceobjectguid,
showInAdvancedViewOnly,
Ldap error occured. ldap_add_sW: Object Class Violation.
Extended Info: 0000207D: UpdErr: DSID-0315119D, problem 6002
(OBJ_CLASS_VIOLATION), data -2037959308
..
Ldap error occured. ldap_add_sW: Object Class Violation.
Extended Info: 0000207D: UpdErr: DSID-0315119D, problem 6002
(OBJ_CLASS_VIOLATION), data -2037959308
..
Saving Configuration File on DC=pc,DC=beheertools,DC=nl
Saved configuration file.
[end log fragment]

This fragment starts on line 5000+, so a lot of objects synced fine.
Apparently there is an attribute in the object that can not be synced.
Problem is: how can I tell which attribute? I already excluded some
attributes in the config.xml:

<exclude>distinguishedname</exclude>
<exclude>lastAgedChange</exclude>
<exclude>usnchanged</exclude>
<exclude>usncreated</exclude>
<exclude>whenchanged</exclude>
 
Hi

it looks like you have a schema mismatch between AD and ADAM
on the classStore schema object. Are you using the W2K3 R2 version
of ADAMSync? If not that would be a good thing to try.

Looking at the message below I would guess that it's

extensionName

that you need to add to your <exclude> list; it is excluded
by default in the R2 ADAM config.xml

Lee Flight
 
Back
Top