Question

9520 error

Updated August 5, 2014

asked on August 5, 2014

I am getting a 9520 error. "no license has been allocated for this user. (9520) for a user. I can open the client and the repository on a different workstation. What would cause this error on some workstations and not others? I have test account I am working with. I do have a new user with what appears to be the same issue. The AD account is definitely listed in the License Manager. This is a RIO installation.

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

Call Stack: (Current)

CLoginDialog::LoginToServer

Additional Details:

Exception: 0x80042530 [9520] (No license has been allocated for this user.) (CLoginDialog::AttemptLogin at LoginDialog.cpp:794)

Call History:

CLoginDialog::LoginToServer

GetOptionString ([DR10Settings]AdminNoPassword)

GetOptionString ([DR10Settings]UserName)

GetOptionString ([Settings]UseWindowsAuth)

GetOptionString ([DR10Settings]UseWindowsAuth)

CLoginDialog::AttemptLogin

GetOptionString ([Settings]CheckServerVersion)

0 0

Answer

SELECTED ANSWER

replied on August 5, 2014

To confirm, you are logging into the repository using Windows Authentication, but for some accounts (test account and/or new account) it returns the 9520 error?

You've confirmed that the account(s) being used are listed under the "Named Users and Devices" node in the License Manager Administration Console. However, can you also check in the Laserfiche Administration Console, under the "Windows Accounts" node, that the account is listed there as well and under the "Named User" column, it has the value, "Full"?

If the account isn't listed under the "Windows Accounts" node, try adding it manually and give it "Trust: allow access." If the account is now listed but under the "Named User" column, it has the value, "False" then try restarting the Laserfiche Server service.

Close and reopen the Laserfiche Administration Console and check the "Named User" status of that windows account again. If it is still listed as "False" then please stop the Laserfiche Server service, go into C:\Program Files\Laserfiche\Server, backup the lfsnu.db file and then remove it from that directory, and finally restart the Laserfiche Server service. One caveat is that you would need to configure any repository named users you had. However, the directory named users should be fine.

If there is still a problem after performing the above steps, then please contact your Laserfiche reseller to open a support case.

0 0

Replies

replied on August 5, 2014

I will check the issues. but yes, we are using Window Authentication. We do not list the users accounts individually in the Admin Console. the users are members of groups that are listed and assigned rights in Windows Accounts in the Admin Console.

The weird issue is that the test accounts can open the repository without issues on some machines. this seems to be workstation specific. However, the problem machines can open a repository for me.

0 0

replied on August 5, 2014

Adding the windows account manually under the Windows Accounts node in the Laserfiche Administration Console is for troubleshooting purposes, to confirm that the Laserfiche Server properly detects that windows account as having been assigned a named user license.

In any case, sticking with just the single test account, are you saying that you can log into Windows on one PC using that test account and then log into the repository successfully using Windows Authentication, however, when logging into Windows on a second PC using that same test account, then trying to log into the same repository using Windows Authentication will then give a 9520 error?

0 0

replied on August 5, 2014

that is correct. same account, 2 workstations. One workstation opens the repository the other doesn't. I am testing on 2 of the same machines.

0 0

replied on August 5, 2014

Is the test account you used listed as "Full" or "False" under the Named User column in the Windows Accounts node in the Laserfiche Administration Console?

0 0

replied on August 5, 2014

Some users are listed in the Windows Accounts, some are not. Some of the listed users are marked false under the Name User column, while are marked True.

0 0

replied on August 5, 2014

For the windows accounts who are listed as "False" under the Named User column, but are listed in the License Manager Administration Console under the Named Users and Devices node, then please follow the steps mentioned a few posts earlier about restarting the Laserfiche Server service and/or stopping the Laserfiche Server service, removing the lfsnu.db file (after backing it up first) and then restarting the service.

0 0

replied on August 5, 2014

I have a lot of other users in repositories right now. I will need to notify them of an outage this afternoon. I don't want to just kick them off with a service restart

0 0

replied on August 5, 2014

the workstation the works has the 9.0 client.

the workstation that doesn't work has 9.1.

0 0

View 3 previous replies

replied on August 5, 2014

Is the test account you used listed as "Full" or "False" under the Named User column in the Windows Accounts node in the Laserfiche Administration Console?

0 0

replied on August 5, 2014

false

0 0

replied on August 5, 2014

I would expect them to be true. but that doesn't explain why the test user can open the repository on one machine and not the other. I removed 9.1 and installed 9.03 on a 3rd workstation. it did not improve anything.

0 0

replied on August 5, 2014

So since that account isn't seen as having a named user license assigned, that may explain what you're seeing. The 9.0 vs 9.1 Client isn't a factor.

The suggestions listed above should correct the matter, however, if they do not, then please contact your reseller to open a support case so we can investigate further.

As for explaining why this may occur in the first place, adding new named users in the License Manager will send out a notification to any Laserfiche Server (that has subscribed to notifications from the License Manager) using UDP. So in some cases the Laserfiche Server may not be aware that a new windows account has been granted a named user license. Restarting the Laserfiche Server service forces the server to connect to the License Manager to get the updated list of named users. In some cases, a bad lfsnu.db file may prevent that from occurring properly so sometimes deleting that file may be necessary as well before restarting the Laserfiche Server service.

0 0

replied on August 5, 2014

I have notified my users of a service restart at 1:15. Thanks for the support. I will go eat so I am fresh and follow the instructions above

0 0

replied on August 5, 2014

The steps above fixed the problem. thanks!

0 0

You are not allowed to follow up in this post.

Question

Question

9520 error

Answer

Replies

Sign in to reply to this post.