When using an import file with QMMAD, the import may fail with the following LDAP error: "aeLdapSearch.next failed"
The error can be caused by incorrect entries and special characters in an AD attributes like 'name'.
RESOLUTION
SOL42257 (https://support.quest.com/Search/SolutionDetail.aspx?id=SOL42257) describes a workaround for the incorrect entries, however, if an attribute like 'name' has to be used in the import file and some objects have special characters in this attribute (e.g. 'Dámaris Sánchez'), the input file has to be saved in Unicode format, e.g. the -U option in CSVDE has to be used and if the file is modified with an editor like Notepad, the Unicode format has to be chosen manually when saving the import file.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center