How to force Code Warrior to release a floating licence?

[PaulWalker]

Hi,

We are using Code Warrior Basic for Power Architecture version 10.3.3 with a single floating licence. The licence server is remote; managed by our IT people.

After we use the flash programming tool, the floating licence often becomes locked to the specific user/PC that performed it. We have tried adding a timeout of 15 minutes (900 seconds) to the server licence - but it still seems to become locked for lengthy periods (mulitple hours or forever).

Is there any way to force a release of a floating licence, i.e. from the client end of the originating PC or similar?

[ZhangJennie]

hi PaulWalker.

from your description, you use floating license. correct?

normally once you close CW/programming tool application in client, the license can be released.  if it is not released, can you please check windows target manager if the processes are still running?

=================================================

this answer is for you, if it helps, please click on "correct answer" button. thanks!

Best Regards,

ZhangJun

[PaulWalker]

Hi,

I've checked windows task manager - nothing interesting to report. No unusual processes are still running. We have even tried re-booting the relevant PC.

We have noticed the licence is normally acquired when the flash programming tool is actually run (or other licensed feature), and released when the flash programming operation is completed. However we have noted sometimes the release does not occur, and despite repeating the flash programming operation, the license remains acquired.

Any help greatly appreciated.

Regards,

Paul

[PaulWalker]

Managed to mostly reproduce problem on demand.

Start CWIDE,

Disconnect the TAP.

Start flash programmer and allow to fail.

Close CWIDE.

Inspect the floating licence via flexlm (lmstat -a -c port@server). You should find the floating licence is still assigned to the user that initiated the flash programmer.

[lunminliang]

Hi,

This is related to 3^rd party problem (Flexnet). We have this logged internally, and remains until FlexNet upgrade.