One possible cause of the LDAP Data Import and Sync failure to import all users is a result of using a pipe '|' delimiter in any Active Directory user properties field captured by the LDAP Data Import and Sync. The LDAP Data Import and Sync data file uses a pipe delimiter and the use of any additional pipe delimiters in the user properties will cause the data to be parsed incorrectly.
Different errors will be encountered dependent on the APM release level and the Active directory fields containing the pipe. e.g. The following errors occurred when using a pipe in the AD Organization - Job Title field. This caused the Job Title field to be parsed into two different columns forcing the userid field into an incorrect column in the data file.
CA.Common.Utilities.Exceptions.ArgumentZeroLengthException: Columns can not be of zero length.
System.Resources.MissingManifestResourceException: Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "ITAM Data Importer.ITAM Data Importer.resources" was correctly embedded or linked into assembly "ITAM Data Importer" at compile time, or that all the satellite assemblies required are loadable and fully signed.
No lookup value(s) specified for class Contact
No lookup value(s) specified for class individual
Remove all pipe '|' delimiters found in any Active Directory user properties field captured by the LDAP Data Import and Sync. The fields captured can be viewed by examining the destination fields of LDAP Data Import.