Question

Unable to log in to admin console error 9030

Version 8 Laserfiche Administration

Updated August 15, 2014

asked on August 7, 2014

I have a client that is unable to log into the Admin Console. They are receiving the following error: The maximum number of sessions that this server instance is licensed for has been reached. [9030]

I’m guessing that the limit on simultaneous connects for the ADMIN account has been reached. Thoughts on getting around that limitation?

0 0

Replies

replied on August 7, 2014

You can go into the "All Sessions" node of the Laserfiche Administration Console (note that you don't need to log into any particular repository) and disconnect the other ADMIN sessions that shouldn't be in use.

As for actually trying to get around this limit, meaning, they have a Rio or Avante system and want more than two concurrent non named user sessions, that isn't possible.

0 0

replied on August 8, 2014

Trying to disconnect the Admin user through sessions was not successful. There was an error: Invalid session. [9037].

0 0

replied on August 8, 2014

Could there have been a network related issue occurring or perhaps an issue where Laserfiche couldn't communicate with SQL for a period?

If you restart the Laserfiche Server service, is there still an issue?

0 0

replied on August 8, 2014

Hi Mick,

Just listing another option expanding on Alexanders comments.

There is also the option to buy a user license and make Admin a named user (if you have lots of users that for some reason need to access the admin account). Costs money yes, but it will increase this limit (to 5 I think). Another option

Cheers!

0 0

replied on August 15, 2014

Hi Mick,

If your question has been answered, please let us know by clicking the "This answered my question" button on the response.

If you still need assistance with this matter, just update this thread. Thanks!

0 0

You are not allowed to follow up in this post.

Question

Question

Unable to log in to admin console error 9030

Replies

Sign in to reply to this post.