LMGRD.EXE Using 99% CPU usage

[Chad Smith]

I upgraded our network license of AutoCAD 2008 to AutoCAD Revit Architecture Suite 2008 on our server the other week, but at that stage I didn't reboot it.

Today, the server was rebooted, and for some reason the license manager, in particular the LMGRD.EXE service is taking all the CPU cycles, meaning the server can't process other programs.
I have tried uninstalling it, then reinstalling, and removing all redundant licenses, with no success.

Anyone have any suggestions which I might try?

[Elmo]

LM Tools is a product that was created by Macrovision and used by Autodesk for the management of the license. I would suggest trying to get a hold of them rather because they can assist you better with their product. Here is their website.

http://www.macrovision.com

[bbeck]

Wish I had an easy answer for you Chad. I've never seen our LMGRD.EXE take up any CPU time. I'm guessing you've started, stopped, restarted, re-read license, etc.....multiple times in an effort to clear this up. What's your status today?

[Chad Smith]

The problem has been resolved with help from Autodesk support.

Please find the following Technical Solution TS1054983 - Network License Manager license file path length limitation

http://usa.autodesk.com/adsk/servlet...linkID=9240617


If the license file path is 107 characters or more, an LMTOOLS Status Enquiry will include the following error:

FLEXnet Licensing error:-16,287

The debug log file will include the following line:

(adskflex) Vendor daemon can't talk to lmgrd (Cannot read data from license server system. (-16,287))

The length of the license file name or path should be reduced to allow the Network License Manager to function correctly.

Note: This limitation has only been tested with FLEXlm® 10.1.5 and 10.8.

[Elmo]

That will be handy to remember.

Note to self - don't go over board on naming the license file.

[Chad Smith]

In my case, it was the path which was the issue. "AutoCAD Revit Architecture Suite 2008" was a bit long .

[Elmo]

Ahh! I understand. I normally just go Revit 2008 Deploy. It's much easier for me like that.