locked
Azure Stack TP2 install fails, Step 16, with inconsistant results RRS feed

  • Question

  • Initially I attempted the deployment with a slightly earlier build of TP2, ran into an issue late in the deployment that required the latest release to fix. I (re-)downloaded the bits on Dec 1 and restarted the whole process, on the first attempt it failed during step 16 complaining that it couldn't create a DNS record (which when I looked existed on the VM DC). I then reset / refreshed everything and started over and now it failing on Step 16 as shown below, can anyone offer some advice on how to get past this?

    COMPLETE: Task Cloud\Infrastructure\Domain - Configure

    VERBOSE: Task: Task completed. - 12/5/2016 12:57:20 PM

    COMPLETE: Step 15 - (DEP) Configure the Domain server

    VERBOSE: Step: Status of step '(DEP) Configure the Domain server' is 'Success'. - 12/5/2016 12:57:20 PM

    STARTING: Step 16 - (DEP) Configure Physical Machine

    VERBOSE: Step: Running step 16 - (DEP) Configure Physical Machine - 12/5/2016 12:57:20 PM

    STARTING: Task Cloud\Infrastructure\BareMetal - Configure

    VERBOSE: Task: Running interface 'Configure' of role 'Cloud\Infrastructure\BareMetal'. - 12/5/2016 12:57:20 PM

    VERBOSE: Interface: Path to module: C:\CloudDeployment\Roles\PhysicalMachines\PhysicalMachines.psd1 - 12/5/2016 12:57:20 PM

    VERBOSE: Interface: Running interface Configure (Roles\PhysicalMachines\PhysicalMachines.psd1, ConfigurePhysicalMachines) - 12/5/2016 12:57:20 PM

    VERBOSE: Found AD running on MAS-DC01 - 12/5/2016 12:57:50 PM

    VERBOSE: The server 'W600AZSD01' is already joined to a domain. - 12/5/2016 12:57:50 PM

    VERBOSE: Adding static route for HNV network - 12/5/2016 12:57:50 PM

    VERBOSE: Find out which NICs are able to connect on each node. - 12/5/2016 12:57:52 PM

    VERBOSE: + W600AZSD01 | Storage1 - 12/5/2016 12:57:52 PM

    VERBOSE: + W600AZSD01 | Deployment - 12/5/2016 12:57:52 PM

    VERBOSE: + W600AZSD01 | Management - 12/5/2016 12:57:52 PM

    VERBOSE: Found AD running on MAS-DC01 - 12/5/2016 12:57:52 PM

    VERBOSE: Registering NIC with DNS W600AZSD01-stor. - 12/5/2016 12:57:55 PM

    VERBOSE: Adding DNS resource record for name 'W600AZSD01-stor' with IP '192.168.100.4' under zone name 'AzureStack.Local' on the domain controller 'MAS-DC01'. - 12/5/2016

    12:57:55 PM

    VERBOSE: Adding record for 'W600AZSD01-stor'. - 12/5/2016 12:57:59 PM

    VERBOSE: Skipping NIC Deployment in W600AZSD01 - 12/5/2016 12:58:00 PM

    VERBOSE: Skipping NIC Management in W600AZSD01 - 12/5/2016 12:58:00 PM

    VERBOSE: Remove existing PS sessions. - 12/5/2016 12:58:00 PM

    VERBOSE: Adding user 'AzureStack\MAS-OpsAdmin' as a local administrator on 'W600AZSD01'. - 12/5/2016 12:58:00 PM


    Invoke-EceAction : Connecting to remote server W600AZSD01 failed with the following error message : Access is denied. For more information, see the

    about_Remote_Troubleshooting Help topic. - 12/5/2016 12:58:02 PM

    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1

    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : OpenError: (W600AZSD01:String) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : AccessDenied,PSSessionStateBroken,CloudEngine.Cmdlets.InvokeCmdlet


    VERBOSE: Adding server 'W600AZSD01' to security group 'MAS-Storage'. - 12/5/2016 12:58:04 PM

    VERBOSE: Adding machine 'W600AZSD01' as a member of the group 'MAS-Storage'. - 12/5/2016 12:58:06 PM


    Invoke-EceAction : Task: Invocation of interface 'Configure' of role 'Cloud\Infrastructure\BareMetal' failed:

    Function 'ConfigurePhysicalMachines' in module 'Roles\PhysicalMachines\PhysicalMachines.psd1' raised an exception:

    Cannot validate argument on parameter 'Members'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.

    at <ScriptBlock>, <No file>: line 1 - 12/5/2016 12:58:06 PM

    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1

    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : InvalidData: (:) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.ActiveDirectory.Management.Commands.AddADGroupMember,CloudEngine.Cmdlets.InvokeCmdlet


    VERBOSE: Step: Status of step '(DEP) Configure Physical Machine' is 'Error'. - 12/5/2016 12:58:06 PM


    Invoke-EceAction : Action: Invocation of step 0.16 failed. Stopping invocation of action plan. - 12/5/2016 12:58:06 PM

    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1

    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet


    VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' is 'Error'. - 12/5/2016 12:58:06 PM


    COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetalAndBGPAndNAT


    VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud' is 'Error'. - 12/5/2016 12:58:06 PM

    VERBOSE: Step: Status of step 'Phase 0 - Configure physical machine and external networking' is 'Error'. - 12/5/2016 12:58:06 PM


    Invoke-EceAction : Action: Invocation of step 0 failed. Stopping invocation of action plan. - 12/5/2016 12:58:06 PM

    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1

    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    Wednesday, December 7, 2016 2:32 PM

Answers

  • Hi Alvin,

    Thanks for the log. Can you please try this - rename the workgroup of your computer (from "AZSWRKGRP") to WORKGROUP (all caps ) and call .\installazurestackpoc –rerun?

    The host should domain join and reboot and then continue deployment.   Please make sure you log back in as the domain admin to watch deployment continue (AzureStack\AzureStackAdmin).

     

    If rerun doesn’t work and you run into another error right away, you may need to redeploy from scratch.

    Please let us know if this helps.

    Thanks, Cheng


    Cheng Wei [MSFT] - Posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, December 13, 2016 7:45 PM

All replies

  • Hi Alvin, to get pass this step you can follow the instructions to use "Rerun" here: https://social.msdn.microsoft.com/Forums/azure/en-US/home?forum=AzureStack&announcementId=10babf67-140d-4e43-b15d-8e6f90af2d79

    Please post back if you get stuck at the same point or any other.

    Thanks,

    Walter.

     

    Walter Oliver

    Wednesday, December 7, 2016 8:59 PM
  • With both attempts since downloading the latest distribution, when I attempt a rerun I get the same error at the same point/step. Resetting and restarting the whole install (tried once plus one rerun) resulted in a different initial error and a repeat of the same error.

    Honestly I'm a bit confused about the whole static network question, I have DHCP on the network the host is running on but when I attempted the deployment relying on that, communication with the first (DC) VM never happened, I had to setup the static network to get past that point. Should I retry with this distribution without the static networking?

    ~Alvin

    Thursday, December 8, 2016 2:24 PM
  • Please do try without the static networking

    Walter Oliver

    Thursday, December 8, 2016 4:10 PM
  • I did and got the same error, also attempted the -rerun with same results.

    COMPLETE: Step 15 - (DEP) Configure the Domain server

    VERBOSE: Step: Status of step '(DEP) Configure the Domain server' is 'Success'. - 12/8/2016 9:42:42 AM

    STARTING: Step 16 - (DEP) Configure Physical Machine

    VERBOSE: Step: Running step 16 - (DEP) Configure Physical Machine - 12/8/2016 9:42:42 AM

    STARTING: Task Cloud\Infrastructure\BareMetal - Configure

    VERBOSE: Task: Running interface 'Configure' of role 'Cloud\Infrastructure\BareMetal'. - 12/8/2016 9:42:42 AM

    VERBOSE: Interface: Path to module: C:\CloudDeployment\Roles\PhysicalMachines\PhysicalMachines.psd1 - 12/8/2016 9:42:42 AM

    VERBOSE: Interface: Running interface Configure (Roles\PhysicalMachines\PhysicalMachines.psd1, ConfigurePhysicalMachines) - 12/8/2016 9:42:42 AM

    VERBOSE: Found AD running on MAS-DC01 - 12/8/2016 9:43:11 AM

    VERBOSE: The server 'W600AZSD01' is already joined to a domain. - 12/8/2016 9:43:11 AM

    VERBOSE: Adding static route for HNV network - 12/8/2016 9:43:11 AM

    VERBOSE: Find out which NICs are able to connect on each node. - 12/8/2016 9:43:13 AM

    VERBOSE: + W600AZSD01 | Storage1 - 12/8/2016 9:43:13 AM

    VERBOSE: + W600AZSD01 | Deployment - 12/8/2016 9:43:13 AM

    VERBOSE: + W600AZSD01 | Management - 12/8/2016 9:43:13 AM

    VERBOSE: Found AD running on MAS-DC01 - 12/8/2016 9:43:13 AM

    VERBOSE: Registering NIC with DNS W600AZSD01-stor. - 12/8/2016 9:43:17 AM

    VERBOSE: Adding DNS resource record for name 'W600AZSD01-stor' with IP '192.168.100.4' under zone name 'AzureStack.Local' on the domain controller 'MAS-DC01'. - 12/8/2016

     9:43:17 AM

    VERBOSE: Adding record for 'W600AZSD01-stor'. - 12/8/2016 9:43:22 AM

    VERBOSE: Skipping NIC Deployment in W600AZSD01 - 12/8/2016 9:43:22 AM

    VERBOSE: Skipping NIC Management in W600AZSD01 - 12/8/2016 9:43:22 AM

    VERBOSE: Remove existing PS sessions. - 12/8/2016 9:43:22 AM

    VERBOSE: Adding user 'AzureStack\MAS-OpsAdmin' as a local administrator on 'W600AZSD01'. - 12/8/2016 9:43:22 AM

    Invoke-EceAction : Connecting to remote server W600AZSD01 failed with the following error message : Access is denied. For more information, see the

    about_Remote_Troubleshooting Help topic. - 12/8/2016 9:43:25 AM

    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1

    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : OpenError: (W600AZSD01:String) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : AccessDenied,PSSessionStateBroken,CloudEngine.Cmdlets.InvokeCmdlet

     

    VERBOSE: Adding server 'W600AZSD01' to security group 'MAS-Storage'. - 12/8/2016 9:43:27 AM

    VERBOSE: Adding machine 'W600AZSD01' as a member of the group 'MAS-Storage'. - 12/8/2016 9:43:29 AM

    Invoke-EceAction : Task: Invocation of interface 'Configure' of role 'Cloud\Infrastructure\BareMetal' failed:

    Function 'ConfigurePhysicalMachines' in module 'Roles\PhysicalMachines\PhysicalMachines.psd1' raised an exception:

    Cannot validate argument on parameter 'Members'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.

    at <ScriptBlock>, <No file>: line 1 - 12/8/2016 9:43:29 AM

    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1

    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : InvalidData: (:) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.ActiveDirectory.Management.Commands.AddADGroupMember,CloudEngine.Cmdlets.InvokeCmdlet

     

    VERBOSE: Step: Status of step '(DEP) Configure Physical Machine' is 'Error'. - 12/8/2016 9:43:29 AM

    Invoke-EceAction : Action: Invocation of step 0.16 failed. Stopping invocation of action plan. - 12/8/2016 9:43:29 AM

    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1

    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

     

    VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' is 'Error'. - 12/8/2016 9:43:29 AM

    COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetalAndBGPAndNAT

    VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud' is 'Error'. - 12/8/2016 9:43:29 AM

    VERBOSE: Step: Status of step 'Phase 0 - Configure physical machine and external networking' is 'Error'. - 12/8/2016 9:43:29 AM

    Invoke-EceAction : Action: Invocation of step 0 failed. Stopping invocation of action plan. - 12/8/2016 9:43:29 AM

    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:652 char:1

    + Invoke-EceAction -RolePath Cloud -ActionType Deployment @startHash -V ...

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    Thursday, December 8, 2016 6:01 PM
  • Hi Alvin, could you zip all the log files under C:\CloudDeployment\Logs and make it available to me? You can use my Twitter handle @walterov. Also, please let us know if you did anything other than run the script such as editing files or changing the password.

    Thanks,

    Walter Oliver


    Walter Oliver

    Thursday, December 8, 2016 10:00 PM
  • Hi,

    We need log files under C:\CloudDeployment\Logs.

    Please send us an email at ascustfeedback@microsoft.com, and we will set up a workspace where you can upload the logs for us to analyze.

     

    Regards,

    Pradeep

    Monday, December 12, 2016 5:01 PM
  • I sent the email, I attached the logs which zipped to 24KB, happy to upload or anything else.

    It's worth mentioning that the last 4 attempts have had consistent results with the same error, in the same way, at the same place, both with and without the static networking.

    Regards,

    ~Alvin



    • Edited by Alvin Roe Monday, December 12, 2016 5:33 PM
    Monday, December 12, 2016 5:30 PM
  • Hi Alvin,

    Thanks for the log. Can you please try this - rename the workgroup of your computer (from "AZSWRKGRP") to WORKGROUP (all caps ) and call .\installazurestackpoc –rerun?

    The host should domain join and reboot and then continue deployment.   Please make sure you log back in as the domain admin to watch deployment continue (AzureStack\AzureStackAdmin).

     

    If rerun doesn’t work and you run into another error right away, you may need to redeploy from scratch.

    Please let us know if this helps.

    Thanks, Cheng


    Cheng Wei [MSFT] - Posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, December 13, 2016 7:45 PM
  • I change the workgroup as directed but had to reboot for it to be effective. Upon rebooting the system automatically logged on and continued the installation, it is past the spot that was stopping it.

    Thanks!

    regards,

    ~Alvin

    Wednesday, December 14, 2016 6:08 PM
  • Azure Stack TP3 has been released on March 1, 2017.

    If you are experiencing any issues with the TP2 release, please download and redeploy using the latest Azure Stack POC deployment package

    Please see the updated deployment documentation:

    https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-run-powershell-script

    And updated Azure Stack Docs:

    https://docs.microsoft.com/en-us/azure/azure-stack/

    If you experience any issues with TP3 release, feel free to contact us.

    https://azure.microsoft.com/en-us/blog/hybrid-application-innovation-with-azure-and-azure-stack/

    Wednesday, March 1, 2017 6:50 PM