Why can't I get a license?

In this topic:
Linger times User names are case-sensitive Stuck licenses

If you see a message similar to "No license available," this means that you need to wait until a license is returned by another process or user. Even if another user has stopped using a license, two factors control how long you need to wait before the license is available for you to check out:

Inactivity time-out: Some tools keep a license checked out during a period of inactivity:
- Validate - 30 minutes
- Klocwork Code Review - 30 minutes
- Klocwork Desktop Java Plug-in for Eclipse - 20 minutes
- Klocwork Desktop Java Plug-in for IntelliJ IDEA - 20 minutes
- Klocwork Desktop C# Plug-in for Visual Studio - 20 minutes
For more information, see How licensing works.

Linger period: The amount of time after the last use of a license before it is free for another user to check out.

Linger times

Linger time is the amount of time after the last use of a license before it is free for another user or command to check it out. Note that Klocwork starts counting the linger times at the end of the inactivity time-outs that some Klocwork components have. When a license is returned after the time-out expires, the license is not available until the linger period expires.

Build licenses are used to run the Klocwork integration build analysis on a build server. Build licenses are always node-locked to a host name, or "fixed". A fixed build license has a long linger period of two weeks (1,209,600 seconds).
User licenses are used by everyone who uses Klocwork tools. A user license has a shorter linger time, generally a 7 day (604,800 second) linger.
The linger time for the kwstruct101 command is 14 days (1,209,600 seconds). The linger time for Structure101 Studio (kws101client license) or Structure101 Build (kws101build license) is 7 days (604,800 seconds). "Linger" is the amount of time after the last use of a license before it is free for another user to check out.
Web service licenses have no linger time.
Concurrent licenses (build agent licenses and CI agent licenses) have no linger time and are available for use as soon as the process or command using the license finishes and returns the license.

User names are case-sensitive

If the Klocwork Server is running on a Windows machine, users who log in to Validate and Klocwork Code Review have a license checked out using the lowercase form of their user name. Other tools will not change the case of the user name (obtained from the OS), so a second license is checked out. Workaround: Use a lowercase user name.

If the Klocwork Server is running on a non-Windows machine, users who log in to Validate and Klocwork Code Review have a license checked out using the case as entered in the Login dialog. As above, other Validate tools use the user name as obtained from the OS. Workaround: Match the user name case used by your OS.

Stuck licenses

Note that if a Klocwork tool terminated unexpectedly, the license may be "stuck", in which case an administrator must release it. See Releasing stuck licenses.