Share via

HCI Registration failed. Error: Cannot bind argument to parameter 'Path' because it is null

Jimenez, Ivan 0 Reputation points
2025-11-21T00:44:48.82+00:00

I'm deploy Azure local 24h2 509 3 nodes switchless, validations were passed but now deployment process failed with the next error:

  • Failed to create deployment settings. Validation status is {Status=, Steps=null}. Deployment Status is {Status=Error, Steps={Name=Deploy Azure Stack HCI, Description=Deploy the Azure Stack HCI system., FullStepIndex=0, StartTimeUtc=2025-11-11T12:30:27, EndTimeUtc=2025-11-20T21:21:16, Status=Error, Exception=Type 'RegisterStamptoAzure' of Role 'ArcIntegration' raised an exception: HCI Registration failed. Error: Cannot bind argument to parameter 'Path' because it is null. Command Arguments ------- --------- {}
Azure Local
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ankit Yadav 6,345 Reputation points Microsoft External Staff Moderator
    2025-11-21T12:48:53.19+00:00

    Hello @Jimenez, Ivan ,

    I understand why you’re confused even if all validations passed, why would registration still fail? But yes, it can happen and rest assured I'll try to help you out with the mitigation for it.There is an older thread for similar issue for similar error message:
    https://learn.microsoft.com/en-us/answers/questions/2239808/azure-local-deploy-register-with-azure-failing and the issue was due to bad configuration for proxy settings.Can you please give it a try once for your environment and let us know if it still fails.

    Reference: https://learn.microsoft.com/en-us/azure/azure-local/manage/configure-proxy-settings-23h2?view=azloc-previous#configure-proxy-settings-for-environment-variables

    If above solution doesn't apply for your case, kindly review and answer us (this will help us to pin-point the root cause behind the issue):

    1. Please verify and confirm that all the pre-requisites have been met for your Azure Local cluster listed out here in the tables: https://learn.microsoft.com/en-us/azure/azure-local/deploy/deployment-prerequisites?view=azloc-previous#review-requirements-and-complete-prerequisites1. Please confirm that you are doing registration without Azure Arc Gateway (this method for Azure Local registration : https://learn.microsoft.com/en-us/azure/azure-local/deploy/deployment-without-azure-arc-gateway?view=azloc-previous&tabs=script&pivots=register-proxy)
    2. All permission for the LCM user are configured properly and it's working fine (ie you are able to login using them) on all the nodes (see: https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/LCM/access-denied-lcm-user.md#issue-validation)
    3. Make sure all the nodes are having only below versions for these modules:
      For Az.Accounts only 4.0.2, for Az.Resources only 7.8.0 and Az.StackHCI only 2.5.0.

    If you see any discrepancies among the nodes, kindly uninstall the module with all the versions of it and then install the required version only.

    Sample Powershell command to remove all versions of the module:

       Uninstall-Module Az.stackhci -AllVersions

    To install the required version:

       Install-Module Az.stackhci -RequiredVersion 2.5.0

    Let me know if these steps help out to fix the registration issue.

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.