Sometimes we encountered a problem when we tried to connect to our integrity server. A popup come up with the following message : "MKS124788 : You require an Integrity Client license with workflow and document capabilities".
Restarting the server solves the problem, but this it always reappear (several times a day).
Any help would be greatly appreciated. Thanks.
It means you have no more licenses available for use, you can see who has the licenses by going to Client Administration view, Server Diagnostics, License Usage.
You can use the Disconnect User to drop users off the system and free up the licenses
You can also set the properties file to auto log the users off after a certain period of time. The option to set the time out is described in the Integrity Adminstration Guide.
Hi Joe and Nicolas,
We have had our own lessons learned about the way the licenses work.
Disconnect User will only free up a license if you are using "float" licenses. If you have "seat" licenses, the only way to free those up is to restart the integrity server after changing the license group membership.
There are also some settings in the Admininstrator client (Workflows and Documents->Configuration->Properties) or (Configuration Management->Configuration->Properties) and server config files (/config/properties/is.properties) for setting timeouts, such as the "mksis.im.httpSessionTimeout", "mksis.si.httpSessionTimeout", and "mksis.idleDisconnectTimeout". These settings can be used to have the system automatically disconnect users that are connected to the server but not performing any actions (i.e. the users wasting a float license).
For more information, please look at the knowledgebase article here:
If there is something else going on with your licenses (such as licenses being denied when you have spares), I would recommend you to open a case with the support team so that they can troubleshoot the issue further.
Hope that helps,
Thank you both for your answers.
We will try to use the Administration View to disconnect user the next time the problem occurs.
If it's works we will change the differents timeout session parameters.