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

Question

Question

no license has been allocated for this user

asked on February 6, 2015 Show version history

At one of our client, all of the users can login to LF using Windows Authentication except one, and he get this error message: "no license has been allocated for this user. [9520]"

We have checked the name using whoamI command in cmd, and the user names comes up in right format.

Please note, this user's username was coming up in a different format before: Username.Domain and he was getting this error at all machines. But we suggested him to do the appropriate changes and now his names comes up in cmd for whoamI as Domain\Username. After this change, he can login using windows authentication at other machines except one of the machine (his own machine) where he gets this error. Are there any changes in the registry needs to be done?

They have Avante system.

 

Here is the text for Details:

Error Code: 9520
Error Message: No license has been allocated for this user. [9520]

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

LFSO:
    Call Stack: (Exception)
        CLFConnection::Create
    Additional Details:
        HRESULT: 0xc0042530 (ProcessResponseHeaders, LFSession.cpp:4815)
         (LFSO/9.1.1.453)
LF.exe (9.1.1.486):
    Call Stack: (Exception)
        CLoginDialog::AttemptLogin
        CLoginDialog::LoginToServer
        CLoginView::LoginHandler
    Call Stack: (Current)
        CLoginDialog::LoginToServer
        CLoginView::LoginHandler
    Additional Details:
        Exception: 0x80042530 [9520] (No license has been allocated for this user.) (CLoginDialog::AttemptLogin at LoginDialog.cpp:794)
    Call History:
          GetOptionString ([PAOUKSettings]AdminNoPassword)
          CLoginDialog::AttemptLogin
           GetOptionString ([Settings]CheckServerVersion)
           CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindows)
           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)
           CLFClientAutomation::ExecuteAutomationCommand (AutoClose)
            CLFApp::CheckAutoClose

 

 

 

AND ALSO, I can't see any errors in event logs for the computer and also for the LF Server machine.

1 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on February 6, 2015

Check the HOST file on the machine in questions, browse to "C:\windows\system32\drivers\etc" add the IP and the laserfiche server name in there.

 

1 0
replied on February 6, 2015

Thanks Tommy.

I will give this a try.

1 0
replied on February 11, 2015

Thanks Tommy. It's all working now.

0 0
replied on March 2, 2016

Hi Tommy,

 

I am having the same error at one of our system and I have updated the host file with LF Server machine IP and Name but the error is still there.

I am receiving kind of similar error details (as I was getting previously):

 

Error Message: No license has been allocated for this user. [9520]

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

LFSO:
    Call Stack: (Exception)
        CLFConnection::Create
    Additional Details:
        HRESULT: 0xc0042530 (ProcessResponseHeaders, LFSession.cpp:4815)
         (LFSO/9.1.1.453)
LF.exe (9.1.1.486):
    Call Stack: (Exception)
        CLoginDialog::AttemptLogin
        CLoginDialog::LoginToServer
        CLoginView::LoginHandler
    Call Stack: (Current)
        CLoginDialog::LoginToServer
        CLoginView::LoginHandler
    Additional Details:
        Exception: 0x80042530 [9520] (No license has been allocated for this user.) (CLoginDialog::AttemptLogin at LoginDialog.cpp:794)
    Call History:
          CLoginDialog::AttemptLogin
           GetOptionString ([Settings]CheckServerVersion)
        LFFlushPrivateProfile
        CLoginView::LoginHandler
         CLoginDialog::LoginToServer
          GetOptionString ([PostroomTSOSettings]AdminNoPassword)
          CLoginDialog::AttemptLogin
           GetOptionString ([Settings]CheckServerVersion)

0 0

Replies

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

Sign in to reply to this post.