KevinL33
Occasional contributor

Flex license server 11.16 not starting on VMWare 6.7

Jump to solution

Trying to install the Flex license sever v11.16 on VMWare 6.7  however it doesn't seem to be compatible. Looking for advice.  I've configured the server properly with lmtools however when pressing the start button it fails to start and also does not log messages to the  error log.

We've seen this with two clients both running virtual servers.  The doc says that it's been tested on VMWare 6.7, is there a config that needs to be done?

 

Kevin Lee.

0 Kudos
1 Solution
jmcmillan
Flexera Alumni

Hi @KevinL33 

Your issue could be to do with the debug log and write permissions. It is best practice to set the location of debug_log_path to a subfolder of ProgramData. This location has user-write permission by default, which is needed when the license server runs as a service with LocalService permission. If you specify a different location, make sure you specify a fully qualified path that can be accessed with LocalService permissions.

One other test to see if your license server works is to run it in a command prompt. You can do this using the following syntax:

lmgrd.exe -c <YourLicenseFile> -l <YourDebugLog>

Then check the debug log for any errors.

If it runs ok, then it'll more than likely be a permissions issue.

Hope this helps.

Kind Regards,
Joe

View solution in original post

2 Replies
jmcmillan
Flexera Alumni

Hi @KevinL33 

Your issue could be to do with the debug log and write permissions. It is best practice to set the location of debug_log_path to a subfolder of ProgramData. This location has user-write permission by default, which is needed when the license server runs as a service with LocalService permission. If you specify a different location, make sure you specify a fully qualified path that can be accessed with LocalService permissions.

One other test to see if your license server works is to run it in a command prompt. You can do this using the following syntax:

lmgrd.exe -c <YourLicenseFile> -l <YourDebugLog>

Then check the debug log for any errors.

If it runs ok, then it'll more than likely be a permissions issue.

Hope this helps.

Kind Regards,
Joe

View solution in original post

KevinL33
Occasional contributor

Yes you nailed it.  Once we addressed the permission on the folder everything started working normally.  Thank you for your time and great answer.

Kevin.

0 Kudos