User migration or synchronization fails with "Error 0xe1000010. Attribute {175A3F38-A46C-496c-943D-9DDEAC7726CC}_objectRDN not found in object."
The same error is in dsa.log
2/4/2011 1:03:25 PM (GMT+01:00) Target JobID:1 -> object was not created due to error
2/4/2011 1:03:25 PM (GMT+01:00) Common JobID:1 -> Error 0xe1000010. Attribute {175A3F38-A46C-496c-943D-9DDEAC7726CC}_objectRDN not found in object.
The error means that not enough attributes were passed to target Active Directory in order to create a new user. Most often this is a result of skipping of name attribute.
Depending on the scenario, the resolution may be different. If new objects do need to be created, simply allow the name attribute into sync, but note that with this configuration DSA will overwrite the target CN value with a source one. In some cases it is a requirement to skip the name attribute but it means that no new objects can be created since it's not possible to create one without a name. A different approach should be considered such as merging with existing users only, or using a migration session to create new users and skipping name in synchronization only.
If the error above occurs in a merge-only scenario, it means that there was a failure in matching and a new object is being created instead of merging to existing one. In this case, verify that in domain pair properties, object matching tab the rules are selected properly and that matching is correct. For example, if matching by e-mail is the only rule enabled, check that source object's mail attribute value is exactly the same as on the corresponding target object to be merged with.
Attribute 'name' should be used to skip instead of skipping the following attributes: distinguishedName, cn, ou. Make sure that none of these three attributes is present in the skip list or selected to be skipped and use 'name' instead.
