Release Stuck FLEXnet Licenses

by John McGehee on October 4, 2009

Software applications are supposed to release Acresso FLEXnet (formerly Macrovision FLEXlm) licenses when they exit. On rare occasion they forget.

The simplest solution is to stop and restart the lmgrd server (lmreread is insufficient). If you cannot do this, use the lmremove command to release licenses so you can use them again.

For example, Cadence SoC Encounter on Linux once failed to release its license. The next time I tried to start it, I got the message,

> velocity
Checking out Encounter license …
License checkout failed: ERROR (LMF-02018): License call failed for feature NanoRoute_Ultra, version 8.100 and quantity 1. The license server search path is defined as 5280@poser. The FLEXnet error message is as follows,
FLEXnet ERROR(-18, 0, 0): License server system does not support this feature.

This was particularly vexing because we did not even have a NanoRoute_Ultra license. Yet earlier, SoC Encounter had been working fine without it.

To release the stuck license, find the license you want to release:

> lmstat -A

License server status: 5280@poser
License file(s) on poser: /usr/local/flexlm/licenses/license.cadence:

Users of Encounter_Digital_Impl_Sys_XL: (Total of 1 license issued; Total of 1 license in use)

“Encounter_Digital_Impl_Sys_XL” v8.1, vendor: cdslmd
floating license

john poser.voom.net poser.voom.net:1.0 (v8.100) (poser/5280 574), start Sun 10/04 20:24

So, it turns out that the Encounter_Digital_Impl_Sys_XL feature is the problem, not NanoRoute_Ultra. Go figure.

Release this license using the information provided by the lmstat command (the following is a single command):

> lmremove -c /usr/local/flexlm/licenses/license.cadence Encounter_Digital_Impl_Sys_XL john poser.voom.net poser.voom.net:1.0

The FLEXnet End User Licensing Guide is very useful. Strangely, the Acresso web site is the only place you cannot get this manual. So just search the Internet for “FLEXnet End User Licensing Guide”, and take your pick.

Leave a Comment

Previous post:

Next post: