LMTOOLS fail to set DACL on new service

[Anonymous]

I have downloaded and installed the latest edition v11.13.1.2 Build 173302 x64_n6 on 3 brand new servers running Window 2012 R2. Installed using default suggested path and then started LMTOOLS to create a new service. When i am finished i click "Save Service" and get an error message.

---------------------------
Updating DACL Failed
---------------------------
Service has been created but failed to update the DACL settings of FlexNet Licensing Service. It will give problem for accessing TS features. Check whether FlexNet Licensing Service is correctly installed or not and delete and create this service again
---------------------------
OK  
---------------------------

There is no info in Event log or in LMTOOL log that can assist me in this matter.

I am loggen on as Administrator and have all rights.

[Mark.Lancaster]

I had that problem the other day and my buddy @Darin.Green fixed it...

He modified the server license file and used the ip address instead of the server name.  Also a port was added at the end of that line too.

Something like this: SERVER <HOSTNAME IP ADDRESS> <HOSTID MAC ADDRESS> <ALTERNATE PORT NUMBER>

I don't remember what port he used but @Darin.Green will chime in and give you the answer..


[Anonymous]

Thank you. The problem i describe is related to setting DACL on a new Service. I did test it though doing as suggested but with same ressult.

From https://msdn.microsoft.com/en-us/library/windows/desktop/ms721573(v=vs.85).aspx#_security_discretion... (read 5 april 2016): (DACL) An access control list that is controlled by the owner of an object and that specifies the access particular users or groups can have to the object. This is new and introduced by the new version of LMTOOLS where they have combined IPv4 and IPv6.  

[Darin.Green · Accepted solution]

You have to down grade your version of LMTOOLs to the previous version to get it working. This may have been the key factor when working with @Mark.Lancaster.

I've attached the previous version for your use.

[jeff.lotan]

I've seen this problem several time and have resolved it by clicking Save again to save the service. It does not happen all the time nor on all machine, it's system specific.

It also happened on one of our servers, but not the other. So try clicking Save again (I'd wait a few seconds between saves), then go to the Start/Stop/Reread tab and start the sevice.  Hopefully it wasn't running when you configured the service or you'll have other problems.

Have a great day!

Jeff Lotan
Solution Center Sr. Technical Support Specialist
North America Solution Center
IMAGINiT Technologies
T: 888.528.4765

[Anonymous]

Yes i agree, i have tested on several servers and its the same there. Do you have the installation? I can replace the files but it would be super with an installation if anyone have one laying around 🙂

[Darin.Green · Accepted solution]

Here's the actual download:

https://knowledge.autodesk.com/sites/default/files/file_downloads/nlm11.12.1.4_ipv6_Win64.exe

[scott_baker · Accepted solution]

This warning dialog does not affect NLM because we don't use Trusted Storage (TS) in network license, both server and client sides.  It can be ignored without having to downgrade.

[Anonymous]

Hello,

i have the same problem on a Server 2008R2.

When I don't update the server the 2017 products don't get a network license. In this case the log of the license server says:

17:07:14 (adskflex) Request denied: Client (11.13) newer than Vendor Daemon (11.12). (Version of vendor daemon is too old. (-83,21049:10053 ""))

When I try to update the license server i get the error message with DACL and cannot start the license server anymore.

Any help?

Regards.

Marco

[jeff.lotan]

You'll need to upgrade, I'd Upgrade to 11.13.1.2
www.autodesk.com/licensetools


Best regards,

Jeff Lotan
Sr. Tech Support Specialist/SAM Engagement Specialist
North America Solution Center
IMAGINiT Technologies
T: 888.528.4765
Email: productivitynow@rand.com
www.imaginit.com

[Anonymous]

That is what we wanted to do but when I update the license server afterwards I get an

error message with DACL (see attachement).

Then I cannot start the license server anymore.

[Darin.Green]

@Anonymous, Have you tried the workaround I provided, to download the previous version of LMTOOLS?

[Anonymous]

Hello,

I was already running license server with version lmgrd and lmtools 11.12

the problem are the new 2017 licenses

when i inserted them and wanted to run the programs they didnt get a license

the lmtool log said:  (adskflex) Request denied: Client (11.13) newer than Vendor Daemon (11.12). (Version of vendor daemon is too old. (-83,21049:10053 ""))

Anyway I tried it now again and it worked. I have no idea what I did.

Regards.

Marco

[Darin.Green]

I know what happened... you used my workaround 🙂

[DRW_CAD]

So... I'm a bit confused. I'm getting this error, similar to the initial post, i.e. 3 new servers that have never had LMs before. I am using nlm11.13.1.2_ipv4_ipv6_win64.msi & my service appears to be working and status indicates that the lic file I'm using has those licenses available. I've stopped and started the service as well as saved the service and the error doesn't come up again. 

But two things I'd like clarified if I could are:

1. It's definately a benign error? If so, all this is a moot point if the service is working correctly, right?

2. I've seen a solution of using an older version of LMtools. Are you talking about installing nlm11.13.1.2_ipv4_ipv6_win64.msi as you normally would to utilize 2017 products & then replacing the lmtools.exe file from the older version? I know there was a time when we could simply stop the service & copy over the files with the new version & restart the service. The last several versions have required uninstalling & reinstalling. I would think copying the lmgrd.exe wouldn't work but lmtools.exe? 

I think I'm good but it's very stressful switching these out each year. I test it on the small servers first & by the time I get to the ones that would bring us to our knees if they don't come back up, I've got it down to a formula one pit stop. so... error messages stress me out. 

[Anonymous]

hello darin,

as far as i understood your workaround is to continue using flexlm v 11.12 and that was not possible as i have said before

so what i did was to copy the nlm11_13.msi locally and start it from there. maybe that did it.

I am definitely using flexlm 11.13 now

Regards

Marco

[jeff.lotan]

I’ve resolved this problem on 2 different servers using this … and one of my co-workers had the same call this morning from another customer and I had her Save again and it worked. 

Autodesk Flex license manager error - Updating DACL Failed

If you are receiving this error with the new 11.13.1.2 license manager you are not alone.

I had a call on this and it also happened on one of my 2 servers that I upgraded to flexlm version 11.13.1.2. 

Situation:
I have downloaded and installed the latest edition v11.13.1.2 Build 173302 x64_n6 on 3 brand new servers running Window 2012 R2. Installed using default suggested path and then started LMTOOLS to create a new service. When i am finished i click "Save Service" and get an error message.

---------------------------
Updating DACL Failed
---------------------------
Service has been created but failed to update the DACL settings of FlexNet Licensing Service. It will give problem for accessing TS features. Check whether FlexNet Licensing Service is correctly installed or not and delete and create this service again
---------------------------
OK 
---------------------------

Solution:

This resolution worked on the above clients server and mine.

1. Click Ok on the dialog box.
2. Click Save again.  

This time we did not receive the error message.

1. Go to the Start/Stop/Reread tab
2. Click Start Server
3. Verify you have licenses by clicking "Perform Status Enquiry" on the "Server Status" tab.

Worked!!

Contact us to learn more about Autodesk programs.

Training: http://www.imaginit.com/training/options/overview
Sales: http://www.imaginit.com/about/offices-training-centers
Technical Support: 888-528-4765 http://www.imaginit.com/support/overview

Best regards,

Jeff Lotan

Sr. Tech Support Specialist/SAM Engagement Specialist

North America Solution Center

IMAGINiT Technologies

[petestrycharske]

Darin,

I had a situation like this as well and downgrading didn't help me sadly.  However, I noticed in the Enquiry Status box that the computer name had switched to the IP address.  When I changed the license file, as Mark mentioned you had done, that did the trick for me.  So, thanks Mark and Darin for the tips!  Have an awesome and most blessed night!

Peace,

Pete

[CRAengineer]

Chalk up another person with trhis issue... I've had the DACL error, wiped all traces of flex off the server and started anew with the latest flex (11.13.1.2) get the service configured and try an start the service and get 

"VD is starting, please check vendor daemon's statis indbug log"

checking the log we have: 

11:55:09 (lmgrd) Server's System Date and Time: Wed May 11 2016 11:55:09 Pacific Daylight Time
11:55:09 (lmgrd) pid 4500
11:55:09 (lmgrd) SLOG: Summary LOG statistics is enabled.
11:55:09 (lmgrd) Detecting other license server manager (lmgrd) processes...
11:55:09 (lmgrd) Done rereading
11:55:09 (lmgrd) FlexNet Licensing (v11.13.1.2 build 173302 x64_n6) started on domain-server (IBM PC) (5/11/2016)
11:55:09 (lmgrd) Copyright (c) 1988-2015 Flexera Software LLC. All Rights Reserved.
11:55:09 (lmgrd) World Wide Web:  http://www.flexerasoftware.com
11:55:09 (lmgrd) License file(s): C:\Program Files\Autodesk Network License Manager\License\IDSP2016_License.lic
11:55:09 (lmgrd) lmgrd tcp-port 27000
11:55:09 (lmgrd) (@lmgrd-SLOG@) ===============================================
11:55:09 (lmgrd) (@lmgrd-SLOG@) === LMGRD ===
11:55:09 (lmgrd) (@lmgrd-SLOG@) Start-Date: Wed May 11 2016 11:55:09 Pacific Daylight Time
11:55:09 (lmgrd) (@lmgrd-SLOG@) PID: 4500
11:55:09 (lmgrd) (@lmgrd-SLOG@) LMGRD Version: v11.13.1.2 build 173302 x64_n6 ( build 173302 (ipv6))
11:55:09 (lmgrd) (@lmgrd-SLOG@) 
11:55:09 (lmgrd) (@lmgrd-SLOG@) === Network Info ===
11:55:09 (lmgrd) (@lmgrd-SLOG@) Listening port: 27000
11:55:09 (lmgrd) (@lmgrd-SLOG@) 
11:55:09 (lmgrd) (@lmgrd-SLOG@) === Startup Info ===
11:55:09 (lmgrd) (@lmgrd-SLOG@) Is LS run as a service: No
11:55:09 (lmgrd) (@lmgrd-SLOG@) Server Configuration: Single Server
11:55:09 (lmgrd) (@lmgrd-SLOG@) Command-line options used at LS startup: -app -win -c C:\Program Files\Autodesk Network License Manager\License\IDSP2016_License.lic -l C:\Program Files\Autodesk Network License Manager\Log\debug.log 
11:55:09 (lmgrd) (@lmgrd-SLOG@) License file(s) used:  C:\Program Files\Autodesk Network License Manager\License\IDSP2016_License.lic
11:55:09 (lmgrd) (@lmgrd-SLOG@) ===============================================
11:55:09 (lmgrd) SLOG: FNPLS-INTERNAL-VL1-1024
11:55:09 (lmgrd) Starting vendor daemons ... 
11:55:09 (lmgrd) Starting vendor daemon at port 2080
11:55:09 (lmgrd) Using vendor daemon port 2080 specified in license file
11:55:09 (lmgrd) License server manager (lmgrd) startup failed: 
11:55:09 (lmgrd) CreateProcess error code: 0xc1   File= adskflex.exe

yes, I know we're not using the default install location but our other server in our other office is configured the same way and works flawlessly.

the only difference is this system is windows server 2003 r2 and the other is 2008 r2.  before we started the update, we had 2016 running just fine and now we can't even get back to that.

any ideas besides downgrading?

[Darin.Green]

@CRAengineer Welcome to the Community!

Open your license file with NotePad and add port 27005 to the end of the Server line.

This will ensure LMGRD for your Autodesk licenses are not sharing the same port as something else.