Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
May 20, 2021 5:13:13 AM
Nov 5, 2019 8:42:57 AM
The maximum number of parallel user connections for a single user in Qlik Sense is five (5). This can be exceeded by users by accident or by unexpected behavior.
The related log file for this issue is:
C:\Programdata\Qlik\Sense\Log\Repository\Audit\AuditSecurity_Repository.txt
The related message reads:
Access was denied for User: 'Domain\USER', with AccessID '264ff070-6306-4f1b-85db-21a8468939b5', SessionID: 'e3cd957b-a501-4bec-a3f8-d35170a73efa', SessionCount: '5', Hostname: '::1', OperationType: 'UsageDenied'
See How to count sessions in Qlik Sense on possible scenarios on when multiple sessions are created.
When the user is consuming too many sessions, they will need to wait until the first one has correctly timed out. This is dependent on the Qlik Sense configuration.
If none of those apply, and a user is not actively connecting more than 5 times, then the below should be investigated:
In some instances, the error message may wrongfully be shown when no license/token was assigned to a user. Note that this should not be the case with the service account, as mentioned above.
iOS does not allow cookies from websites in iFrames without having first visited the embedded site directly.
To resolve this, access the site hosting the iFrame once. After that, cookies can be accepted.
In the following scenarios, the client device is disconnected from Qlik Sense during an active session:
When the session is resumed, all request sent to server contain the previous session cookie, which has expired during the disconnection. The requests with invalid session cookie leads to re-authentication for multiple requests, which leads to session count being rapidly exhausted.
This issue has been addressed and resolved in below releases, where Release Notes on "Handle 'invalid cookie' bursts in the Qlik Sense proxy Service" for additional configuration details.
Verify if any of the following tables in the Qlik Sense Repository Database (QSR) includes 5 or more records for the user that are older than 5 minutes:
If that is the case, the maintenance/cleanup of old sessions might not be working properly.
This issue has been addressed and resolved in the below releases.
I am having 4 environments each with Qlik Sense Sep 2019 Sr 5 installed.
3 of them are working fine with the service account as well but only one of them always shows error of
"You cannot access Qlik Sense because you have too many sessions active in parallel."
IF the issue is resolved I dont understand why its appearing. Is there anything which I can do to get it resolved.
SecondlyI received these errors on same server for some users who even were not service accounts.
It Happens only on Chrome with Qlik Sense November Patch 5. We're investigating right now to find a fix/workaround without upgrading Qlik Sense (it is not possible)..
FM
Just had a case (on 2019 Nov SR5) were the user error was "too many sessions ..." but the problem was no token assigned to the user (yes, still using tokens in that case).
Hi John,
Your issue is resolved? if so, how. we are facing the similar issue with only new users to who we assigned newly. old users are working fine.
the version we are using is Nov 2019 and 13.51.4
we have changed our licensing model to latest one after this upgrade.
It was resolved by assigning a license to the user in that case.
But, as the article states, there are other causes for the error.
User already assigned a license, still getting the error in the front end, but there is no error in the audit security log.
My suggestion would be to open a ticket with Qlik Support to investigate.
Thanks John,
Already raise d case with Qlik support, you might be knowing their response is pathetic!!.
Looks/feels to me like Qlik Support is *slightly* understaffed, overworked and maybe under-qualified ... sometimes ... .
I hope this situation will be addressed and improved.
This situation is obviously not the fault of the people working in Qlik Support!
@nizarch13 I believe I found your case in our system and am seeing what we can do to review this for you - as well to ensure the findings are documented afterwards.