FLEXnet Licensing Error: -15,570

[cmcruz]

Hello,

I am trying to install LMTOOLS with a single licensing server onto a Windows 2008 Standard server. We have 4 licenses of AutoCAD 2007. The install went OK, and I think that the license creation worked, but when I configure LMTOOLs and Perform a Status Enquiry, I get the following error:

--------
Status
--------
Flexible License Manager status on Thu 1/29/2009 14:08

[Detecting lmgrd processes...]
License server status: @clarkapps
License file(s) on clarkapps: C:\Program Files\Autodesk Network License Manager\License\ACD2007clarkapps2.lic:

lmgrd is not running: Cannot connect to license server system.
The license server manager (lmgrd) has not been started yet,
the wrong port@host or license file is being used, or the
port or hostname in the license file has been changed.
Server name: clarkapps
License path: @clarkapps
FLEXnet Licensing error:-15,570
For further information, refer to the FLEXnet Licensing End User Guide,
available at "www.macrovision.com".

It appears to be referencing the correct license file. I've added port 2080 (which is referenced in the license file) to the Windows Firewall and still no dice. When I try to manually start the Flexlm service from Services, I get an error that the service did not respond to the start or control request in a timely fashion within a few seconds of hitting start.

Any thoughts would be greatly appreciated.

Thank you,
Christine

[cmcruz]

When I look at the System log, I get the following error message while trying to start the service:

"The Flexlm Service 1 service failed to start due to the following error:
Flexlm Service 1 is not a valid Win32 application."

Could my version not be compatible with Windows Server 2008 (Windows Server 2008 Standard SP1)?

Thank you.

[Anonymous]

Try this :

href="http://support.microsoft.com/kb/875351">http://support.microsoft.com/kb/875351

Franck Hervet

href="http://www.aricad.fr">www.aricad.fr

style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">

"cmcruz" a écrit dans le message de groupe de discussion :
title="mailto:6115091@discussion.autodesk.com CTRL + Cliquez ici pour suivre le lien"
href="ma......

When
I look at the System log, I get the following error message while trying to
start the service: "The Flexlm Service 1 service failed to start due to the
following error: Flexlm Service 1 is not a valid Win32 application." Could my
version not be compatible with Windows Server 2008 (Windows Server 2008
Standard SP1)? Thank you.

[cmcruz]

Thanks for the idea. It didn't work though.

[cmcruz]

Different error. Looks like it has something to do with .NET Framework.

I'll repost if I get it working after updating.

Thanks!

[cmcruz]

OK, I still can't get the service started. I increased the timeout value in the registry as the error message suggests, but no dice. Any ideas?

Error messages when trying to start the Flexlm service:

"A timeout was reached (100000 milliseconds) while waiting for the Flexlm Service 1 service to connect."

"The Flexlm Service 1 service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."


Thank you!

[Anonymous]

hello,
i have the same error. did you manage to work this problem out?

[Anonymous]

ok i found out where the problem was. in my situation i checked in lmtools to use flexnet as a service nad to start up at power on. unfortunatelly it dont work in windows server 2008 and it also block starting the server manually. after unchecking these two boxes and restarting server i was manage to manually start the flexnet server. hope this works for others 🙂

[jmayo-EE]

If I can bring this back to life for I would like someone to better explain this.

"and it also block starting the server manually"

I have someone who has issue getting LMTools congfigured with Server 08 and they had it working before updating LMTools.

Thanks,

John

[Anonymous]

Just a quick note, in case folks are still running into this:
My server was 2003 standard

This error was resolved for me, by specifying a log directrory in the service config tab of lmtools.

Don't really care about a log, but the service setup required this.

I also had to adjust the new Code Execution Prevention crap, so it could have also been a problem.

Lata,
Ribs