HLK Studio Machine status stuck "initialising" but "ready" in HLK manager

Question

Hi!

Can someone kindly help me get out of this situation with HLK Studio, please? I am an new to it.

I have a test machine which seems always to be stuck at status "Initlaisating" when viewed in HLK Studio -> Configuration -> Machine Management. I cannot get it out of that state. I did once manage it but it later got stuck again after a reboot. A reinstall did not fix this.

The interesting thing (for me) is that in HLK Manager -> My Machines the system in question shows as "ready". There, I can schedule tests on it (e.g. DF- InfVerif) and they run and return results. (They fail, FYI, but I am not asking about that right now.) But I cannot do anything more than this and the features I need from HLK Studio remain unusable because my test system is not ready.

Server: Windows Server 2019 server with "Windows Hardware Lab Kit - Windows 10" Controller 10.1.15063.0 . No domain configured.

Client: Windows 10 Pro 1803 build 17134.1304 server with "Windows Hardware Lab Kit - Windows 10" 10.1.15063.0

I had thought this was an issue specific to the client release of Windows 10 but I also tried with Windows 10 build 19041 and 19043 with the same results so I am guessing there is something up with my server configuration. It could be something simple I've missed although I have been through the a number of guides and documents, no of which refer to this symptom.

A couple of posts on other forums refer to firewall and UAC controls, and I have disabled both completely with no obvious effect. (The install process did ask me if I wanted to allow a port to be opened and I agreed to that.) Do I need to have change UAC/Firewall settings before installing the client part of HLK from HLKInstall share?

Does anyone have experience and advice regarding this situation?

Thanks in advance
AD

Answer 1

Okay - it looks like this was a mismatch between the Win10 version and the version of HLK. I was pretty sure I had used the correct versiion for Windows 10 19041 or but further a reinstallation of the server/controller from re-downloaded sources seems to have resolved this for me.

This really came down to chasing error messages in the controller-side application event log for HLK. Basically, if you get "Error: Could not find a Release in the database that matches build number 'xxxxx'" in your application event log (where xxxxx could be 17134, or 19041 - the build no of Win10 as shown in settings -> system -> about, then your database is either broken or too old a version for your test clients.

I hope this helps someone.

Answer 2

Hi,

Here are my troubleshootings. Please try followings.

• Delete the machine in Configuration and reboot the machine.
  The machine will be shown in Default fool. Then move the machine to your machine fool(you created).

or

• If you connect client machine and HLK server not directly(VMware, etc), modify network type to Bridge (not NAT or else).

Answer 3

Thanks, 781827897. I tried that previously and tried again just now but it still doesn't work. It is stuck in initialising.

By the way, I omitted to mention that the "Platform" always shows "Unknown platform". It machine is never identified as Windows 10. My apologies because I am sure that is relevant. Furthermore, I find in the HLK application event log entries for "Error: Could not find a Release in the database that matches build number '17134' which is the Win 10 build number of my client.

So my thought is actually that the controller installation is somehow screwed up. I will maybe do a complete re-isntall and see how I fare.

Thanks in advance,
Aidan

Answer 4

HI, All

A re-install of HLK controller + studio did not fix the issue. Nor did another re-install of the client OS and HLK from \...\HLKInstall.

Regards,
Aidan

Answer 5

Just check more detail error in event vỉewer,

If error like "Could not find a Release in the database that matches build number..." you need re install version HLK Controller or install HKL Client on ohter PC (or VM)