locked
Azurestack TP2 install failing . Invocation of step 60.120 failed RRS feed

  • Question

  • Am trying to install TP2 and have encountered an error which occurs after the line :

    VERBOSE: 1> 3> Task: Status of action 'Deployment-Phase4-DeployADFS' of role 'Cloud' is 'Success'. - 12/6/2016 5:17:43
    AM
    VERBOSE: 1> Step: Status of step 'Phase 4 - ConfigureVMs-Part2' is 'Error'. - 12/6/2016 5:17:43 AM
    Invoke-EceAction : 1> Action: Invocation of step 60.120 failed. Stopping invocation of action plan. - 12/6/2016
    5:17:43 AM
    At line:6 char:2
    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.16  ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: 1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'. - 12/6/2016 5:17:43 AM
    COMPLETE: Task Cloud - Deployment-Phase2-ConfigureStack
    VERBOSE: 1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'. - 12/6/2016 5:17:43
    AM
    VERBOSE: Step: Status of step 'Phase 2 - ConfigureVMs' is 'Error'. - 12/6/2016 5:17:43 AM
    Invoke-EceAction : Action: Invocation of step 60 failed. Stopping invocation of action plan. - 12/6/2016 5:17:43 AM
    At line:6 char:2
    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.16  ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    Full deployment log - https://access.acronis.com/t/rco5mep0

    Any ideas? 

    Wednesday, December 7, 2016 10:55 AM

Answers

All replies

  • Hello,

    We are researching on the query and would get back to you soon on this.

    I apologize for the inconvenience and appreciate your time and patience in this matter.

    Regards,

    Sadiqh

    Wednesday, December 7, 2016 7:42 PM
  • Hi,

    Can you try re-running the install using the -rerun flag?

    Thanks

    Daniel.

    Friday, December 9, 2016 7:49 PM
  • I've tried to use rerun flag and run it from scratch 3 times. And got the same error.
    Monday, December 12, 2016 8:46 AM
  • Hi,

    We see only one log file, which is not sufficient to discover the root cause for this problem.

    We need log files from XRP vm (C:\MASLogs folder).

    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 4:52 PM
  • I have the exact same error. Is there a resolution for this yet?

    Charles


    Charles A. Windom Sr.

    Wednesday, December 14, 2016 2:32 AM
  • I sent my zipped logfiles to  ascustfeedback@microsoft.com

    Charles


    Charles A. Windom Sr.

    Wednesday, December 14, 2016 3:37 AM
  • Hi I've run deployment from scratch and got different output

    VERBOSE: 1> 1> Task: Status of action 'Deployment-Phase5-CreateStorageAccounts' of role 'Cloud' is 'Success'. -
    12/13/2016 1:56:58 AM
    VERBOSE: 1> Step: Status of step 'Phase 5 - DeployServices' is 'Error'. - 12/13/2016 1:56:58 AM
    Invoke-EceAction : 1> Action: Invocation of step 60.140 failed. Stopping invocation of action plan. - 12/13/2016
    1:56:58 AM
    At line:6 char:2
    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.16  ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: 1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'. - 12/13/2016 1:56:58 AM
    COMPLETE: Task Cloud - Deployment-Phase2-ConfigureStack
    VERBOSE: 1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'. - 12/13/2016 1:56:58
    AM
    VERBOSE: Step: Status of step 'Phase 2 - ConfigureVMs' is 'Error'. - 12/13/2016 1:56:58 AM
    Invoke-EceAction : Action: Invocation of step 60 failed. Stopping invocation of action plan. - 12/13/2016 1:56:58 AM
    At line:6 char:2
    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.16  ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet


    Logs from deployment and from machine MAS-Xrp01 and MAS-WASP01 https://access.acronis.com/t/zfglycwd

     
    Thursday, December 15, 2016 8:17 AM
  • Hi Michael,

    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

    Thursday, December 15, 2016 4:33 PM
  • You can download all logs by this link https://access.acronis.com/t/zfglycwd
    Monday, December 19, 2016 8:01 AM
  • Hi Michael,

    Our security restricts us from receiving log files via email or Workspaces other than our own.

     

    To continue our investigation we’ll need to analyze the log files under C:\CloudDeployment\Logs.

    Please email us at ascustfeedback@microsoft.com and we will set up a workspace where you can upload the logs.

    NOTE - Please use a Work, Organizational or Student email address when contacting ascustfeedback@microsoft.com


    Gary Gallanes

    Tuesday, December 20, 2016 11:44 PM
  • From ascustfeedback@microsoft.com I've got response:
    Thank you for your Email.  I am out of the office on holiday and will be returning on Turesday January 3rd

    What I can do now?


    Tuesday, December 27, 2016 3:12 PM
  • I've trying to restart deployment many times, but always got the same error

    2016-12-13 01:49:39 Verbose  1> 2> Registering virtual machine 'MAS-NC01' with compute controller.
    2016-12-13 01:50:02 Verbose  1> 2> Successfully registered virtual machine 'MAS-NC01' with cluster resource id equal to 'c6c280f5-3c43-4154-9e37-0ab34fda4024' with compute controller.
    2016-12-13 01:50:02 Verbose  1> 2> Registering virtual machine 'MAS-SLB01' with compute controller.
    2016-12-13 01:50:12 Verbose  1> 2> Successfully registered virtual machine 'MAS-SLB01' with cluster resource id equal to '3227cc88-2d7b-4bc0-939c-aabe134e583c' with compute controller.
    2016-12-13 01:50:12 Verbose  1> 2> Registering virtual machine 'MAS-Gwy01' with compute controller.
    2016-12-13 01:50:23 Verbose  1> 2> Successfully registered virtual machine 'MAS-Gwy01' with cluster resource id equal to '2fc24b21-1473-420b-8a1e-10b9a1a1dabc' with compute controller.
    2016-12-13 01:50:23 Verbose  1> 2> Registering virtual machine 'MAS-Con01' with compute controller.
    2016-12-13 01:50:33 Verbose  1> 2> Successfully registered virtual machine 'MAS-Con01' with cluster resource id equal to 'ca0c009b-59fc-41df-80cd-82ed195a784c' with compute controller.
    2016-12-13 01:50:33 Verbose  1> 2> Registering virtual machine 'MAS-ASql01' with compute controller.
    2016-12-13 01:50:43 Verbose  1> 2> Successfully registered virtual machine 'MAS-ASql01' with cluster resource id equal to '60f5add4-ee0b-42a7-a388-0b62093ccb7e' with compute controller.
    2016-12-13 01:50:43 Verbose  1> 2> Registering virtual machine 'MAS-SUS01' with compute controller.
    2016-12-13 01:50:53 Verbose  1> 2> Successfully registered virtual machine 'MAS-SUS01' with cluster resource id equal to 'b6e72d38-2d9e-446b-a57f-791f2de00ed7' with compute controller.
    2016-12-13 01:50:53 Verbose  1> 2> Registering virtual machine 'MAS-WAS01' with compute controller.
    2016-12-13 01:51:03 Verbose  1> 2> Successfully registered virtual machine 'MAS-WAS01' with cluster resource id equal to '5a543ef8-31b5-44c8-916a-dfd6a3f8ed34' with compute controller.
    2016-12-13 01:51:03 Verbose  1> 2> Registering virtual machine 'MAS-WASP01' with compute controller.
    2016-12-13 01:51:13 Error    1> 2> Task: Invocation of interface 'Migrate' of role 'Cloud\Fabric\VirtualMachines' failed: 
    
    Function 'Add-CpiObjects' in module 'Roles\VirtualMachine\VirtualMachine.psd1' raised an exception:
    
    Failed to register virtual machine 'MAS-WASP01' with compute controller. Operation failed with: Exception calling "GetResult" with "0" argument(s): "MakeReservation VM:f628238f-dd71-4e4f-af4c-7761120f1e52 Cluster:S-Cluster"
    At C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1:2134.
    +         $eceVm.Name
    at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 52
    at Add-CpiObjects, C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1: line 2134
    at <ScriptBlock>, <No file>: line 18
    2016-12-13 01:51:13 Verbose  1> 2> Step: Status of step '(CPI) Migrate Created VMs, Hosts, and Cluster to CPI' is 'Error'.
    

    Tuesday, December 27, 2016 3:16 PM
  • Hi Michael,

    I'm currently reviewing your logs and will get back to you soon.

    Thanks 


    Gary Gallanes

    Friday, December 30, 2016 8:30 PM
  • Michael,

    We have seen a similar issue involving the Time Zone settings that'll cause VM registration to compute cluster to fail.

    Try setting time zone to UTC in the server BIOS and OS and redeploy using the -rerun flag.

    Thanks


    Gary Gallanes

    Saturday, December 31, 2016 12:13 AM
  • I've tried to change the time on the host machine to UTC (in BIOS I don't have any setting for timezone, only local time) and start deploy from scratch. But all created VM have time UTC - 8 and host machine can't joint to the newly created domain. How I cam change this behavior? How can I change default timezone for newly created VM?




    Thursday, January 5, 2017 8:55 AM
  • Hi Michael,

    There is a known 'Time-Zone' issue affecting deployments in certain regions that should be resolved in the next refresh release.  

    Thanks,


    Gary Gallanes

    Monday, January 9, 2017 7:45 PM
  • Hi when this release will be avialible for download?
    Tuesday, January 10, 2017 8:25 AM
  • Hi Michael,<o:p></o:p>

    The release date hasn't been announced for the upcoming refresh build.  <o:p></o:p>

    I do know it is getting very close and really appreciate your patience. 

    Thanks,



    Gary Gallanes

    Thursday, January 12, 2017 12:06 AM
  • 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:16 PM