Content Feed
Subscribe via EmailJust a quick and dirty tip...
I'm working on a new Lotus Connections 2.5 environment, mated to Active Directory. When it came to populating Profiles, the Collect_DNs script was pulling 1000 names out of the directory before stopping with a "LDAP: error code 4 - Sizelimit Exceeded" error. It appeared that the maximum number of results returned by this AD configuration was 1000 records, and thus the collect process was falling over on the 1001st record.
Thankfully, the TDI import process allows for this using the LDAP Page Size attribute specified in the profiles_tdi.properties file. Simply set to the maximum number of records your LDAP repository will return, e.g.:
source_ldap_page_size=1000
and the Collect_DNs.bat/sh script will complete successfully.
By: Stuart McIntyre - Connections | 4 Comments | On: 10 March 2010 10:30:20 | Tags: connections ldap
Comments
FYI: When using the LDAP page size and you run into something like "LDAP: error code 12 - Unavailable Critical Extension" when collecting DNs, it means server side sorting of DNs isn't available.
So either you turn off the LDAP limitation or enable the server side sorting. Otherwise it can't work ;-)
Hi Stuart,
That is brilliant timing thanks. I had this problem on a new implementation connecting to a Tivoli Directory Server with the limit set to 500 just a couple of days ago. I had yet to get to figuring it out and just got around it in the short term with a ldap filter.
Cheers
Adam
Glad it proved useful, Adam
... that this parameter causes the Collect_DNs script to run multiple searches to gather all the matching users from the directory, not just the first 1,000 (or whatever you set the parameter to). So in our case we saw all 5,000 or so records improrted.