HPC Pack 2019 cannot connect to headnode immediately after first install

Ivan Voutchkov 1 Reputation point

I have just installed HPC Pack 2019 Update 1 on a brand new Windows Server 2022. Immediately after installation finishes and I attempt to start the HPC Cluster Manager I get this. Please help!

The connection to the management service failed. detail error: Microsoft.Hpc.RetryCountExhaustException: Retry Count of RetryManager is exhausted. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Hpc.HttpClientExtension.<>c__DisplayClass5_0.<

Azure HPC Cache
Azure HPC Cache
An Azure service that provides file caching for high-performance computing.
22 questions
{count} votes

5 answers

Sort by: Most helpful
  1. Yutong Sun 261 Reputation points Microsoft Employee

    Hi @Ivan Voutchkov ,

    The call stack indicates there was a connection issue with the HpcNaming service to resolve the service instance. Could you check if the HpcNaming service is in running state on the head nodes and retry it again?

    Yutong Sun

    0 comments No comments

  2. Nathan Anderson 0 Reputation points

    @Ivan Voutchkov Did you ever get this working? I'm running into the same problem.



    0 comments No comments

  3. Gurvinder Bindra 0 Reputation points

    New deployment, SAME issue! Will appreciate any help we can get! Naming service IS running!

  4. Ken Kam Hung, Lin 91 Reputation points

    I have the same issue too, after installing HPC Pack 2019 Update 2 on Win 2022.

    0 comments No comments

  5. Yutong Sun 261 Reputation points Microsoft Employee

    For running HPC Pack 2019 on Windows Server 2022, please also check if the required .Net Framework 4.8 cumulative update August 9, 2022-KB5015733 or later is applied to all cluster nodes and clients that are on Windows Server 2022. If the updates are not available, you may need to disable TLS 1.3 on Windows Server 2022 before installing the head node as a workaround. This is a known issue in th release note.

    0 comments No comments