Your client license was released due to inactivity and a license could not be acquired ...

[Tom_Barnes]

We have one user that repeatedly gets the following pop up about the license being released due to inactivity. (It has happened to others but disconnecting them seemed to fix it)

We only use named licenses so I do not understand why this would be happening. It started after updating our license certificate. Then changing some of the users from Workflow to Workflow/Workview combined named users. We are using v 20.3.19.1000.

[Alan_Boucher]

Hi @Tom,

This appears to be an incorrect error message.  Take a look at this case that resembles yours and the resolution:

Named User Clients receiving licensing error

Description
Error message appearing: "Your client license was released due to inactivity and a license could not be acquired because all licenses are currently in use. You may still continue working.

Note: An attempt will be made to access a free license periodically and this message will reappear until a license can be acquired. Please notify your system administrator that your organization may need additional client licenses."

This error is incorrect.
The Named User Client licenses still had two available even with impacted user still visible in licensing list.
Can you please confirm how this occurs when the system has available licenses to assign?

Resolution
Disabled “Remove Expired Session Information” from Unity Scheduler.

Refer to System Tasks in the Unity Scheduler MRG.

I hope this helps!

~Alan

[Tom_Barnes]

Thank you. I'll try that and see if it works. 

[Michael_Lerch]

@Alan Boucher  @Tom  Did that work? Having a similar issue with Named license users getting timed out all the time now that I put user group timeout a lot lower to help with concurrent licenses. I believe this shouldn't apply to Named licensed users, but it is... wondering if this is related.

[Michael_Lerch]

I'm on a similar version  v20.3.20.1000.

[Tom_Barnes]

Sorry for the delayed response. I am not aware of this error coming back up after I made the change but we also just upgraded to 22.1 so I'm not positive which solved the problem. 

[Michael_Lerch]

Thanks @Tom  my first line of support said 22.1 should fix it. Until then I think I figured out a work around. I created a user group that has a really high timeout of 960 minutes (if they're working longer than 16 hours I guess they'll tell me haha!) and then added all the named users to that group. Our timeouts are by least restrictive. This seems to have fixed the problem until we can go to 22.1.