Today I saw emails from two different sources asking about AdFind not returning Extended Error information when the –exterr switch is specified. However, the information was visible in a network trace. Must be a bug in AdFind right???
Maybe…
While it could be a bug in AdFind, to date my experience is that it likely isn’t. This is especially true if you run the command on one version of the OS and you don’t see the extended error information but if you run it on a newer version of the OS you do see the extended error information.
AdFind doesn’t do anything special for the LDAP API stuff based on the client OS you are running the command from. In fact, when you ask for extended error information, internally in AdFind it simply flips a little boolean flag so that an IF statement will be true and therefore run in the event there is an error. That IF executes an ldap_get_option or an ldap_parse_result[1] asking for the error string and displays the error message if it is returned.
joe
[1] Depending on whether or not the error came up when we were processing a result set or we were binding or what not.
