Mr.X
asked on
One of the services is not starting
Hi guys,
Got 2011 sbs
One of the service is not starting from services.msc
Whenever I start the service, giving an error
“Error1503: the service did not respond to the start or control request in timely fashion”
Tried restarting the server- still no luck
Any idea ??
Got 2011 sbs
One of the service is not starting from services.msc
Whenever I start the service, giving an error
“Error1503: the service did not respond to the start or control request in timely fashion”
Tried restarting the server- still no luck
Any idea ??
ASKER
It's a third party application
Flexnet licensing
Flexnet licensing
I have not see that application. Uninstall it, restart and then install it again. See then if the service starts properly.
Best is to check the application log - could be licensing, SSL or similar issue. Log will tell you more.
flexnet is a licensing service used by some application vendors
i would start by contacting support for that 3rd party application
could be as simple as doing a repair and not having the need to uninstall and reinstall
i would start by contacting support for that 3rd party application
could be as simple as doing a repair and not having the need to uninstall and reinstall
The Flexnet executable or service should be able to run whether you have a license or not. This is the network license server itself, not the licensed product. Where are the Flexnet license manager files installed? Can you open a command prompt, navigate to it, then run the lmgrd.exe command on the command line? (It may be renamed, depending on the product. Check your instructions) Does it start there in Command Prompt Window? Can you start lmtools.exe?
If it runs manually, the service might be installed incorrectly. Did you check the radio button for Configuration using services in the Service/License File tab? It might be pointing to the wrong executable path or have the wrong options. How was the service installed? Remove the service from Services.mmc and use LMTOOLS to reinstall it, or go use the command line options and you can run it from the command line. Depending on the vendor version, it installs the services in different ways. Early Flexnet installs use the sc command to install it from a batch file. Some vendors use an compiled executable that basically does the same thing. Maybe there was a mismatch or typo in the script or executable, or maybe you did not install it in the default location or you had spaces in path or service name. They came from the Unix world, so it still has command line mode to get set up.
You can manually install the service with the sc.exe command and give the services your own name. Something similar to the following. (doing from command line memory, not from actual command. You may need to give lmgrd.exe the proper options to load the license.lic file, or whatever the license file is named)
sc create MyLicenseService C:\MyLicensedProduct\Flexn
If you have multiple products that use Flexnet, you can even use the generic lmgrd.exe License manager and consolidate licenses to one license service, instead of installing several Flexnet services. Some of them might have renamed there services to a product name, but it's still basically the lmgrd.exe exectuable. You'll just need to change or set the ports, assuming the products allow the changes in port configuration. Most Flexnet license products used unique ports, so they'll load in the same license server. There are a few tools in the Flexnet bin folder that lets you manage the licenses via the command line. They match their Unix counterparts with the same syntax.
If it runs manually, the service might be installed incorrectly. Did you check the radio button for Configuration using services in the Service/License File tab? It might be pointing to the wrong executable path or have the wrong options. How was the service installed? Remove the service from Services.mmc and use LMTOOLS to reinstall it, or go use the command line options and you can run it from the command line. Depending on the vendor version, it installs the services in different ways. Early Flexnet installs use the sc command to install it from a batch file. Some vendors use an compiled executable that basically does the same thing. Maybe there was a mismatch or typo in the script or executable, or maybe you did not install it in the default location or you had spaces in path or service name. They came from the Unix world, so it still has command line mode to get set up.
You can manually install the service with the sc.exe command and give the services your own name. Something similar to the following. (doing from command line memory, not from actual command. You may need to give lmgrd.exe the proper options to load the license.lic file, or whatever the license file is named)
sc create MyLicenseService C:\MyLicensedProduct\Flexn
If you have multiple products that use Flexnet, you can even use the generic lmgrd.exe License manager and consolidate licenses to one license service, instead of installing several Flexnet services. Some of them might have renamed there services to a product name, but it's still basically the lmgrd.exe exectuable. You'll just need to change or set the ports, assuming the products allow the changes in port configuration. Most Flexnet license products used unique ports, so they'll load in the same license server. There are a few tools in the Flexnet bin folder that lets you manage the licenses via the command line. They match their Unix counterparts with the same syntax.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The service is spawned by an application. Did you / can you uninstall the application, restart the server at a convenient spot, and install the application again.