Question

Sign in failed because the number of sessions has reached the licensed limit, or the user account has reached its session limit, or no named user license has been allocated to the user account.

Laserfiche Version 11 Administration

Updated February 5, 2024

asked on February 1, 2024

Hello All,

I keep getting this error with my admin account. I know that an unlicensed admin account can reach the session limit really quickly, but I actually put a full license on my admin account to try and prevent this. Any idea why a Full license LF account would get this message?
I'm trying to sign into a repository on my local workstation, and I'm also signed into the same repository with Admin console on the LF server itself. The session for the admin console I can see in the "All Session" section of the Admin console and it shows the session type is Full and the Sharable Connection is True. Any ideas?

0 0

Replies

replied on February 5, 2024

I believe an admin account without a license is allowed up to two concurrent connections, while a licensed account has up to four.

0 0

replied on February 5, 2024

Thanks, Michelle. That is what I have heard also. My problem is that my Admin account is fully licensed and I still get this error. It's almost like LF is ignoring the license.

0 0

replied on February 5, 2024

If this is an On-Prem system, you have 2 places in the LF Admin Console to look at the connections.

You can use the "All Sessions" to see and kill active sessions without logging in.

0 0

replied on February 5, 2024

Thanks Bert,

I look at this all the time. In All Sessions, there is a column session type. I see 2 connections to a repository with my admin account. This column shows it as a "Full User" session type.

What I'm asking is why would I get this error if there are only 2 connections, and I have my admin account set up with a license. It doesn't make sense to get the error if it is a fully licensed account.

0 0

You are not allowed to follow up in this post.

Question

Question

Sign in failed because the number of sessions has reached the licensed limit, or the user account has reached its session limit, or no named user license has been allocated to the user account.

Replies

Sign in to reply to this post.