I'm having the same issue, I've installed FlexLM on a Windows 2003 (SP1 32bits), it runs fine in "manual" mode, with LMtools running with a user loggued in, but I am unable to install it as a service using LMTools (Use Services checkbox under the "Config Services" tab.
If I try to start the server as a service it give the generic error:
Server Start Failed. The Server May Already Be Running!! (it isn't)
If I try to ReRead License File it gices the error:
Reread Server Failed.
It does create the service in windows, but trying to start the service gives an error
"Could not start the service name service on Local Computer" Error 193: 0xc1
Any help, suggestions??
The latest version now at the time of this post is 11.8 and is provided by Flexera. You can download the appropriate 32-bit version for your Server 2003 here:
I would recommend the following steps:
1. Open LMTOOLS
2. Stop the service from Stop/Start/Reread, making sure the Force Server Shutdown box is checked.
3. Remove the service from the Config Services tab.
4. Recreate the service (default name is Flexlm Service 1) pointing to all the correct files. Create a new debug.log file if an old one already exists. Check both boxes at the bottom and save the service.
5. Start the service from the Stop/Start/Reread tab.
I also highly recommend adding all four NLM .exe files to the Data Execution Prevention (DEP) exception list found under the WIndows System Properties > Advanced tab > Performance settings > Data Execution Prevention tab.
If you still have problems, please let me know.
Hadn't thought of DEP!
I've updated to Flexera and made the changes to DEP.
Unfortunatly DEP requires a reboot and the server is used by that department for some other purpose, so I can only reboot it off hours.
I'll keep you posted, thank you for the fast reply!
I found the culprit... the service wouldn't start because there are spaces in the path...
(ie: D:\Program Files\AutoCAD License Manager\...)
Here's the fix:
To resolve this issue, add quotation marks around the following entry in the Windows registry, where <ServiceName> is the name of the service:
The ImagePath entry contains the path of the executable file for the service. To add quotation marks around the ImagePath entry for a service:
Thanks for your help!
Very good find and thanks for sharing that information. It's strange that sometimes spaces will still break programs even though they work for 99% of everyone else.
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!