Microsoft HPC Pack 2019 , wont start HPC Cluster manager

Samala, Kiran 0 Reputation points
2026-08-12T07:20:25.6933333+00:00

Failed to initialize collector. Retrying in 60 seconds. System.Net.Http.HttpRequestException: Response status code does not indicate success: 503 (Service Unavailable).

at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()

at Microsoft.Hpc.Monitoring.ManagementRestClient.<>c__DisplayClass19_0.<<GetApiCallAsync>b__0>d.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at Microsoft.Hpc.Monitoring.MonitoringRetryModule.<RetryTemporaryFailAsync>d__8`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at Microsoft.Hpc.Monitoring.MonitoringRetryModule.<RetryTemporaryFailAsync>d__8`1.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at Microsoft.Hpc.Monitoring.HpcRestMonitoringStore.<GetMetricsAsync>d__10.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at Microsoft.Hpc.Monitoring.HpcRestMonitoringStore.GetMetrics(Nullable`1 target)

at Microsoft.Hpc.Monitoring.MetricCollector.Initialize()

Windows for business | Windows Server | User experience | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Allan Solomon Mejia 7,915 Reputation points
    2026-08-13T21:51:40.96+00:00

    Hello @Samala, Kiran

    The 503 Service Unavailable is coming from the HPC monitoring REST service, so this looks more like a head-node monitoring/service issue than an HPC Cluster Manager client problem.

    On the head node, first check that the HPC services are running, particularly HpcMonitoringServer, and review the HPC-related Windows Event Logs for errors occurring when Cluster Manager starts.

    You can quickly check the services with:

    Get-Service *Hpc* | Select Name, Status, StartType

    Restarting the failed HPC monitoring service may restore Cluster Manager temporarily, but if the 503 returns, check the monitoring service/database connectivity and certificates rather than repeatedly restarting the client.

    Also confirm your HPC Pack 2019 version. Microsoft currently provides HPC Pack 2019 Update 3, with subsequent fixes, so if you're running the original 2019 release or an older update, bringing the cluster to a supported/current build should be considered.

    If you can share the output of Get-Service Hpc and your HPC Pack build number, we can narrow down which service is generating the 503.

    Reference: Microsoft – HPC Pack 2019 Update 3 https://www.microsoft.com/en-us/download/details.aspx?id=108564

    Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.