search cancel

Error with ca.olf file trying to start the harvest broker Component not licensed


Article ID: 5035


Updated On:


CA Harvest Software Change Manager - OpenMake Meister


When trying to start the harvest broker it appears the following error message:

ERROR: - Component not licensed. Please contact your account representative to obtain a new license


All Harvest SCM Versions.


The ca.olf file is missing or it's corrupted.


Set the License User Count

Important! If you have not received any licensing information, contact your account representative immediately to obtain a license.

Also you can create a ticket for customer care in the following link to obtain the license as well:


Follow these steps:

Navigate to the %CA_SCM_HOME% directory and locate the hbroker.arg file.

Verify that the ‑maxserver parameter setting matches the maximum user count for your license.

Note: The ‑maxserver parameter setting specifies the maximum number of product server processes permitted. One product server process corresponds to one product user. For example, if the maximum user count for your license is 100, set the ‑maxserver parameter to 100. The default user count is 50.

Save and close the hbroker.arg file.

Find and open the product's Lic98.log file, which typically exists in the CA_LIC directory.  The CA_LIC folder is in the <C:\Program Files\CA\SharedComponents> folder on a 32-bit Windows machine, and <C:\Program Files (x86)\CA\SharedComponents> on a 64-bit machine.

Check the file for an error message similar to the following message, which indicates that the -maxserver parameter is set higher than the licensed user count:

CA Licensing -2CHA - Usage limitation exceeded. Contact your account representative to obtain a new license.

If this message does not appear, go to the next step.

If this message appears, either lower the -maxserver count or contact your account representative to obtain a new license.

Copy the ca.olf file to the CA_LIC directory.


If you have an older installation you can get the ca.olf file from the old environment and pass to the new installation,

Note: first make a backup of the file that will be replaced, since that we can restore the new one if the action plan fails.