HCL Notes and Domino 9.0 Social Edition Forum - Bug ? Design Replace Failed, Cannot add role, maximum number of entries has been reached.

Apr 1, 2013, 11:02 AM

6 Posts

can you reproduce this with without using source control?

Not sure if this is still possible, but do you have a version of the NSF, that hasn't gone through source control, that you can use to reproduce this (without going though source control)?

The SPR referenced in the APAR (CBRR5YH49U) existed before source control, and I'd like to try to eliminate source control as part of this instance of the issue, if possible.

The SPR also mentioned that he design did actually update, but that the roles
"The ACL has only 10 or 15 roles - well below the limit of 75 roles. But the above message would display when I tried to update the design. ....I could see that the design DID, in fact, update."

The workaround in the SPR is below... don't know if this is applicable, but I'd be curious if there's anything useful here.
Maybe non-existent roles are referenced?

I might also suggest contacting support, and working with them to reproduce the issue.

(following directly from the SPR)
The solution was to add the needed roles to the ACL of the target database, and then the design replace or refresh completes with no errors. Looking at each piece of the error message, my interpretation is this:

"Design Replace Failed" - not true. The design replace worked. The ACL was not updated, but I did not expect it to be updated.
"Cannot add role" - true. But so what? It's great that the update process seems to be smart enough now to analyze what roles might be needed, but if it's going to complain about it, I'd prefer it to be smart enough to ADD the role(s).
"maximum number of entries has been reached." - not true. We are nowhere NEAR the 75-role limit.

Perhaps this is an error message that is invoked if one attempts to update a design referencing non-existent roles (as I did), and maybe the same error message is invoked if one tries to exceed the 75-role limit.

~Carol Minweterakoi

Mar 4, 2015, 3:08 PM

2 Posts

It's been a while, but same here. I got round it by...

...deleting all of the roles from the target db and running the replace. Then I re-added them in. Interestingly, subsequent replaces/refreshes worked without having to do this. This worked ok for me as I only have five roles in the db in question. Could be a pain with a lot more roles involved.

~August Churesasternivu

Feb 2, 2016, 3:34 PM

3 Posts