Hydratec Inc.

Need to save a card for later?

Create a bookmark folder in your browser of choice (Chrome, Firefox...), and save individual cards in your bookmarks to view here later.

Security and Licensing HydraKEY (Ribbon/Toolbar/Location)

Button: Add New Authorization Error Type: Failed Call To Server

Description:

A failure to call the Hydratec security server occured. 

-OR-

Hydratec Security Error

FAILED CALL TO SERVER (to Activate): Could not parse request body into json.

 

Solutions:

1.
Cause:

In September of 2023 AWS upgraded their servers to only allow TLS 1.2 Connections or later.  Any version of HydraKEY before version 2023.05.04 will not function correctly and give some or all of these errors:
Solution:

You need to update your HydraKEY application to version 2023.09.09 or later.  To do this follow these steps:

  1. Close all hydratec products, including HydraKEY.
  2. Open this link to download the install .zip :  https://hydrakey-public.s3.us-east-2.amazonaws.com/HydraKeyInstall.zip
  3. Unzip and run the HydraKEYInstall.exe inside the .zip.
  4. Open HydraKEY and make sure it says 2023.09.09 (or later) in the top title bar.
  5. Try doing whatever you were doing originally to see that it no longer causes any of the three errors on the left.  (i.e. “Transfer Authorization”, “Renew Authorization” , “Add New Authorization” , Opening a Hydratec product, etc.)
2.
Cause:

FAILED CALL TO SERVER (to Activate) A WebException with status NameResolutionFailure was thrown

 

FAILED TO CALL SERVER (To Transfer LTA): The role defined for the function cannot be assumed by Lambda
Solution:

Your internet connection is down or very slow. Try again Later.

Your firewall is blocking the connection between HydraKEY and the AWS server. Talk to your administrator.

If you are being blocked by security on your network or machine, let you administrator know:

·  Allowlist *amazonaws.com. In other words, allowlist all domains that end with .amazonaws.com. We call their servers to check HydraKey version as well as activate, renew and transfer our authorizations.

  • If you're unable to allowlist *amazonaws.com, you can allowlist our specific calls: 
    • s3-r-w.us-east-2.amazonaws.com
    • us-east-2.compute.amazonaws.com

-These calls are made on the dynamic secondary ports.  These are randomly assigned ports within the following range:   5001 - 65500

-To test if your firewall or some network condition is blocking the call, try connecting your computer to a different wifi network (like a hotspot on your phone) then try opening HydraKey and running the command again. If it still doesn't work, then the problem is likely some software running on windows, or windows defender firewall.

-To test if some software on your machine is blocking you, try opening a browser and going to following address: https://hydrakey-public.s3.us-east-2.amazonaws.com/HydraKEY_Current_Versions_Comparison_File.txt

It should looks something like this (the numbers may be different, but that's alright):

If you see these words with some numbers after, but opening Hydrakey gives a "Cannot get latest HydraKEY update information!"  Error,  then some software on your computer is specifically stopping calls to the internet by HydraKey.exe and HydraLicenseUpdater.exe but allowing your browser to go to the exact same link without a problem.  You are looking for virus scanners and firewalls in which to change settings.

Sometimes upgrading from windows 10 to windows 11 can fix this issue.

-HydraKEY Version 2022.04.17 and previous use the Server Certificate TLS 1.0 to communicate with the AWS server.  Later versions of HydraKEY will use TLS 1.2.   If you are on version 2022.04.17 or before and your administrator has set up your network to restrict TLS 1.0 / SSL communication, it will cause this error.
3.
Cause:

Solution:

Your FIPS security settings are blocking your ability to reach the AWS servers for Activation, Renewal or Transfer of your HydraKEY authorization.

-Disable FIPS

   -Open Control Panel in windows.

  -Got to "System and Security"

    -Go to  "Administrative Tools"

   -Choose "Local Security Policy"          

     -Choose "Local Policies" then "Security Options"   

       -On the right side find "System cryptography: Use FIPS copmpliant algorithms for ...."

       - Right-Click it and choose "Properties", then Disable it, then hit ok.  

-In Local policies, It should look like this:

-NOW TRY TO ACTIVATE, TRANSFER OR RENEW IN HYDRAKEY AGAIN. MAKE SURE FIPS HAS REMAINED OFF.

- if you like, Re-enable FIPS. (you'll have to repeat this process each time you renew your authorization if you do)

       -In Local Policies, it should now look like this:    

 
4.
Cause:

When trying to "Add New Authorization" or "Renew Authorization"  you receive the error "Failed call to server Not Found".
Solution:

The HydraKey system is having trouble creating a machine id for the current machine because it is having issues obtaining the machine's hardware profile.

If this is the case, you will likely be able to repair this problem by running some Windows scripts.  See HydraCARD #1232 , cause #1 for its instructions.

-Re-installing Windows will very likely repair the problem, if you are able.

 

If you are not able, and the above link to the batch file doesn't work, there are 2 scripts that have been known to help:

Open the windows command shell as administrator:

-type CMD in the search area of the task bar

-right click on "Command Prompt"

-select "Run as administrator"

 

-Copy and paste the following:

sc config winmgmt start= disabled

net stop winmgmt /y

%systemdrive%

cd %windir%\system32\wbem

for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s

wmiprvse /regserver

winmgmt /resetrepository

sc config winmgmt start= auto

net start winmgmt

-Should look something like:

-Try again to activate.

-If that doesn't work try copying and pasting the following script into the command prompt:

@echo on

cd /d c:\temp

if not exist %windir%\system32\wbem goto TryInstall

cd /d %windir%\system32\wbem

net stop winmgmt

winmgmt /kill

if exist Rep_bak rd Rep_bak /s /q

rename Repository Rep_bak

for %%i in (*.dll) do RegSvr32 -s %%i

for %%i in (*.exe) do call :FixSrv %%i

for %%i in (*.mof,*.mfl) do Mofcomp %%i

net start winmgmt

goto End

 

:FixSrv

if /I (%1) == (wbemcntl.exe) goto SkipSrv

if /I (%1) == (wbemtest.exe) goto SkipSrv

if /I (%1) == (mofcomp.exe) goto SkipSrv

%1 /Regserver

:SkipSrv

goto End

:TryInstall

if not exist wmicore.exe goto End

wmicore /s

net start winmgmt

:End

-Try again to activate.

If you are being blocked by security on your network or machine, let you administrator know:

·  Allowlist *amazonaws.com. In other words, allowlist all domains that end with .amazonaws.com. We call their servers to check HydraKey version as well as activate, renew and transfer our authorizations.

  • If you're unable to allowlist *amazonaws.com, you can allowlist our specific calls: 
    • s3-r-w.us-east-2.amazonaws.com
    • us-east-2.compute.amazonaws.com

 

 

Downgrade to version 2023.05.04 of HydraKEY and request an old style pass from Hydratec:

https://hydrakey-public.s3.us-east-2.amazonaws.com/HydraKey0504Install.exe
5.
Cause:

When tryinig to use a Serial Number in HydraKey, One of the above messages occurs.

Version of AWS .dlls are out of sync with version of windows.  This particularly occurs on older versions of Windows.

On some machines running an older version of HydraKEY, this can occur when attempting to Activate a new Long term authorization or renew an existing one.
Solution:

-Hit the UPDATE button inside HydraKEY.  or click this link: https://hydrakey-public.s3.us-east-2.amazonaws.com/HydraKeyInstall.exe

-Select "Save File"

-Go to the folder where the file downloaded.

- Close All HydraTec Products.

-Right Click and Run the file as administrator:

-Go through the install and click Finish.

-You are now on the newest version of the HydraKEY install.
6.
Cause:

Unknown cause, but may be related to Dell computers and old drivers and firmware

 
Solution:

1. Upgrading the Dell computer from Win10 to Win11 worked and the user was able to load the authorization.  This end user did try to update drivers before going to Win11.

2. After running all driver and firmware updates on the Dell computer the end user was able to load their Perpetual Authorization

 
Updated: April 11, 2024, 3:34 p.m. Created: March 2, 2020, 6:21 p.m.