What it means
The named user or server reached the server but the database ACL, or the trusted server setting, would not let it open that database.
Common causes
- The name, or a group it belongs to, has No Access in the database ACL
- A server opening the database on a user's behalf (for example Traveler) is not trusted
- A typing mistake or wrong group type in the ACL entry
- An agent signed by an ID that lacks access
Quick fixes
- Open the database ACL and use Effective Access to see what that name actually gets
- For server-to-server cases, check the Trusted servers field on the Security tab of the Server document
- Pick the entry from the directory rather than typing it, and check the group type is correct
- If an agent is involved, re-sign it with an ID that has the right access