locked
ASDK installation error at step 60 RRS feed

  • Question

  • Hi,   

     

    I'm trying to install Azure Stack Development Kit. The same platform (dell r630) was used to install and test the TP2 and TP3.  

     I face an error at step 60.  I have tried to rerun and to redeploy. 

     Can you help to troubleshoot ?  

     Here is the full error message. I can also share the full logs :  

     

    VERBOSE: 1> Step: Status of step '60.160.163 - (MON) Registers Monitoring Alert Templates' is 

    'Error'. - 7/20/2017 9:44:35 AM 

    VERBOSE: 1> Checking if any of the in progress steps are complete. The following steps are 

    currently in progress: '60.160.163'. - 7/20/2017 9:44:35 AM 

    VERBOSE: 1> Action: Action plan 'Deployment-Phase6-ConfigureMA' failed. Finish running all steps 

    that are currently in progress before exiting. - 7/20/2017 9:44:35 AM 

    VERBOSE: 1> Draining all steps that are still in progress. The following steps are still in 

    progress or just completed: '60.160.163'. - 7/20/2017 9:44:35 AM 

    VERBOSE: 1> Action: Action plan 'Deployment-Phase6-ConfigureMA' failed. - 7/20/2017 9:44:35 AM 

    Invoke-EceAction : 1> Action: Invocation of step 60.160.163 failed. Stopping invocation of action 

    plan. - 7/20/2017 9:44:35 AM 

    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:579 char:5 

    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ... 

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

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

        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet 

      

    VERBOSE: 1> Action: Status of 'Deployment-Phase6-ConfigureMA' is 'Error'. - 7/20/2017 9:44:35 AM 

    COMPLETE: Task Cloud - Deployment-Phase6-ConfigureMA 

    VERBOSE: 1> Task: Status of action 'Deployment-Phase6-ConfigureMA' of role 'Cloud' is 'Error'. - 

    7/20/2017 9:44:35 AM 

    VERBOSE: Step: Status of step '60.160 - PHASE 6 - Install Resource Providers' is 'Error'. - 

    7/20/2017 9:44:35 AM 

    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently 

    in progress: '60.160'. - 7/20/2017 9:44:35 AM 

    VERBOSE: Action: Action plan 'Deployment-Phase2-ConfigureStack' failed. Finish running all steps 

    that are currently in progress before exiting. - 7/20/2017 9:44:35 AM 

    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress 

    or just completed: '60.160'. - 7/20/2017 9:44:35 AM 

    VERBOSE: Action: Action plan 'Deployment-Phase2-ConfigureStack' failed. - 7/20/2017 9:44:35 AM 

    Invoke-EceAction : Action: Invocation of step 60.160 failed. Stopping invocation of action plan. 

    - 7/20/2017 9:44:35 AM 

    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:579 char:5 

    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ... 

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

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

        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet 

      

    VERBOSE: Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'. - 7/20/2017 9:44:35 AM 

    COMPLETE: Task Cloud - Deployment-Phase2-ConfigureStack 

    VERBOSE: Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'. - 

    7/20/2017 9:44:35 AM 

    VERBOSE: Step: Status of step '60 - Phase 2 - ConfigureVMs' is 'Error'. - 7/20/2017 9:44:35 AM 

    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently 

    in progress: '60'. - 7/20/2017 9:44:35 AM 

    VERBOSE: Action: Action plan 'Deployment' failed. Finish running all steps that are currently in 

    progress before exiting. - 7/20/2017 9:44:35 AM 

    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress 

    or just completed: '60'. - 7/20/2017 9:44:35 AM 

    VERBOSE: Action: Action plan 'Deployment' failed. - 7/20/2017 9:44:35 AM 

    Invoke-EceAction : Action: Invocation of step 60 failed. Stopping invocation of action plan. - 

    7/20/2017 9:44:35 AM
    Thursday, July 20, 2017 7:55 AM

Answers

  • Hello Pierre,

    One more thing to check.

    In Azure AD enabled ASDK configurations, we’ve found the majority of deployment failures in and around step 60 are due to ASDK being out of sync with UTC causing AAD authentication to fail.

     

    To check if ASDK time is in sync with UTC run following commands and make sure the difference is + or – a second.

    Example output:

    18:37:02, -00.0104484s

    18:37:04, +00.0019010s

     

    ### Compare AzS-DC01 to UTC

    Invoke-command -Computername AzS-DC01 -ScriptBlock {w32tm /stripchart /Computer:time.windows.com /dataonly}

    ### Compare Host to UTC -

    w32tm /stripchart /Computer:time.windows.com /dataonly

     

    To check if the ASDK-Host & AzS VMs time are in sync with each other.

     

    ### Compare time on Host & AzS VMs

    $VM = Get-VM

    Invoke-command -Computername $VM.name -ScriptBlock {get-date}

    get-date

     

    To set the ASDK-Host & AzS VMs to UTC.

    ### Set time source on AzS-DC01 & Force sync to UTC

    Invoke-command -Computername AzS-DC01 -ScriptBlock {w32tm /config /manualpeerlist:"time.windows.com" /syncfromflags:manual reliable:yes /update}

    # Sync Host and VMs to AzS-DC01

    $VM = Get-VM

    Invoke-command -Computername $VM.name -ScriptBlock {w32tm /config /update /syncfromflags:DOMHIER}

    w32tm/config/update/manualpeerlist:AzS-DC01.azurestack.local/syncfromflags:MANUAL

     

    After setting ASDK to UTC redeploy using -rerun

    cd C:\CloudDeployment\setup

    .\InstallAzureStackPOC.ps1 -rerun

     

    Let us know how it goes.

     Thanks,


    Gary Gallanes


    Tuesday, August 1, 2017 1:56 AM

All replies

  • Hello,

    If you haven't already done so, please try redeploying using the -rerun parameter.

    NOTE: Make sure you are running the deployment as under the AzureStack\AzureStackAdmin account.

       

    cdC:\CloudDeployment

    .\InstallAzureStackPOC.ps1-rerun

     

    If the deployment continues to fail, we’ll require some logs in order to continue troubleshooting. 

    If you could, please email ascustfeedback@microsoft.com  to get a workspace setup to upload your logs. 

      

    Make sure to use a Work, Organizational or Student address when contacting ascustfeedback@microsoft.com and include the thread URL in the subject.

     

    https://aka.ms/GetAzureStackLogs :)

     

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

     

     Thanks,


    Gary Gallanes

    Thursday, July 20, 2017 4:33 PM
  • Hello Pierre,

    Errors at and around step 60 typically involve a networking issue or resource becoming unavailable.

    If your environment has internet access, how does it connect?  NAT, Transparent Proxy, Proxy Server or is it a disconnected deployment?

     

    Can you compare the time between the ASDK-Host and AzS-DC01? Are they out of sync?

    If they are, try resyncing the ASDK-Host and redeploy with the -rerun parameter

     

    ### Update & sync time to DC

    w32tm /config /update /syncfromflags:DOMHIER

     

    ### Redeploy with the -rerun parameter

    cd C:\CloudDeployment

    .\InstallAzureStackPOC.ps1 -rerun

     

    Let us know how it goes.

     

    If that does get you past the error, we look forward to seeing your deployment logs.

    Please email ascustfeedback@microsoft.com  to get a workspace setup to upload your logs. 

      

    Make sure to use a Work, Organizational or Student address when contacting ascustfeedback@microsoft.com and include the thread URL in the subject.

     

    Also see https://aka.ms/GetAzureStackLogs :)

     

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

     

     

     Thanks,


    Gary Gallanes

    Thursday, July 20, 2017 11:50 PM
  • Hello Gary,

    Thank you for replying.
    Despite we are a premier customer, we cannot reach the email "ascustfeedback@microsoft.com"

    "550 5.7.133 RESOLVER.RST.SenderNotAuthenticatedForGroup; authentication required; Delivery restriction check failed because the sender was not authenticated when sending to this group"

    Any tips to reach you ?

    Thanks,

    Monday, July 24, 2017 7:27 AM
  • Hello Pierre,

    We have setup a Workspace for you to upload your logs & sent email with a link and detailed instructions for gathering and uploading your logs.    

    Please see the following link for instructions on using The Log Collection Tool.

    https://aka.ms/GetAzureStackLogs

     

    Example:  Get all logs for past 2 weeks

    Get-AzureStackLog -OutputPath C:\AzureStackLogs -FromDate (Get-Date).AddHours(-336) -ToDate (Get-Date)

     

    We look forward to continuing our investigation just as soon as we receive your logs.

     Thanks,


    Gary Gallanes

    Monday, July 24, 2017 4:38 PM
  • Hello Pierre,

    We've received your logs and currently performing analysis.  We will reply with 'next steps' as soon as our analysis is complete.

     Thanks,


    Gary Gallanes


    Tuesday, July 25, 2017 5:36 PM
  • Thank you Gary.
    Thursday, July 27, 2017 2:23 PM
  • Hi Gary,

    Unable to send email at ascustfeedback@microsoft.com for workspace setup. Looking for your kind response.


    Tariq Younas

    Thursday, July 27, 2017 11:21 PM
  • Pierre,

    Our investigation is pointing to an issue with the XRP VM. Can you check your access to the AzSXRP-01 VM?

    Please run the following commands from an elevated PowerShell session on ASDK-host and post your output back to the Forums.

    Ping azs-xrp01
    Test-netConnection  azs-xrp01 -commonport winrm
    Enter-pssession azs-xrp01
     Thanks,


    Gary Gallanes

    Saturday, July 29, 2017 12:24 AM
  • Hello Pierre,

    One more thing to check.

    In Azure AD enabled ASDK configurations, we’ve found the majority of deployment failures in and around step 60 are due to ASDK being out of sync with UTC causing AAD authentication to fail.

     

    To check if ASDK time is in sync with UTC run following commands and make sure the difference is + or – a second.

    Example output:

    18:37:02, -00.0104484s

    18:37:04, +00.0019010s

     

    ### Compare AzS-DC01 to UTC

    Invoke-command -Computername AzS-DC01 -ScriptBlock {w32tm /stripchart /Computer:time.windows.com /dataonly}

    ### Compare Host to UTC -

    w32tm /stripchart /Computer:time.windows.com /dataonly

     

    To check if the ASDK-Host & AzS VMs time are in sync with each other.

     

    ### Compare time on Host & AzS VMs

    $VM = Get-VM

    Invoke-command -Computername $VM.name -ScriptBlock {get-date}

    get-date

     

    To set the ASDK-Host & AzS VMs to UTC.

    ### Set time source on AzS-DC01 & Force sync to UTC

    Invoke-command -Computername AzS-DC01 -ScriptBlock {w32tm /config /manualpeerlist:"time.windows.com" /syncfromflags:manual reliable:yes /update}

    # Sync Host and VMs to AzS-DC01

    $VM = Get-VM

    Invoke-command -Computername $VM.name -ScriptBlock {w32tm /config /update /syncfromflags:DOMHIER}

    w32tm/config/update/manualpeerlist:AzS-DC01.azurestack.local/syncfromflags:MANUAL

     

    After setting ASDK to UTC redeploy using -rerun

    cd C:\CloudDeployment\setup

    .\InstallAzureStackPOC.ps1 -rerun

     

    Let us know how it goes.

     Thanks,


    Gary Gallanes


    Tuesday, August 1, 2017 1:56 AM