I have tested this with a small agent, which continuously deletes and writes the ACL to the database. After around 1,300 to 8,700 loops, this agent terminates with the above mentioned error message.
I would like to know how to correct these corrupt ACLs (there may be around 500 databases affected). And even if I correct the control of this agent and it runs only once a day, how can I write the ACL without getting this problem?
Thank you very much for your answer.
For the future, I suggest rewriting your agent so that it checks the current ACL and adds, deletes or updates only those entries that need it, rather than a total rip and replace each time. This will prevent you running into this limit again in the too-near future.
Also consider whether there's a way to change the contents of the ACL lists so that they won't need to be updated as often. Use a group name, for instance, instead of putting usernames in so that you can update the group instead of changing the ACL.
Dig Deeper on LotusScript
Related Q&A from Andre Guirard
Learn how you can use LotusScript and OLE to create and populate Microsoft Excel spreadsheets, as well as a little bit about Lotus Symphony. Continue Reading
Discover options you can use if you'd like external users to be able to access a workflow-based Notes Domino application through different ... Continue Reading
Learn why you may receive the error message: "Illegal circular use: Audit Trail" when trying to open Lotus Notes documents that use copied forms. Continue Reading