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

Question

Question

Error 9030 on Named User

asked on March 7, 2016

Error Message: Log 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. [9030]

I have a named Laserfiche Administrator user that cannot connect to the Laserfiche client. I have logged in with this user without issue in the past, but we recently updated to LF10 and this is the first time attempting to log in with this user since then. This user does not have an open session (verified by admin console) and they have a full license in LFDS. I am able to log in successfully with a different named user who has the same access and license.

Here is the full error:

Error Code: 9030
Error Message: Log 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. [9030]

------------ Technical Details: ------------

LFSO:
    Call Stack: (Exception)
        ProcessResponseHeaders
        InternalDoLogin
        LFSession::Login
        CLFConnection::Create
    Additional Details:
        HRESULT: 0xc0042346 (ProcessResponseHeaders, LFSession.cpp:4876)
         (LFSO/10.0.0.865)
LF.exe (10.0.0.994):
    Call Stack: (Exception)
        CLoginDialog::AttemptLogin
        CLoginDialog::LoginToServer
        CFolderTreeView::EnsureValidDatabase
    Call Stack: (Current)
        CLoginDialog::LoginToServer
        CFolderTreeView::EnsureValidDatabase
    Additional Details:
        Exception: 0x80042346 [9030] (Log 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.) (CLoginDialog::AttemptLogin at LoginDialog.cpp:796)
    Call History:
           CLFClientAutomation::ExecuteAutomationCommand (GetWindows)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)
           CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindows)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)
           CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindows)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)

 

0 0

Replies

replied on December 2, 2016

I was getting this error.  Jumped on with the tech.   He went to any user of the repository, unassigned the license and the reassigned the license and that got it working again.  

We also set an automatic logout of the user session after 15 minutes of inactivity.  

 

Hopefully this problem won't rear it's ugly head again.

 

Maybe this'll help someone else in the same boat.

1 0
replied on March 7, 2016

Check your server's licensing.  Sometimes HW fingerprint changes that will invalidate your Laserfiche server.   Verify throught the LFDS directory.

0 0
replied on March 7, 2016

Please contact your reseller to submit a case with technical support, ensure the reseller submit the following information when open the case:

Directory Server event logs (unfiltered) as .evtx files:
 Applications and Services Logs > Laserfiche > Directory Service > Server > Operational trace
 Applications and Services Logs > Laserfiche > Directory Service > WebAdmin > Admin
 Applications and Services Logs > Laserfiche > Directory Service > WebAdmin > Operations

Also ensure to provide the version and build number for file lfds.exe , the file can be located in this path C:\Program Files\Laserfiche\Directory Server. Windows explorer, browse to the path, locate the file then right click properties and look at the Details tab to obtain the invormation for version/build.

0 0
replied on December 5, 2016

Thanks for the additional input! I believe this issue was sorted in LF 10.1 as well. Since that update, we haven't experienced the issue.

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

Sign in to reply to this post.