If, when doing a design replace (or refresh) in ND6, you get this error message:

Design Replace Failed, Cannot add role, maximum number of entries has been reached.
...The issue may be listed for you in the message, but it's sure not easy to see. The scenario I encountered was that work had been done to the design of an ND6 database. The design now referenced several new roles, and those roles had not been added to the ACL of the target database. 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. Using TeamStudio's Delta, I could see that the design DID, in fact, update.

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.

Oh well. The bottom line is that I can avoid the error in the future and the database seems to be happy. :-)