Hi and welcome to Qlik Fix! This video covers the scenarios in which the "too many sessions active in parallel" error message is expected to occur, and how to prevent it. Starting on the June 2019 release of Qlik Sense, the error message displayed here became a common occurrence. Prior to the June 2019 release and since April 2018 when Professional and Analyzer licensing model was released, the error message indicating "you have no access pass" was expected to be displayed instead, which was misdleading. The issue is due to the maximum allowed five authentication sessions that can be active at any time in Qlik Sense. See Access Assignment in Qlik Help site. (https://help.qlik.com/en-US/sense-admin/November2020/Subsystems/DeployAdministerQSE/Content/Sense_De...) The maximum of five allowed sessions applies to authenticated licensed users, so after opening multiple authentication sessions from different browsers or computers, we see the error message displayed to the client after attempting to open the sixth session. In this storage location we can review the Qlik Sense repository audit security logs which will have lines registered indicating that the SessionCount has reached a value of five, so it logs UsageDenied in reference to this issue. Note that different tabs on the same browser normally use the same authentication session and do not lead to the same issue. This issue is more commonly observed when an administrator uses the Qlik Sense service account to manage and develop Apps via the Hub. This occurs because the service account has been assigned a professional or analyzer license, and the number of sessions limit is imposed not just for client connections, but also internal system connections to the Qlik Sense Proxy API, such as for Monitoring app reload tasks, which use the service account by default. In order to prevent this issue, administrators should not use the service account for developing and managing apps via the Qlik Sense hub. Instead, use another licensed account, and do not allocate a license to the Qlik Sense service account. If the issue is reported with a regular user account, make sure the maximum number of sessions is not being reached for the user. For more information on how to count the number of sessions, see the knowledge base article "How to count sessions in Qlik Sense". (https://community.qlik.com/t5/Support-Knowledge-Base/How-to-count-sessions-in-Qlik-Sense/ta-p/171420...) Note that when allocating the legacy User Access Pass to the service account, this issue may also delay or prevent Monitoring app reload tasks from being performed successfully. This happens because the Qlik Sense service account is used to create sessions with the Qlik Sense Proxy API during the reload. In order to prevent reload task issues, the recommendation is again to leave the Qlik Sense service account as a RootAdmin, without any license allocated to it. An alternative would be to use another RootAdmin for the monitoring apps Data Connections that is not used in App development, and has no license allocated. If you’d like more information, search for answers using the unified search tool on the Support Portal. It searches across the support knowledge base, Qlik Community, Qlik Help site, and Qlik YouTube channels. Take advantage of the expertise of peers, product experts, and technical support engineers by asking a question in a Qlik Product Forum on Qlik Community. And don’t forget to subscribe to the Support Updates Blog. Thanks for watching!
Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.