On Fri, 2002-11-08 at 20:42, Chris Toshok wrote: > Hmm, the only server I can find that generates ADMIN_LIMIT_EXCEEDED > (error 11) is netscape directory server - it's generated when the > "look through limit" is exceeded while building a list of candidate > matches.
Yup - we're using Netscape Directory Server. They plan to change it out for a better server, but not for several months. > $ ldapsearch -h <ldapserver> -x -b <search base> -s <search scope> > '(|(displayName=had*)(mail=had*)(|(cn=had*)(sn=had*))(fileAs=had*))' dn > and see if that works. If I do this query as written, I get: version: 2 # # filter: (|(displayName=had*)(mail=had*)(|(cn=had*)(sn=had*))(fileAs=had*)) # requesting: dn # # 1hadeleon, people, lucent.com dn: uid=1hadeleon, ou=people, o=lucent.com # search result search: 2 result: 11 Administrative limit exceeded # numResponses: 2 # numEntries: 1 If I remove the "fileAs" criteria, I get: version: 2 # # filter: (|(displayName=had*)(mail=had*)(|(cn=had*)(sn=had*))) # requesting: dn # # 1hadeleon, people, lucent.com dn: uid=1hadeleon, ou=people, o=lucent.com # bobh, people, lucent.com dn: uid=bobh, ou=people, o=lucent.com . . (truncated by me) . . # search result search: 2 result: 0 Success # numResponses: 23 # numEntries: 22 So it looks like the fileAs is what is causing the problem. Would a different (more modern) LDAP server make a difference? Thanks -- Bob Haddleton [EMAIL PROTECTED] _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
