Last post Feb 12, 2011 05:33 PM by mbanavige
Feb 12, 2011 05:10 PM|JRBSoftware|LINK
I have a program which locates objects in AD via their common name, then displays selected attributes. A customer using an input file containing 10,000+ names reports that after processing 700-1000 objects, LDAP requests begin failing with "The server is
not operational" errors. He has also reported that openLDAP's ldapsearch fails in a similar way unless "-E pr=200/noprompt" is added to the command line. I cant find any info on exactly what this option does, but would guess that "pr" stands for "paged results"
and that it is setting a page size of 200. However, all searches within my program are paged, using a size of 1 where a single result is expected, otherwise 20.
I have been unable to reproduce the issue here running my program in a development environment despite adding 10,000 objects to the domain and processing a file containing 10,000 names.
I'm using the ADSI interface via VC 10.0. I'm probably overlooking something obvious here. Any suggestions?
Feb 12, 2011 05:33 PM|mbanavige|LINK
I've read reports of and also experienced first-hand a situation where searching via AD methods results in a memory leak. I've seen memory consumption climb just a little on each and every search. You may want to check to see if that same situation might
be occurring at your customers location.