End Google Tag Manager (noscript) -->
USA +1 866 806 2068 | UK +44 203 1292 513 | JAPAN +81 3 45208991 担当:萩原 info@openlm.com

Broker Service Not Starting: TS-BR001

Symptom

 

alt

Observed

Run net start “OpenLM Broker” on the command line.
The following error was observed
alt

In this case

-NO log file is created, since the service does not run the application.

-NO errors in the EventViewer

Troubleshooting:

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 Files\OpenLM\OpenLM Broker\OpenLMBroker.jar”

start “C:\Program Files\OpenLM\OpenLM Broker\broker.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

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\OpenLM Broker

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 Files\OpenLM\OpenLM Broker/OpenLMBroker.jar” start “C:\Program Files\OpenLM\OpenLM 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_MACHINE\SYSTEM\CurrentControlSet\services\OpenLM Broker\Parameters]

“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\””

 

Title Broker Service not starting.
Category Broker
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:
– Succeeded.
2. Check the registry for the required key.
– Failed.
3. Import the key.
Solution Found