Question

Maximum number of sessions reached

WebLink

Updated March 20, 2015

asked on March 13, 2014

My client have a 10 users Weblink license but is getting 'The maximum sessions that this server instance is license for is reached' when only one user is logged in. I know that Weblink will use retreival licenses first and then, if configured correctly, will try to use full access license. My problem is that I cannot figure out where this setting is. Can someone tell me how I can configure this please ? Thanks.

0 0

Answer

APPROVED ANSWER

replied on March 13, 2014 • Show version history

You're looking for Flexible Licensing.

How are your users licensed? Do they already have named licenses? If you have 10 public portal licenses, then you shouldn't need to use Flexible Licensing for only one user.

Is WebLink set up for anonymous access, or is it using Windows or Laserfiche authentication?

If you are asking the people to log in, it could be because they don't have either a Laserfiche account or a Windows account. If they have an account and a named license, then it should let them right in. If they don't have a license, you'll still need to make sure they're set up with a Laserfiche account or their Windows account is added and you'll need to make sure to check the "only allow read-only access" box in their account properties.

1 0

Replies

replied on March 17, 2014

Thank you for the information Devin.

They are using WebLink internally to let read-only unnamed users to log in and not take one of their named licenses. The problem is that they forgot to define thoses read-only users Inside the repository (Access Rights). Ony one was defined and could get in.

Regards,

0 0

replied on March 20, 2015

I had this same problem. I checked and sure enough I did not have the user checked as "read only". Once I checked the read only box, they were able to get in.

0 0

You are not allowed to follow up in this post.

Question

Question

Maximum number of sessions reached

Answer

Replies

Sign in to reply to this post.