Licensing keeps failing probably on Altairs end

Question

Subject: HyperMesh 2026.1 - Persistent License Activation Failure (Managed Licensing / Altair One)

Hello Altair Support,

I'm unable to activate my HyperMesh 2026.1 license via Managed Licensing (Altair One account), despite extensive troubleshooting. I'd appreciate help investigating this from the account/server side, as I've ruled out everything on my end.

Account: korne.gaal@edu.fh-joanneum.at

Product: Altair HyperMesh 2026.1

Licensing method: Managed on Altair One

Recurring error from the License Log:

System Error: No Auth Token in Managed Licensing config

Error during authorizing: Could not connect to server

System Error: SOAP 1.1 fault SOAP-ENV:Client [no subcode]

"End of file or no input: message transfer interrupted or timed out (5 sec max recv delay) (5 sec max send delay)"

Followed by:

Altair License Manager: License error

Feature(s): GlobalZoneEU, HyperWorks, HWHyperMesh

Error Code: 15

[NETWORK] 6200@localhost - (Err: 15) Unable to connect to license server

This also occurs for feature set GlobalZoneEU, HyperworksEDU.

What I've already ruled out:

* Tested on 4 different networks: university wifi, home wifi, mobile hotspot, and via a Cisco VPN — identical failure every time
* Fully uninstalled McAfee LiveSafe (was previously suspected as the cause of an earlier, different local error) — no change
* Windows Defender: added a full folder exclusion for the HyperMesh install directory — no change
* Reinstalled HyperMesh multiple times (5+), including a clean uninstall, reboot, and reinstall as Administrator — no change
* Confirmed I can log into my Altair One account successfully through a web browser on the same machine and network, so the account credentials and entitlement appear valid from that side
* Checked the Windows hosts file — no unusual redirects
* Checked Task Manager and Services (services.msc) for any Altair-related background process or service — none found, before or after reinstalling
* Colleagues at the same institution (fh-joanneum.at accounts) are able to activate and use HyperMesh without issue, which suggests this isn't a broader account-type/domain problem

Given that browser login succeeds but the desktop client consistently times out trying to reach the license server, and this happens across every network I've tested, I suspect this may be an account/session provisioning issue on the server side, or a client-specific bug, rather than something fixable through local network or antivirus configuration.

Could someone take a look at my account's Managed Licensing status/entitlement, and let me know if there's additional diagnostic information I can provide?

Thank you,

Kornel Gaal

Kornél_Gaál_2006 · Answer

Hi Ankita,

Thanks for the suggestions. I've tried all three and unfortunately none of them resolved it:

* Slow/unstable connection & timeout: I set ALM_HHWU_TIMEOUT=30 as a system environment variable and did a full PC restart afterward (not just relaunching HyperMesh). The failure is still happening at almost exactly the same ~4 second mark as before, so it doesn't look like a timeout issue — the connection is failing immediately, not running out of time.
* Firewall/antivirus blocking the connection: I fully uninstalled McAfee LiveSafe (not just disabled it) and also added a full folder exclusion for the HyperMesh install directory in Windows Defender. Still the same error afterward.
* Proxy: I checked both the in-app Proxy Settings (Use Proxy is unchecked/not configured) and confirmed my internet access isn't routed through any proxy. I've also tested this on 4 completely different networks — university wifi, home wifi, mobile hotspot, and via a Cisco VPN — and get the identical error every time.

A few more data points that might help narrow this down:

* I can log into my Altair One account successfully through a web browser on this same machine/network, so the account and credentials seem fine from that side.
* I checked Task Manager and Services (services.msc) for any Altair-related background process/service — none exist, even after multiple clean reinstalls.
* Colleagues at my institution (also fh-joanneum.at accounts) can activate and use HyperMesh without any issue, so this doesn't seem to be a broader account-type problem.

The recurring error is:

System Error: No Auth Token in Managed Licensing config

Error during authorizing: Could not connect to server

System Error: SOAP 1.1 fault SOAP-ENV:Client [no subcode]

"End of file or no input: message transfer interrupted or timed out (5 sec max recv delay) (5 sec max send delay)"

Followed by:

Altair License Manager: License error

Feature(s): GlobalZoneEU, HyperWorks, HWHyperMesh

Error Code: 15

[NETWORK] 6200@localhost - (Err: 15) Unable to connect to license server

Given that browser login works fine but the desktop client consistently fails within a few seconds regardless of network, antivirus, or firewall configuration, would it be possible to check my account's Managed Licensing status/entitlement on your end? I'm happy to provide any additional logs or diagnostics if that would help.

Thanks again for your help,

Kornel

Ankita_v · Answer

@Kornél_Gaál_2006

The error you are seeing usually means that the software is having trouble connecting to our servers. This can happen for a few different reasons -

One common cause is a slow or unstable internet connection. By default, the software tries to connect for 5 seconds before timing out. If your connection is slightly delayed, that may not be enough time. You can increase the timeout by setting an environment variable:

ALM_HHWU_TIMEOUT=<timeout in seconds>

e.g. ALM_HHWU_TIMEOUT=15

Another possible reason is that a firewall or antivirus program on your computer is blocking the connection. If that is the case, increasing the timeout will not resolve the issue. You will need to add an exception in your firewall or antivirus settings to allow the software to connect.

It is also possible that your internet access goes through a proxy. If so, the proxy settings must be correctly configured on your computer, and the proxy must allow the software to reach our servers.

Thanks