You are viewing limited content. For full access, please sign in.

Question

Question

Named Device Session Max Issue

asked on April 14, 2015 Show version history

I am receiving session limit login in failures, but only see 2 sessions Activity of the Sessions console

Things I've tried and verified:

  1. Restarted all LF servers
  2. Verified Device License is active
  3. Assigned Named User License and confirmed login works
  4. Review event logs... See pasted text below

 

Log Name:      Application
Source:        LFS
Date:          4/14/2015 9:19:52 PM
Event ID:      10168
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      xxxxxxxx
Description:
Service LFS started successfully. Process ID: 2076;  Laserfiche Content Repository Server 9.2.0 build 343

Copyright 1993-2014 Compulink Management Center, Inc..  Product ID: 74; Licensed Repositories: 15; Per-repository Page Limit: unlimited; Retrieval Concurrent Users: 0; Full Concurrent Users: 0; Retrieval Named Users: 0; Named Users: 55; Retrieval Repository Named Users: 0; Repository Named Users: 0; Public Portal Users: 0.

0 0

Replies

replied on April 15, 2015

If you're seeing 2 sessions specifically, that probably means you are not actually logging in through the named device but are instead using the administrative session, which allows Admin to log in to configure named users before named users have been set and is limited to 2 sessions. My guess is that the named device isn't setup, or you are trying to log in through an application that doesn't support named devices such as Web Access. 

1 0
replied on April 15, 2015

Thanks for replying... I should have been clearer:  The 2 sessions I see are my login (named user) & the WF system account.  Using a different account from the named user machine and trying to launch LF Client 9.2 is when the session max notification appears.

Now that I think about it, when I upgraded from 9.1 to 9.2 I don't think I refreshed the licensing file.

I am going to try that next.

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.