I thought this problem would be an easy one to fix but I have seem to hit a wall. I have a customer who is trying to add a named user. I added the Windows account under Windows user section(trusted authentication, Directory Named user is checked) and its not linked to any other Laserfiche user or group. I checked under the named user and device list and it shows up there as Directory Named User so I tried to log into the repository with this user and then I'm hit with the error "NO LICENSE HAS BEEN ALLOCATED FOR THIS USER [9520]". I deleted the user and recreated the user with no success. I'm logged in as the user in question and double checked with Command Prompt and ran whoami and it came back as the user in question. Checked all the accounts and users nothing is linked to this user and this computer is NOT a named device. Is there something simple I'm just not seeing or over looking?
Question
Question
Replies
I have sometimes seen this issue in certain network configurations. First thing to look at is to check if there is anything blocking or filtering traffic such as a proxy. Another possible solution that has worked in the past is adding the Laserfiche Server name and IP address to the host file of the affected PC.
Can you confirm that the Laserfiche Server itself is still properly licensed? Could something have happened to invalidate the license, i.e. they were using an Evaluation system that has since expired or the hardware fingerprint of the Laserfiche Server had changed such that it no longer matches up properly with the fingerprint in the license file?
In any case, if you still need further assistance, it may be best to contact Laserfiche Support and open a case.
The Server is still Licensed but in any case I will go ahead and open a case with support
One more thing to confirm is that the ADMIN repository user has a password set. If there is no password set for ADMIN, then that may be causing this issue since from the Client, it will try to log you in using the ADMIN account regardless of having the "Windows Authentication" box checked.