Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CLM- Localhost refused to connect

Status
Not open for further replies.

LAAZ

Systems Engineer
Aug 4, 2021
111
IN
Dear Friends,

i am facing issue while opening CLM to activate the license of AC Win console.

I am getting an error
Refused to connect localhost.

Please guide me to resolve the issue.

i am trying to activate the license with CLA through import ,still I am getting Unauthorized copy of AC WIN


thanks
 
You do not need CLM. It's just a GUI to the CLA interface. You only need CLA installed to license the application.

The process to use CLA is.
1 - CLA is installed to (default) C:\Program Files (x86)\Licensing\License Agent
2 - You drop the .lic file into C:\Program Files (x86)\Licensing\License Agent\import
3 - The .lic file will disappear in a couple of seconds and
- if the licence is OK, an rlf_xxxx.XML file (same file but with new name) appears in the C:\Program Files (x86)\Licensing\License Agent\license directory
- if the licence is not OK - a new file does not appear in license dir, and in C:\Program Files (x86)\Licensing\License Agent\log\error.log, you will see the reason why it did not work.


So if you have a problem, you check first did the license import OK (do you have a new file in license dir, which is good, or do you have new text in error.log, which is bad).

If you have an entry in error.log, you solve whatever that issue is, likely wrong locking ID.
If you have a new file in the license dir, then so far everything is good and your license is importing.

But if you then have a problem with your application reporting no license, it could be.
1 - Wrong license/wrong version of software (nothing wrong with CLA here)
2 - CLA not running/listening on port 61740 (app/firewall issue)
3 - Wrong TLS version, somewhere around R40/R41, CLA switched to TLS 1.2 connection only. If you have an older app that is not talking TLS 1.2 it will not be able to connect to CLA. You have to either use an older CLA, or in the C:\Program Files (x86)\Licensing\License Agent\bin\cla.xml file, add the line AllowOlderTlsProtocols and set to true, and restart the CLA service.

In the same cla.xml you can also increase tracelevel, change from "low" to "all", and in the C:\Program Files (x86)\Licensing\License Agent\trace\trace.log you will see a lot more going on. Remember to change it back to low when finished. If CLA is on a separate machine, Wireshark is useful to confirm that the app is hitting the CLA server.

You can't install the same license twice, CLA will remember, so it might be easier to uninstall CLA, make sure the old C:\Program Files (x86)\Licensing\License Agent dir is removed, and start again.

 
Dera Moriendi,

Thank you very much for your information and will update here once resolved.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top