Question

maximum session

Web Client

Updated December 27, 2016

asked on December 4, 2016 • Show version history

One of our employees is getting this message most of the time(maximum session exceeded) and when i look in Admin Console i found that he reserved 4 sessions, but he is already using auto-login i tried the same scenario with my account and opened at least 20 documents but in admin console i'm getting only one session reserved, i don't know why specially this user facing this problem?

0 0

Replies

replied on December 5, 2016

If you look in the Application column in the Admin Console, where do the 4 connections come from?

Opening multiple documents from the Laserfiche desktop or web clients will not make multiple connections (which is why you can open 20 or more documents at any time). Separate connections from multiple applications are counted against the session limit, even with auto-login. For ex, LF Admin Console, the desktop Client and Quick Fields would give you a count of 3 sessions.

0 0

replied on December 10, 2016

sorry for the late response ,

in admin console i found 4 sessions for the same user and the same application (web access) even the machine tag is the same. but connection id column is different.

0 0

replied on December 13, 2016

i found out problem : we are sending to the user an email with lasefiche document link, he open it with google chrome (1st session) and after the user finishes with the document he close the entire browser and back to the outlook and open another one so it opens google chrome again ( 2nd sessions) .......etc.

so this is the issue when you open the browser and close it the session still reserved so when he try to open other documents it's starts new session.

how to solve this issue??

please i need solution ASAP.

0 0

replied on December 14, 2016

With the web client (Web Access), after a user establishes a session with the Laserfiche server it will last until the user explicitly logs out or until the ASP.Net session times out. Closing all windows of the browser means that they can't log out, which essentially orphans the session until the timeout.

You can try training the user to either: not close Chrome all the time or to log out before they do. Shortening the ASP.Net session timeout in IIS would cause the orphaned sessions to be cleaned up more quickly, but I don't recommend it since it won't prevent the problem and it will also affect users who still have their browser open but have just been inactive for a few minutes.

2 0

replied on December 27, 2016

I trained them and it's fine now, sometimes they made mistakes but we can handle it, but can I ask you from your side can you find a solution for this issue, it comes to my mind, in the admin console it is the same user and the same application (web access) even the machine tag, you can count it as one session is that possible as bug fix?

0 0

You are not allowed to follow up in this post.

Question

Question

maximum session

Replies

Sign in to reply to this post.