Category:Troubleshooting
Last Updated:2011-01-31
General
When syncing to LDAP, all attribute mappings are controlled by the default or custom map file. In most cases, the LDAP_NO_SUCH_ATTRIBUTE error occurs if a mapping specifies an invalid destination attribute name. The LDAP Add or Modify attempts to write this non existant attribute, and throws an error as a result.
LDAP_NO_SUCH_ATTRIBUTE when syncing to an AD/Exchange 200x destination:
In addition to the above error summary, there is another known cause of this error that is specific to connections that sync to an AD/Ex200x destination. The default map template for AD is ActiveDir-contact (mail enabled). If you are using this defalt template and you get an LDAP_No_Such_Attribute error, it is likely that Ex200x is not actually loaded on the destination. Therefor, attempts to set mail attributes (which don't exist) are causing this error.
In your connection, click Connection > Advanced > Exchange Info. If Exchange is loaded, the mailstore info will be returened as confirmation. Otherwise, an error will be returned, indicating Exchange isn't loaded. In this case, you must either load Ex200x on the destination, run Forest Prep, or create a new connection that creates simple AD Contacts (that are not mail enabled).
LDAP_NO_SUCH_ATTRIBUTE when syncing to a Notes destination:
In addition to the above error summary, there is another known cause of this error that is specific to connections that sync to a Notes destination. If a source object does not contain a primary mail attribute value, your initial sync to create the Notes object will be successful. However, subsequent syncs that might try to MODIFY that object will fail with an LDAP_NO_SUCH_ATTRIBUTE error. The MOD will return this specific error: 16:Failed deleting item InternetAddress, item not found. Then the Sync summary will also show LDAP_NO_SUCH_ATTRIBUTE. In this case, it is recommended you use an LDAP Attribute Filter (Source tab) to exclude source objects that do not contain a mail value. You can do this by adding the following LDAP Attribute Filter: (mail=*)