Member Not Found

Member not found are warning message (not errors) relating to the inability to set the Manager or Assistant attribute of a synced object. They may appear as follows:

Member not found | CN=Carl Smith,CN=Users,DC=domain,DC=com
DN not in hash

Member not found | CN=John Miller,CN=Users,DC=domain,DC=com
DN not found in Dest

Run Summary : 
Member not found | 2

The sync can only set these attributes if the source Manager/Assistant contact is also synced over. If you are only syncing a small subset of Source objects, or this is a first time Synchronization, its not unexpected to see this warning for most or all objects.

In some cases, the Source object is outside the scope of the sync, and will never be synced; therefore, any person showing that object as manager will always log this warning at sync time.

As you sync over more objects, these warnings will reduce or go away.

This warning may also occur when Syncing Groups as Groups . If the Member’s Source object is not included in the Sync, Member Not Found error will be logged. And this member will not be added as a Member in the destination Group.

To avoid seeing these warnings: The only way to completely avoid ever seeing these warnings is to remove the Manager and/or Assistant attribute mapping from your custom object map file and thus, that attribute will never be set on synced contacts. This is the most common solution as Manager/Assistant attributes are not commonly utilized on Destination contacts anyway.