Forum Discussion

MattENZ's avatar
MattENZ
Tin Contributor
Jul 22, 2026

Cannot run "Get-SolutionUpdate" or "Get-SolutionUpdateEnvironment" after updating to 2604

My Azure Local environment had been a bit out of date for the last few months so I was catching it up with the updates, stepping from 2602 to 2603 and then to 2604 last night. Since that update, when I run "Get-SolutionUpdate" or "Get-SolutionUpdateEnvironment" the command hangs for a few minutes and then eventually returns with something like the following:

get-solutionUpdate : A WebException occurred while sending a RestRequest. WebException.Status: SendFailure on
https://FQDN:4900/providers/Microsoft.Update.Admin/updateLocations?api-version=2022-08-01
    + CategoryInfo          : ConnectionError: (:) [Get-SolutionUpdate], SendFailureException
    + FullyQualifiedErrorId : SendFailureException,Microsoft.AzureStack.Lcm.PowerShell.GetSolutionUpdateCmdlet

get-solutionUpdate : Object reference not set to an instance of an object.
    + CategoryInfo          : InvalidOperation: (:) [Get-SolutionUpdate], NullReferenceException
    + FullyQualifiedErrorId : NullReferenceException,Microsoft.AzureStack.Lcm.PowerShell.GetSolutionUpdateCmdlet

I have tried https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Update/Get-SolutionUpdate-GatewayTimeout.md to try resolve it as it seemed similar but it hasn't helped. Any idea what might be going on?

azure local

2 Replies

  • Jamony's avatar
    Jamony
    MCT
    Jul 24, 2026

    The SendFailure is important. It means the cmdlet cannot complete its HTTPS request to the clustered Azure Stack HCI Update Service on port 4900; the NullReferenceException is usually a follow-on because no response object was returned. Since the GatewayTimeout procedure did not help, run Get-ActionPlanInstances and confirm it responds quickly. If it stalls, move the Azure Stack HCI Orchestrator Service Cluster Group. Next confirm the Azure Stack HCI Update Service Cluster Group is Online, note its owner node, and test DNS resolution and TCP 4900 to the reported FQDN from every node. On the owner, review the Application log for AzureStack Agent Lifecycle Agent events, especially Update Service termination or memory-limit errors. Move the Update Service cluster group once and retest. If the endpoint still fails, collect diagnostic logs and open Microsoft support with UTC timestamps; 2604 release notes do not list this exact error as a known issue.

  • Kidd_Ip's avatar
    Kidd_Ip
    MVP
    Jul 24, 2026

    After updating to build 2604, the Get-SolutionUpdate and Get-SolutionUpdateEnvironment cmdlets can fail with SendFailure or NullReferenceException errors if the update orchestrator or cluster update resources are unhealthy, learn.microsoft.com/en-us/azure/azure-local/update/update-troubleshooting-23h2?view=azloc-2606