2017 Network License not working

[Anonymous]

Hope this is the correct forum, but I'm having an issue activating an add on for AutoCAD 2017 via a network license. The add on is Point Layout 2017, and from what I can tell everything is set up correctly. I have my LMTOOLS server up and running, and the license file is loaded -- or rather, I replaced my 2016 license file with the 2017 file.

With my 2016 programs, I actually had to use an Enviornment Variable of "ADSKFLEX_LICENSE_FILE" directed at  "@Benjamin-PC" for it to dectect the server and load the file, but with AutoCAD 2017 that doesn't seem to be possible. Instead when I click on the "Get License" button I'm taken to AutoDesk's new license select screen. Here I'm able to select "Network" and enter the Server Name (which is still Benjamin-PC), but it doesn't work. Instead, after entering it, a pop up with an error message comes onto the screen, and I'm unable to obtain a license. (See attached image for the error.)

The thing is, I know for a fact that my server is still running, and I know that the license file is correct. I'm able to use the 2017 license in 2016 (and older) programs just fine, it's just I cannot get it to activate with this new interface (which does not use Enviornment Variables). Is there anyway to fix this? I have tried nearly everything I can think of (including removing the add on from older programs, and including the port number when entering the server's name), and I also ran a check on the server to confirm that the license wasn't in use by some other program somewhere -- which it wasn't.

Thanks,

[Otto]

Hello Benjaminkb91 and welcome to the Autodesk community!

It looks like you are unable to obtain a license from the server. The following article(s) should help you resolve the problem:

Can't obtain a license from the server

How to specify license servers using the ADSKFLEX_LICENSE_FILE environment variable

Troubleshooting FLEXnet Licensing Errors

If this information was helpful, please consider marking it as an Accepted Solution by clicking on the "Accept as Solution" link, below. Taking a moment to do this will help others with similar questions find useful answers. Thank you!

Kudos (click on the link or the "thumbs-up!" icon), are also gratefully received! (Even a bot likes praise.)

If this answer missed the mark, please let us know so that other community members can lend a hand. Any additional details might help, too: consider including relevant screenshots, log files, error messages, or system specs.

[Anonymous]

I should mention that I've tried the solutions the HelpBot posted before I made this thread. Sadly nothing there helped me...

[Darin.Green]

0,0,0 means the license file doesn't have that license listed. Make sure your license manager is point to the right license file that includes 2017 products.

[Anonymous]

I can confirm it is pointed at the correct file. As I mentioned I can use the 2017 license file to open the program in AutoCAD 2016 (the license is backwards compatible with earlier programs).

Below is my server status if that would help. (Note: Only the 2017 license file is loaded in the server, but as it works with previous versions of the program, previous years are listed as well.)

--------
Status
--------
Flexible License Manager status on Thu 4/21/2016 16:09

[Detecting lmgrd processes...]
License server status: 27000@Benjamin-PC
    License file(s) on Benjamin-PC: C:\Program Files\Autodesk Network License Manager\License Files\Bens_Autodesk_Point_Layout_(2017).lic:

Benjamin-PC: license server UP (MASTER) v11.12.1

Vendor daemon status (on Benjamin-PC):

  adskflex: UP v11.12.1
Feature usage info:

Users of 86385PNTLAY_F:  (Total of 1 license issued;  Total of 0 licenses in use)

Users of 86725PNTLAY_2017_0F:  (Total of 1 license issued;  Total of 0 licenses in use)

Users of 86535PNTLAY_2016_0F:  (Total of 1 license issued;  Total of 0 licenses in use)

Users of 86384PNTLAY_2015_0F:  (Total of 1 license issued;  Total of 0 licenses in use)

Users of 86298PNTLAY_2014_0F:  (Total of 1 license issued;  Total of 0 licenses in use)

[Darin.Green]

Also, for the server name field do not put 2080@servername because the ADSKFLEX daemon uses that port not LMGRD. 

Within your license, you can specify a single port between 27000 - 27009 for LMGRD to use. Then for the server name field you would have something like 27005@servername for example.

[Darin.Green · Accepted solution]

You need to update the license manager utility to a newer version...

https://knowledge.autodesk.com/search-result/caas/downloads/content/autodesk-network-license-manager...

[Anonymous]

---

@Anonymous wrote:

Also, for the server name field do not put 2080@servername because the ADSKFLEX daemon uses that port not LMGRD. 

Within your license, you can specify a single port between 27000 - 27009 for LMGRD to use. Then for the server name field you would have something like 27005@servername for example.

---

I've actually tried this as well. The 2080 port was just an example of how I was typing it in. It's actually set to "27000@Benjamin-PC"

[Anonymous]

Great, thanks for the help! If there is any other issue I'll be back. Thanks

[Darin.Green]

You're welcome!

[Anonymous]

if u dont mind to share with me, how u settle your network license problem? 

[Mark.Lancaster]

@Anonymous

I assume you are referring to a 2017 license issue, is that correct?

So my first question is, did you upgrade your license manager to 11.13.1.2 version.  It is required for the 2017 version.

If you did upgrade and still have an issue that you need to provide us with details of what's going on.

[Anonymous]

@Mark.Lancaster 

Yes I am. I already upgrade my license manager to 11.13.version but still got license error (-96.7.11004). Later on, got another problem error with Autodesk another version( License was not obtain, error 20). Here, I provide a few reference to get some idea to settle this problem. 

[Anonymous]

Its okay mark, problem solve by my own. thank you for your time. 

[Anonymous]

Be sure to restart the computer with the licence server after you update. It does not prompt you to do so. Doing this final step solved the issue for me.

Thanks!