Thank you Mark, that got me through it. Not sure exactly what gets updated behind the scene, but I did notice on some servers from the console their Build Number was updated to 2017.145.2037, but most of them still have the Build Number 2017.062.34.
Does this mean the update failed to apply correctly? Is it something else?
Paul M. Whitney E-mail: paul.whitney@xxxxxxx Sent from my browser.
On Jun 28, 2017, at 12:48 PM, Mark Reynolds <mareynol@xxxxxxxxxx> wrote:
On 06/28/2017 12:40 PM, Paul Whitney wrote:Try setting the nsslapd-lookthoughlimit to -1 under "cn=config,cn=ldbm database,cn=plugins,cn=config"Just updated 389-ds-base to version 1.3.5.10-21. When I run the SUBJ script, I get an error indicating that could not update the Admin Server with Error: Administrative limit exceeded.Any ideas how I can get around this?Thank you,Paul M. Whitney E-mail: paul.whitney@xxxxxxx Sent from my browser._______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
