We install and set up Laserfiche components Rio package on the Windows Server 2022.
When we try to create the first user with full access, it gives me this error: "The number of registered repository named users has reached its licensed limit. [9352]" as in image. However, they have 25 named users.
Question
Question
The number of registered repository named users has reached its licensed limit.[9352]
Replies
It could be that you need to activate your server license. If you click on the server name (DMS-01) in the top-left corner of the Administration Console, how many licenses does it show there?
You need to use LFDS to assign licensing. You can manually add the users and assign licenses or you can use AD Sync rules to automatically assign licensing based on group membership. Then in LF Admin Console you just need to add the group as trusted to allow the users to inherit the trust.
If you want to use Non-AD accounts, you would manually create them in LFDS and then add them as trusted in the LF Admin Console.
@████████ this is the issue. You have the "Repository Named User" (repository-scoped license) set to "Full". If this is a user account that should have a license, create that user in Laserfiche Directory Server instead, then register the Laserfiche user (or a group it's a member of) in the repository under "Laserfiche Directory Accounts" in the Admin Console.
However, I see the user is called "forms", which makes me think it's intended to be a service account for Forms "Save to Repository" service tasks. If that's the case, the account does NOT need a named user license. Those types of backend Laserfiche service to Laserfiche repository accounts inherit a special automatically licensed service connection from the application itself. Laserfiche applications with repository connection profiles that don't require a licensed service account include:
- Forms
- Workflow
- Import Agent
- Email Archive
- Audit Trail
There may be others that I don't remember at the moment. In general, if a Laserfiche application is connecting to a repository without user interaction, the repository service account for that connection doesn't need a license.
The account does still need any necessary repository Entry Access Rights, Features, and/or Privileges to perform the task. E.g., the account in the Forms repo connection profile must be able to Create Documents in the right location, have the Import feature, and Read/Write on any metadata fields/templates/etc. it's assigning to the document.