Multiple lmadmin installations on windows

[christian_lemm]

Hi all,

as a software vendor I would tend to recommend my customers to install a separate instance of lmadmin per vendor - although lmadmin supports multiple vendors in one lmadmin server.

Separate installations would minimize inter-dependencies.

I tried to install lmadmin64-11.16.3.0 twice on windows 10.  It looked quite promising, the installer gave me the option to install into different directories, use different ports, and I could even give the lmadmin service different names.

Both installations started the web server (on different ports), but the second installation reported this error message: "Encountered problem saving license server configuration"

And, when checking the windows settings "Apps & Features" I saw only one entry for FlexNet Publisher.

So my question: should it be possible to have multiple lmadmin installations?

Best regards, Frank

[aparashar1]

Hi Christian,

Multiple lmadmin on a single system is a supported configuration.

Could you share the lmadmin along with VD log, so that we can try a quick analysis on what may have gone wrong?

Regards,

Abhay

[christian_lemm]

Dear Abhay, I have no vendor daemon log so far, as I didn't import any key up to this point. The error message already comes on the first login, after/together with the mandatory changing of the password. The lmadmin.log ist empty in both logs directories.

C:\ProgramData\FLEXlm\lmadmin\logs\web.log

[Fri Apr 26 16:03:37.403058 2019] [:notice] [pid 10432:tid 1008] ModSecurity for Apache/2.9.2 (http://www.modsecurity.org/) configured.
[Fri Apr 26 16:03:37.403058 2019] [:notice] [pid 10432:tid 1008] ModSecurity: APR compiled version="1.6.3"; loaded version="1.6.3"
[Fri Apr 26 16:03:37.403058 2019] [:notice] [pid 10432:tid 1008] ModSecurity: PCRE compiled version="8.41 "; loaded version="8.41 2017-07-05"
[Fri Apr 26 16:03:37.403058 2019] [:notice] [pid 10432:tid 1008] ModSecurity: LIBXML compiled version="2.9.9"
[Fri Apr 26 16:03:37.403058 2019] [:notice] [pid 10432:tid 1008] ModSecurity: Status engine is currently disabled, enable it by set SecStatusEngine to On.
[Fri Apr 26 16:03:37.403058 2019] [ssl:warn] [pid 10432:tid 1008] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
[Fri Apr 26 16:03:37.403058 2019] [mpm_winnt:notice] [pid 10432:tid 1008] AH00354: Child: Starting 10 worker threads.
WARNING: An error ocurred saving the config file: unable to open file 'C:\ProgramData\FLEXlm\lmadmin\conf\server.xml'
WARNING: An error ocurred saving the config file: unable to open file 'C:\ProgramData\FLEXlm\lmadmin\conf\server.xml'

C:\ProgramData\FLEXlm\lmadmin2\logs\web.log

[Fri Apr 26 16:03:42.906210 2019] [:notice] [pid 12572:tid 996] ModSecurity for Apache/2.9.2 (http://www.modsecurity.org/) configured.
[Fri Apr 26 16:03:42.906210 2019] [:notice] [pid 12572:tid 996] ModSecurity: APR compiled version="1.6.3"; loaded version="1.6.3"
[Fri Apr 26 16:03:42.906210 2019] [:notice] [pid 12572:tid 996] ModSecurity: PCRE compiled version="8.41 "; loaded version="8.41 2017-07-05"
[Fri Apr 26 16:03:42.906210 2019] [:notice] [pid 12572:tid 996] ModSecurity: LIBXML compiled version="2.9.9"
[Fri Apr 26 16:03:42.906210 2019] [:notice] [pid 12572:tid 996] ModSecurity: Status engine is currently disabled, enable it by set SecStatusEngine to On.
[Fri Apr 26 16:03:42.906210 2019] [ssl:warn] [pid 12572:tid 996] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
[Fri Apr 26 16:03:42.906210 2019] [mpm_winnt:notice] [pid 12572:tid 996] AH00354: Child: Starting 10 worker threads.

See also attached screenshot for error message in lmadmin for second installation.

Again there is only 1 entry in "Apps & Features".

Today, I tried two different ways to start the installer.  First time, I started the installer just by double-click.  Then I was asked for an admin account. For both installations.  The second time, after having uninstalled everything, I did a right-click on the installer and chose "Start as administrator".  But always the same results.

What I did not try so far, is to login to windows with an administrator account.  Don't know, if this would make a difference.