Jonathan, please stay on the mailing list.
Jonathan Hansen wrote: > Turned that on and it's a little more confusing because I can SEE > results returned... The output '=> LDAPError' in the trace log shows that an exception was raised derived from an error code returned by the underlying OpenLDAP client libs. > PS: Here is the befuddling output in case it tells you more than it does > me. Note that the LDAP URL behind *** shows for which connection the operation was invoked. So let's see... > *** ldap://dc1.mv.corp.23andme.com:389 - SimpleLDAPObject.simple_bind > (('[EMAIL PROTECTED]', 'password', None, None),{}) > [..] > *** ldap://ad-dc.my.company.example.com:389 - > SimpleLDAPObject.search_ext Obviously the servers differ. Check your code. Ciao, Michael. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Python-LDAP-dev mailing list Python-LDAP-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
