Licensing Error

[Anonymous]

I have just installed Building Design Suite Premium 2017 and I get the following message.

The License manager is not functioning or is improperly installed.

AutoCAD will shut down now.

this happens not matter which program I try to start. I have uninstalled everything once and disabled virus protection then reinstalled but still got same message.

[TravisNave]

Check to make sure the Autodesk licensing service is running under your Windows Services.  Maybe you need to manually start it?

Otherwise, try this to reset your licensing:

http://upandready.typepad.com/up_and_ready/2012/01/licensing-the-security-system-softlock-license-ma...

Good Luck!

[jeremy.h · Accepted solution]

I think this is actually a somewhat different issue than the one covered in the article Travis referenced. This is a new issue we're seeing with AutoCAD-based 2017 products. It's covered in this article:

http://knowledge.autodesk.com/article/AutoCAD-2017-fails-to-launch-after-install

The tricky part is figuring out which product key to use in the folder name. When you install a suite, you might not actually be installing vanilla AutoCAD even though it looks like you are. Some suites use a vanilla AutoCAD profile on top of one of the AutoCAD verticals. So check in Control Panel to see which version of AutoCAD is actually installed, then look at the 2017: Product keys for Autodesk products to determine which product key to use.

For example, if AutoCAD Architecture 2017 is the one that's installed, create the folder C:\ProgramData\Autodesk\CLM\LGS\185I1_2017.0.0.F. Create the LGS.data file in that folder and give it the _STANDALONE value. If you have multiple AutoCAD-based 2017 products installed, create a folder and LGS.data file for each of them just to cover all your bases.

[Anonymous]

Hi, i faced the same problem at client site Autocad 2017 these solution cant help me. Any idea to solved this problem?

[Mark.Lancaster]

@Anonymous

If the information in the LGS.DATA file is correct and the other solutions provided in that article doesn't resolve your issue, then check to make sure the FlexNet Licensing Service 64  is enabled and started under Window Services.