Skip to main content
Kofax

Insight's Concurrent License Model Explained

3025273

Question / Problem: 

How does Insight's concurrent license model work and how can I verify my seats are actually being used?

Answer / Solution: 

Insight’s concurrent license model permits dashboard users to run Viewer application as long as a license (“seat”) is available in the license pool. To identify exactly how many seats you have, log into Admin application and view the License tree – in this example, the environment is licensed for two concurrent seats for Viewer application:
 

2021-01-20 15_14_43-Window.jpg

A value of ‘unlimited’ means that there are no limits to how many users can access the viewer application. When a user attempts to access the viewer application when there are no available licenses, the following text is displayed:


“Current application is not available with your license. Please contact your administrator”


In addition, the following messages are logged into the WcfDataService log file:

2021-01-07 14:20:50,962 [177] ERROR AltoSoft.Insight.DataService.Code.InsightService.LicenseProvider - The maximum amount of concurrent users reached.
.
.
System.ServiceModel.FaultException`1[AltoSoft.Insight.Common.LicenseException]: Your License has been violated. (Fault Detail is equal to AltoSoft.Insight.Common.LicenseException).


To check where the concurrent seats (licenses) are assigned, open Admin application and check Admin Dashboard. The Current Sessions tab will list all sessions that are actively taking a seat. Each seat is assigned to the Session/User whose “Application” column value is “Viewer”. Only the Viewer application consumes a license.


There are situations where those sessions may not be actively used (i.e., user no longer has the viewer application open in their browser), yet still consume a license. Here are some examples and resolutions:

Example 1:

User authenticates into viewer application and views dashboard data. When done, user clicks ‘x’ button on the browser window instead of clicking the logout button on the dashboard. This causes the application session to still remain intact because a logout event hasn’t triggered a request to free the license.

To resolve this, the user can reload the dashboard and click the logout button on the dashboard or, if a logout button doesn’t exist, use the complete logout URL of the viewer application. For example: http(s)://InsightServer.company.com/Insight/view/Logout.aspx

If that doesn’t free the license (checking Admin Dashboard in Admin application), perform an IIS reset to restart Insight’s data service. 

Example 2:

User authenticates into the viewer application, however, the role assigned to the user doesn’t have a default view configured. The following message displays in the viewer:

“You can specify parameter “ViewID” in URL or just set default view in Admin Tool.”

In that case, because the authentication passed, a seat was taken but no view was displayed (no authorization). To free that license, call the logout.aspx form as discussed in Example 1 above.
 

Insight also has a feature to automatically log out users that have no activity after x minutes. For more information on that, please review KB 3025283.

 

 

Applies to:  

Product Version
Insight 6.x

 

 

  • Was this article helpful?