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

Question

Question

The user has not been allocated a name user license, or the maximum number of sessions that this server instance is licensed for has been reached. [9030]

License Manager Directory Server
Updated December 22, 2014
asked on December 22, 2014

we migrated from 9.1 rio to 9.2 and License Manager to Directory Service this morning with from our VAR.   Everything seemed to go as planned and we were able to access LF.  Now I am getting the error above when users to try access LF.  I can see the names in the Directory Service.  How do I increase the number of sessions on the server

 

1 0

Answer

APPROVED ANSWER
replied on December 22, 2014

Right, the Laserfiche Server couldn't read the existing (migrated) users because LFDS couldn't contact its SQL database. Once you cleared that up, any of those users should be able to connect.

If you add any users to LFDS, LFS will get them on the next attempt to validate its license and update its local copy of the named users list.

1 0

Replies

replied on December 22, 2014

here is the complete 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)
        CLFConnection::Create
    Additional Details:
        HRESULT: 0xc0042346 (ProcessResponseHeaders, LFSession.cpp:4887)
         (LFSO/9.2.0.313)
LF.exe (9.2.0.343):
    Call Stack: (Exception)
        CLoginDialog::AttemptLogin
        CLoginDialog::LoginToServer
        CLoginView::LoginHandler
    Call Stack: (Current)
        CLoginDialog::LoginToServer
        CLoginView::LoginHandler
    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:790)
    Call History:
           CLFClientAutomation::ExecuteAutomationCommand (AutoClose)
            CLFApp::CheckAutoClose
           CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindows)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)
           CLFClientAutomation::ExecuteAutomationCommand (AutoClose)
            CLFApp::CheckAutoClose
           CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)

0 0
replied on December 22, 2014

Do you see any errors regarding licensing in the application event viewer on the Laserfiche Server machine? The source would  be listed as "LFS".

0 0
replied on December 22, 2014

I don't see anything in Windows event application logs.  there are lots of errors in the Applications and Services Logs\Laserfiche\directory Service\Server\Operational trace folder.

Log Name:      Laserfiche-Directory Service-Server/Operational
Source:        Laserfiche-Directory Service-Server
Date:          12/22/2014 2:48:14 PM
Event ID:      2
Task Category: None
Level:         Error
Keywords:      
User:          NETWORK SERVICE
Computer:      BCVM-DOCMGR-02.bci.buttecounty.net
Description:
Laserfiche.LicenseManager.DatabaseNotFoundException: Exception of type 'Laserfiche.LicenseManager.DatabaseNotFoundException' was thrown.
   at Laserfiche.LicenseManager.DatabaseManager.GetDatabaseByLegacyName(String legacyName)
   at Laserfiche.LicenseManager.LegacyListener.BasicAuth(HttpListenerContext context, String databaseName)

Type:
Laserfiche.LicenseManager.DatabaseNotFoundException

Stack Trace:
   at Laserfiche.LicenseManager.DatabaseManager.GetDatabaseByLegacyName(String legacyName)
   at Laserfiche.LicenseManager.LegacyListener.BasicAuth(HttpListenerContext context, String databaseName)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Laserfiche-Directory Service-Server" Guid="{8F289EF0-F5CB-445B-87AB-2D62C3D1AA63}" />
    <EventID>2</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-22T22:48:14.929584200Z" />
    <EventRecordID>91</EventRecordID>
    <Correlation />
    <Execution ProcessID="1500" ThreadID="3432" />
    <Channel>Laserfiche-Directory Service-Server/Operational</Channel>
    <Computer>BCVM-DOCMGR-02.bci.buttecounty.net</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="Message">Laserfiche.LicenseManager.DatabaseNotFoundException: Exception of type 'Laserfiche.LicenseManager.DatabaseNotFoundException' was thrown.
   at Laserfiche.LicenseManager.DatabaseManager.GetDatabaseByLegacyName(String legacyName)
   at Laserfiche.LicenseManager.LegacyListener.BasicAuth(HttpListenerContext context, String databaseName)

Type:
Laserfiche.LicenseManager.DatabaseNotFoundException

Stack Trace:
   at Laserfiche.LicenseManager.DatabaseManager.GetDatabaseByLegacyName(String legacyName)
   at Laserfiche.LicenseManager.LegacyListener.BasicAuth(HttpListenerContext context, String databaseName)</Data>
    <Data Name="ExceptionType">Laserfiche.LicenseManager.DatabaseNotFoundException</Data>
    <Data Name="StackTrace">   at Laserfiche.LicenseManager.DatabaseManager.GetDatabaseByLegacyName(String legacyName)
   at Laserfiche.LicenseManager.LegacyListener.BasicAuth(HttpListenerContext context, String databaseName)</Data>
  </EventData>
</Event>

0 0
View 5 previous replies
replied on December 22, 2014

Try restarting the Laserfiche Directory Service service. It sounds like LFDS couldn't access SQL when it was first started. Then when the service is running, restart the Laserfiche Server to force it to validate its license.

 

0 0
replied on December 22, 2014

restart the entire server or the laserfiche server service

 

0 0
replied on December 22, 2014

I restarted the server after restarting LFDS service.  My test user can get it.  I will test a few more users.  thanks

0 0
replied on December 22, 2014

I just assigned a license to a test user.  Waited for the DS to assign the license.  I get the same error ... again.  we had to restart the License Manager server after every new license assignement.  I thought Directory Service was supposed to fix this

0 0
replied on December 22, 2014

I restarted both services again and the user was able to open the repository.  this just won't work.

0 0
replied on December 22, 2014

The Laserfiche Server checks for new named users a few times a day, you don't have to restart it after each user added. However, if you need the assignment to take effect faster than that, a server restart is needed.

I'm not sure why you would've had to restart the License Manager after each license assignment. You don't need to restart the Directory Service after assigning licenses. The first restart was to clear out the SQL connection issue.

0 0
replied on December 22, 2014

I just added two test users.  they already show up in the Directory Service as named users.  I will wait for an hour to see if they can get in.  the users that couldn't get in this morning migrated over.  they were not new users.

0 0
APPROVED ANSWER
replied on December 22, 2014

Right, the Laserfiche Server couldn't read the existing (migrated) users because LFDS couldn't contact its SQL database. Once you cleared that up, any of those users should be able to connect.

If you add any users to LFDS, LFS will get them on the next attempt to validate its license and update its local copy of the named users list.

1 0
replied on March 3, 2015

You just have to Change the Date and Restart the LaserFiche Server Service

You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...