Users were not able to start the Broker service through the Windows Services tool.
Attempting to run net start “OpenLM Broker” on the command line failed and:
- NO log file is created, since the service does not run the application.
- NO errors in the EventViewer
1. Try running the Broker from the command line.
This is running the Broker as a Java application, not as a service.
java -jar "C:Program FilesOpenLMOpenLM BrokerOpenLMBroker.jar" start "C:Program FilesOpenLMOpenLM Brokerbroker.xml"
In this case-study, this procedure succeeded. This means there is a problem only with the service and not the application.
2. Check the Registry:
a. Open the registry editor : type regedit in the start command line.
b. Navigate to
c. check that you have a Parameters key, with an Application name.
The value of this name should be:
"C:/Program Files/Java/jdk1.6.0_25/bin/java.exe" -Xrs -jar "C:Program FilesOpenLMOpenLM Broker/OpenLMBroker.jar" start "C:Program FilesOpenLMOpenLM Broker/broker.xml"
3. If this key does not exist, save the following marked text in a .reg file, and import it under key OpenLM Broker:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesOpenLM BrokerParameters] "Application"=""C:/Program Files/Java/jdk1.6.0_25/bin/java.exe" -Xrs -jar "C:\Program Files\OpenLM\OpenLM Broker/OpenLMBroker.jar" start "C:\Program Files\OpenLM\OpenLM Broker/broker.xml""
OpenLM Support Info
|Title||Broker Service not starting.|
|Date||Oct 05, 2011|
|Handled by||Efrat, Rachel.|
|Relevant Links||(link to mantis item, docs, customer correspondance etc.)|
|Symptoms||Broker service failed to start,
No broker log file was written
|Applies to license managers||FLEXlm, FLEXera FLEXnet, IBM LUM, HASP, RLM, Sentinel RMS|
|Applies to license mode||Floating licenses, Network licenses, Concurrent licenses|
|Observed during investigation||Error when attempting to run the broker service via command line.|
|Trouble shoot process||1. Run the Broker as a Java application (Not a service) from a command line, to establish whether the problem is in the application or just with running the service:
2. Check the registry for the required key.
3. Import the key.