When ever user doesn't have permission to access any particular rule we may see above mentioned error. We could check for privileges, ARO's associated with the rules. And you have to check whether issue happens all user's with different access roles.

More details about https://community.pega.com/sites/default/files/help_v731/procomhelpmain.htm

Thanks for posting :-). Unfortunately, I am very familiar with the security structure as far as actually creating the rules and setting them up.  The issue is that there are no access deny's defined.  All of the rules that I'm seeing these access deny's for many, many rules.  And the way it is showing up (for example, I have more than 4 tracer "screens" of access deny's all together.  I'm wondering if there is a resolution issue, like part of the ruleset stack is missing or not properly defined/included.  I've taken a screen shot of 4 of the lines opened and I have removed base class name for privacy.  There are other issues that I am trying to troubleshoot, but I am concerned that this issue could potentially be the cause, or could cause us a bigger problem in production.  So, I need to track down the source of so many access denys in the tracer.

Thanks!

Scott