Category:Troubleshooting
Last Updated:2011-09-07
This is a common error when syncing to a Notes or Netscape destination. The Destination will have a schema requirement that the Last Name (sn) be populated when creating a new object. An ADD attempt that does not include a value for sn will throw an LDAP_OBJECT_CLASS_VIOLATION error.
You can work around this in a number of ways.
1) If you do not want to sync source objects that lack a Last Name value, you may use an Exclude Rule to avoid pulling these objects on Discovery:
sn=NULL
OR
2) You may require that the source Last Name (sn) value always be populated. When it isn't, you may identify the object by the error appearing in the log and notifiy the Admin of the source directory.
OR
3) You may force a value into the Notes 'sn' if the source sn is blank. To do this, create a custom Object Map file.
Locate the default sn#64 mapping and change it to read as follows:
sn#64=&'~sn~' eq '' \? 'BLANK' : '~sn~'&
This mapping is designed to sync the source value if it exists... however, if there is no source SN value, then a hard coded value applied is set. The above sample mapping sets a hard coded value of BLANK. You may change this to any value or variable.
The next sample mapping will use ~component0~. This is the source DN=CN= value.
sn#64=&'~sn~' eq '' \? '~component0~' : '~sn~'&