How to connect HiPath 3000 Manager E and CLA?

[Lexzie]

I have installed Manager E V10 R3.13.0 (latest version)
I have installed OpenScape License Management CLA V1 R48.0.0 (latest version)
I checked if License Agent is running under Windows Services.
In ass_150e.ini I added:
[tt][License]
Cla_Host=127.0.0.1[/tt]

I load a kds and when I click on Licensing (in the left pane) I always get the message 'Error: No response from CLA!'.

I have a lic-file but I want to set the system in Grace Periode so I do'n need the file.

When I try other kds' from other systems I get the same or Manager E crashes.

 

[plokijuh]

Usually it works just fine.

Did you start browser with CLA web page (desktop icon should appear after CLA installation)?

What is HiPath firmware version and OS version ?

 

[Lexzie]

I just installed CLA V1 R48.0.0 (updating the old V1 R42.0.0) and no desktop icon was made.
What desktop icon/shortcut would that be? I never had that before in the past.
Or do you mean the CLM? Never needed that too for HiPath 3000.

CLA runs as a Windows service and the service is running:

HiPath Manager E is latest version

HiPath is 3800 V9

OS is Windows 10, tried it on various machines

 

[plokijuh]

I think this is some software incompatibility.
I've never used Windows 10 or newer for CLA before. I usually use Windows 7.
Try to use windows compatibility mode.

I had a crash issue when opening the "Licensing" section, back then I updated the Manager and issue gone.

 

[Lexzie]

I already tried opening Manager E in compatibility mode (Windows 7).
I don't know how I should do that for CLA since it is running as a Windows service.
It worked in 2019, I'm sure because that was the last time I needed it for sure.
I also installed Manager E V10 R2.20.0 and CLA V1 R42.0.0 which both were released in april 2019, even on a laptop that was never used for Manager E.
I'm afraid I have to try it via f.e. VMware Virtual Machine.

 

[thepfy]

Could be Java issues, not unknown for CLA.

 

[Lexzie]

We managed to fix it.
HiPath 3000 Manager E uses TLS 1.0 (even the latest version does!).
You have to add a line to the file cla.xml (should be in C:\Program Files (x86)\Licensing\License Agent\bin):
[tt] <AllowOlderTlsProtocols>true</AllowOlderTlsProtocols>[/tt]

Also we uninstalled both Manager E and CLA and installed Manager E V10 R2.20.0 and CLA V1 R42.0.0.
Stopped the Windows service License Agent to edit cla.xml and started it afterwards.

If you try this with the latest Manager E (V10 R3.13.0) regardless if you use CLA v10 R48.0.0 of R42.0.0 Manager E crashes.

Although Manager E is still maintained I don't expect they will fix this for a product that is more than 10 years EOL.