Autodesk Network License Manager 2019

[TravisNave]

Well, it's that time again.  Time to update your Autodesk Network License Manager files to the latest and greatest (Autodesk) version.

Autodesk is providing an updated version 11.14.1.3 for 2019 products for the first time in two releases.  It is advised that you update this and any 3rd party Flexera versions that you may be running to this release or newer. 

NOTE:  If you do not update with the 2019 release, you may get a 0.0.0 error. 

For detailed installation instructions see this link:

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/How-do...

Just like the last couple of years and moving forward, the License Manager files are no longer available for direct download from Flexera.  Per their new policy, you must obtain the license manager from your software vendor.  You can download the Autodesk Network License Manager files here for both 32-bit and 64-bit versions:

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

You can update your license file to 2019 versions from your Autodesk Accounts page once your Subscription has been updated. 

Autodesk Product Keys for all versions can also be found here.

You can use the online method to activate your license here:

https://register.autodesk.com and from the new Autodesk Accounts page at https://accounts.autodesk.com

Or you can contact your Value-Added Reseller for assistance. You can locate your VAR here:

http://www.autodesk.com/resellers/locate-a-reselle​r

To update your license file, you will need to provide your serial number and ethernet ID of the new license server.

For a Quick-Start Guide on configuring the Autodesk License Manager, please see my post for further information:

https://forums.autodesk.com/t5/installation-licensing/quick-start-guide-for-configuring-lmtools/m-p/...

Good Luck!

[chriswade]

I managed to figure out how to get the service installed, but now I get a new error when trying to start the server when running as a service:

VD is starting, please check vendor daemon's status in debug log

Here are the contents of the debug.log when running as a service:

15:16:34 (lmgrd) Forced shutdown requested
15:16:35 (lmgrd) SHUTDOWN request from cw at node LicenseServer
15:16:35 (lmgrd) lmgrd will now shut down all the vendor daemons

15:16:35 (lmgrd) Shutting down adskflex pid=644 because of signal 15
15:16:35 (adskflex) (@adskflex-SLOG@) ===============================================
15:16:35 (adskflex) (@adskflex-SLOG@) === Last 10 Client Requests Processing Time (in ms) ===
15:16:35 (adskflex) (@adskflex-SLOG@) Time: Wed Jul 18 2018 15:16:35 Pacific Daylight Time
15:16:35 (adskflex) (@adskflex-SLOG@) Request processing time, when, #concurrent clients, (private bytes (in KB)), client info (user, node, FD)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000000 ms at Wed Jul 18 2018 15:16:35 Pacific Daylight Time,#8,(3624K),(cw,LicenseServer,684)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000000 ms at Wed Jul 18 2018 15:16:13 Pacific Daylight Time,#7,(3624K),(dlee,Archistruct,748)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000000 ms at Wed Jul 18 2018 15:16:13 Pacific Daylight Time,#7,(3624K),(jbreen,12h-Server,744)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000000 ms at Wed Jul 18 2018 15:16:08 Pacific Daylight Time,#7,(3624K),(Jatienza,12h-Server,492)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000000 ms at Wed Jul 18 2018 15:16:00 Pacific Daylight Time,#7,(3624K),(Alagasca,12h-Server,736)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000000 ms at Wed Jul 18 2018 15:15:48 Pacific Daylight Time,#7,(3624K),(dsung,24h-Server,740)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000000 ms at Wed Jul 18 2018 15:15:35 Pacific Daylight Time,#8,(3624K),(SYSTEM,LicenseServer,684)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000000 ms at Wed Jul 18 2018 15:15:35 Pacific Daylight Time,#8,(3624K),(SYSTEM,LicenseServer,684)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000000 ms at Wed Jul 18 2018 15:15:35 Pacific Daylight Time,#8,(3624K),(SYSTEM,LicenseServer,684)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000000 ms at Wed Jul 18 2018 15:15:35 Pacific Daylight Time,#8,(3624K),(SYSTEM,LicenseServer,684)
15:16:35 (adskflex) (@adskflex-SLOG@) 
15:16:35 (adskflex) (@adskflex-SLOG@) === Top 10 Peak Client Requests Processing Time (in ms) ===
15:16:35 (adskflex) (@adskflex-SLOG@) Time: Wed Jul 18 2018 15:16:35 Pacific Daylight Time
15:16:35 (adskflex) (@adskflex-SLOG@) Request processing time, when, #concurrent clients, (private bytes (in KB)), client info (user, node, FD)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000016 ms at Wed Jul 18 2018 15:12:00 Pacific Daylight Time,#3,(3372K),(Alagasca,12h-Server,736)
15:16:35 (adskflex) (@adskflex-SLOG@) 00000015 ms at Wed Jul 18 2018 15:12:33 Pacific Daylight Time,#7,(3540K),(SYSTEM,LicenseServer,752)
15:16:35 (adskflex) (@adskflex-SLOG@) 
15:16:35 (adskflex) (@adskflex-SLOG@) === Top 10 Peak In-house Operations time (in ms) ===
15:16:35 (adskflex) (@adskflex-SLOG@) NOTE: Peak times greater than 4 seconds get recorded.
15:16:35 (adskflex) (@adskflex-SLOG@) Time: Wed Jul 18 2018 15:16:35 Pacific Daylight Time
15:16:35 (adskflex) (@adskflex-SLOG@) In-house operation time, when, #concurrent clients
15:16:35 (adskflex) (@adskflex-SLOG@) 
15:16:35 (adskflex) (@adskflex-SLOG@) === Active Connections Info ===
15:16:35 (adskflex) (@adskflex-SLOG@) Peak active connections #8 attempted at Wed Jul 18 2018 15:15:35 Pacific Daylight Time
15:16:35 (adskflex) (@adskflex-SLOG@) 
15:16:35 (adskflex) (@adskflex-SLOG@) === Memory Usage Info ===
15:16:35 (adskflex) (@adskflex-SLOG@) Peak private bytes 3624K attempted at Wed Jul 18 2018 15:15:08 Pacific Daylight Time
15:16:35 (adskflex) (@adskflex-SLOG@) ===============================================
15:16:35 (adskflex) Shutdown requested.
15:16:35 (adskflex) daemon shutdown requested - shutting down
15:16:35 (adskflex) IN: "64300ACD_F" Alagasca@12h-Server  (SHUTDOWN)
15:16:35 (adskflex) IN: "64300ACD_F" jbreen@12h-Server  (SHUTDOWN)
15:16:35 (adskflex) IN: "64300ACD_F" dsung@24h-Server  (SHUTDOWN)
15:16:35 (adskflex) IN: "64300ACD_F" Jatienza@12h-Server  (SHUTDOWN)
15:16:35 (adskflex) IN: "85797BDSS_F" dlee@Archistruct  (SHUTDOWN)
15:16:35 (adskflex) IN: "87143BDSS_2019_0F" dlee@Archistruct  (SHUTDOWN)
15:16:35 (adskflex) IN: "87084ACD_2019_0F" Alagasca@12h-Server  (SHUTDOWN)
15:16:35 (adskflex) IN: "87084ACD_2019_0F" jbreen@12h-Server  (SHUTDOWN)
15:16:35 (adskflex) IN: "86830ACD_2018_0F" dsung@24h-Server  (SHUTDOWN)
15:16:35 (adskflex) IN: "86830ACD_2018_0F" Jatienza@12h-Server  (SHUTDOWN)
15:16:35 (lmgrd) Shut down FlexNet adskflex license server system on machine LicenseServer
15:16:35 (lmgrd) EXITING DUE TO SIGNAL 15

[TravisNave]

Looks to me as if the shutdown was requested by cw on the LicenseServer. 

(lmgrd) SHUTDOWN request from cw at node LicenseServer

[chriswade · Accepted solution]

That was so that I could stop the server manager and start the service.

As it turned out when the License Manager created the service, it tied it to my account and you have to modify the service to use the local account.

This is apparently a known issue in the latest version of LMTOOLS.

Additionally, there is now a third box that needs to remain unchecked

I think it is important that this gets documented so someone else who may be having the same issues doesn't have to go through everything that I did.

[chriswade]

Apparently with this error the service doesn't even show up in the debug log before failing.

[TravisNave]

Yes, I had made note of it in my most recent KB about the NLM errors.  The service is not created by LocalSystem anymore, which causes a plethora of problems.  The best practice is probably just making it a System process by default, honestly.  Thanks for the thorough follow-up!

[chriswade]

I have done a search about local account and the only reference I can find is one reseller who appears to be from the UK has it in their knowledgebase online. So if your KB is public, it is not easily findable in Google, just a heads up.

[TravisNave]

Thanks.  I just wrote it the other day.  It probably hasn't been crawled yet.  But being in this thread will help that situation for the next person. 

[chriswade]

Ah, that would explain it, but still annoying that this happens. It would be really nice if Autodesk would upgrade its licensing system, I know it would be a pain for a little while until older products are phased out unless they issued hotfixes that would connect to a new licensing system, but it would be nice to say have the option of connecting to a licensing server or to the internet instead and use a web based licensing server that Autodesk provides basically.

[Anonymous]

Hi Travis,

How you did that? my Autocad 2019 shows an (0:0:0) error using LMTools version 11.7

I'll apreciate if you can give me a hand on this.

Autocad 2010 works fine.

[Anonymous]

I'm needing to upgrade a few Linux Triad Redundant server configurations to 11.14.1.3 to support new AutoCAD 2019 licenses but have found that the Linux installation is only for 64 bit, as far as I can find. my company is still running RHEL 5.11 on the Triad servers , we currently are running 11.14.1.2. but know we need to upgrade to be able to use AutoCAD 2019 licenses.

Any guidance is appreciated. 

Jason

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

[RichardBianco2782]

My 2019 versions of Building Design Suite & Infrastructure Design Suite are not finding a license. Earlier versions do get a license from my server running version 11.12

I about to upgrade the server but am concerned if the older versions will continue to work?

[Mark.Lancaster]

@RichardBianco2782

All Autodesk 2019 product line requires the Autodesk License Manager to be at version 11.14.1.3.  If you currently don't have that, then you can't obtain 2019 release from the license.   The new license manager works with all Autodesk versions.

[TravisNave · Accepted solution]

The NLM is backwards compatible. For 2019 to work, you need to ensure that
the latest adskflex.exe is being used and the old one is not running. A
status enquiry will tell you the version of adskflex vendor daemon.
Likewise, the old 11.7 still works for everything. It's magical. 🙂

[RichardBianco2782]

Thanks Mark. I upgraded and my 2019 & 2018 products are working. I can't find the "Accept as Solution" button

[RichardBianco2782]

When your post of 11.7 ws working with 2019 products I was expecting 11.12 to work also and it doesn't.

[StephenThomasGrace]

Again!

Any time I have issues with my ADLM it seems I can ALWAYS figure out some kind of solution after checking your posts, Travis!

I was not able to get AutoCAD 2019 to run off the 11.7, as you suggested, on my old Windows 2008 server (not R2), but...

I was able to install the latest version 11.16 on a Windows 10 (x86) and then copy the files over to the Server 2008.

Even though it is "Not Supported" by autodesk, it works!

That'll tide me over until long overdue server upgrade happens.

Many thanks.

-steve

[TravisNave]

Haha!  Always glad to help.  I'll have my 2020 Update out soon.  And I'll probably be making an update to the License Administrator web-based NLM too at some point.  I had some hits and misses with 11.7 on 2019 as well, which was the first time I'd ever seen it not work.  I look forward to testing it with the 2020 release and seeing how its compatibility works.  From a purely technical standpoint, the only file that really matters is the adskflex.exe in terms of whether or not the Autodesk software will work.  The LMGRD itself is compatible all the way back to at least 9.2!

[StephenThomasGrace]

Awesome, Another very interesting nugget of information.

I'll be looking forward to your update!

-steve