Issue with hosted licenses; Error Code: 1; HHWU;

Benjamin Mayr
Benjamin Mayr Altair Community Member
edited February 2021 in Community Q&A

Hello Community,

Our company recently decided to use hosted licenses on Altair One instead of local license files.
Although all machines were set up and authorized correctly, we got following error code:
(We also got some other error-codes due to our applications failing to get licenses, but I think that one is the relevant one.)

Error Code: 1
Error Description:
SOAP 1.1 fault SOAP-ENV:Client [no subcode]
"SSL_ERROR_SSL
error:14007086:SSL routines:CONNECT_CR_CERT:certificate verify failed
unable to get local issuer certificate"
Detail: SSL/TLS handshake failed

This error looked like there may be a problem in the connection to AltairOne, so the IT department tried to fix this (without success). In the end we got a contact to license-support, which figured out the problem.

We added a System variable: “ALM_HHWU_USE_WININET” and set the value of that new variable to “1”. This fixed our Problem immediately.

Hopefully I can spare you some hours of troubleshooting with this post.

Greetings
Benjamin

Tagged:

Best Answer

  • Matthieu Pupat
    Matthieu Pupat
    Altair Employee
    edited February 2021 Answer ✓

    Hello,

    The error message you mentioned comes from proxies which re-encrypt the traffic with their own certificate. Altair One rejects this traffic as it has been altered.

    The solution is either to define the variable ALM_HHWU_USE_WININET=1 as you mentioned or to add an exception to the proxy configuration for the traffic to our servers.

    Please also not that the behavior has changed in the most recent versions of our software and this should not be needed with them.

    Thanks,

    Matthieu

Answers

  • Matthieu Pupat
    Matthieu Pupat
    Altair Employee
    edited February 2021 Answer ✓

    Hello,

    The error message you mentioned comes from proxies which re-encrypt the traffic with their own certificate. Altair One rejects this traffic as it has been altered.

    The solution is either to define the variable ALM_HHWU_USE_WININET=1 as you mentioned or to add an exception to the proxy configuration for the traffic to our servers.

    Please also not that the behavior has changed in the most recent versions of our software and this should not be needed with them.

    Thanks,

    Matthieu

Categories