locked
Deployment '60.140.141 - (ACS) Configure Azure-consistent Storage.' RRS feed

  • Question

  • Hi, i am Having the exact same error

    '60.140.141 - (ACS) Configure Azure-consistent Storage.' is 'Error':

    How did you solve it ?

    VERBOSE: 1> [ACS:Register] New-SessionWrapper retry: 0, RetryTimes: 3, RetrySleepTimeInSeconds: 5 - 10/21/2017 10:27:42 AM
    VERBOSE: 1> [ACS:Register] Session is created, computer AzS-WAS01.azurestack.local - 10/21/2017 10:27:53 AM
    WARNING: 1> Task: Invocation of interface 'Register' of role 'Cloud\Fabric\ACS' failed:

    Type 'Register' of Role 'ACS' raised an exception:

    An error occurred while trying to make an API call to Resource Manager: Unable to connect to the remote server

    Additional details:
    at Load-ResourceManagerClientCertificate, C:\Program Files\WindowsPowerShell\Modules\Microsoft.AzureStack.Solution.Deploy.Fabric\AzureStackInstaller\Utils\XRP\ResourceProvider.ps1: line 936
    at Register-ACSFarm, C:\Program Files\WindowsPowerShell\Modules\Microsoft.AzureStack.Solution.Deploy.Fabric\AzureStackInstaller\Utils\XRP\ResourceProvider.ps1: line 1143 - 10/21/2017 10:28:14 AM
    Invoke-EceAction : 1> Task: Invocation of interface 'Register' of role 'Cloud\Fabric\ACS' failed:
    Type 'Register' of Role 'ACS' raised an exception:
    An error occurred while trying to make an API call to Resource Manager: Unable to connect to the remote server
    Additional details:
    at Load-ResourceManagerClientCertificate, C:\Program Files\WindowsPowerShell\Modules\Microsoft.AzureStack.Solution.Deploy.Fabric\AzureStackInstaller\Utils\XRP\ResourceProvider.ps1: line 936
    at Register-ACSFarm, C:\Program Files\WindowsPowerShell\Modules\Microsoft.AzureStack.Solution.Deploy.Fabric\AzureStackInstaller\Utils\XRP\ResourceProvider.ps1: line 1143 - 10/21/2017 10:28:14 AM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:661 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OperationStopped: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : An error occurred while trying to make an API call to Resource Manager: Unable to connect to the remote server
    Additional details: ,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: 1> Step: Status of step '60.140.141 - (ACS) Configure Azure-consistent Storage.' is 'Error'. - 10/21/2017 10:28:14 AM
    VERBOSE: 1> Checking if any of the in progress steps are complete. The following steps are currently in progress: '60.140.141'. - 10/21/2017 10:28:14 AM
    VERBOSE: 1> Action: Action plan 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' failed. Finish running all steps that are currently in progress before exiting. - 10/21/2017 10:28:14 AM
    VERBOSE: 1> Draining all steps that are still in progress. The following steps are still in progress or just completed: '60.140.141'. - 10/21/2017 10:28:14 AM
    VERBOSE: 1> Action: Action plan 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' failed. - 10/21/2017 10:28:14 AM
    Invoke-EceAction : 1> Action: Invocation of step 60.140.141 failed. Stopping invocation of action plan. - 10/21/2017 10:28:14 AM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:661 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-Phase5-ConfigureWASAndCreateStorageAccounts' is 'Error'. - 10/21/2017 10:28:14 AM
    COMPLETE: Task Cloud - Deployment-Phase5-ConfigureWASAndCreateStorageAccounts
    VERBOSE: 1> Task: Status of action 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' of role 'Cloud' is 'Error'. - 10/21/2017 10:28:14 AM
    WARNING: 2> Task: Invocation of interface 'Migrate' of role 'Cloud\Fabric\VirtualMachines' failed:

    Type 'Migrate' of Role 'VirtualMachines' raised an exception:

    Failed to register cluster 'S-Cluster' with compute controller. Operation failed with: A WebException occurred while sending a RestRequest. WebException.Status: ConnectFailure.
    Command        Arguments
    -------        ---------
    Add-CpiObjects {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ErrorAction=Stop, Verbose=True}
                   {}
    <ScriptBlock>  {CloudEngine.Configurations.EceInterfaceParameters}
    <ScriptBlock>  {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceInterfaceParameters, 1011101c-...

    at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 59
    at Add-CpiObjects, C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1: line 1236
    at Migrate, C:\CloudDeployment\Classes\VirtualMachines\VirtualMachines.psm1: line 46
    at <ScriptBlock>, <No file>: line 18
    at <ScriptBlock>, <No file>: line 16 - 10/21/2017 10:34:27 AM
    WARNING: 2> Task: Retrying interface 'Migrate' of role 'Cloud\Fabric\VirtualMachines'... - 10/21/2017 10:34:27 AM
    VERBOSE: 2> Task: Running interface 'Migrate' of role 'Cloud\Fabric\VirtualMachines'. Attempt #2. totalRetries = 2 (Retry 1 of 2.) - 10/21/2017 10:34:27 AM
    STARTING: Task Cloud\Fabric\VirtualMachines - Migrate
    Saturday, October 21, 2017 1:02 PM

Answers

  • Hello Saul,

    Just an FYI – We’ve had a couple ASDK Customers get past the deployment at or around 60.140.14X by redeploying from scratch.  We have customer log file and working on finding Root Cause and resolution.

    For now, you may be able to get past by downloading a fresh CloudBuilder.vhdx and redeploying from scratch.  

           

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

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

          

     Thanks


    Gary Gallanes

    Monday, October 30, 2017 5:26 PM

All replies

  • Hey,

    In my case I suspected it was a timeout issue so I blew it away and reinstalled which worked fine second time round. Not too helpful I know.

    With the info Gary provided I would now try one of two things. The first would be jumping on to the offending VM and unregistering it from the domain and then rerunning the deployment or assuming that the step that is now failing to run actually completed successfully it just took longer than expected and so use the powershell Gary provided to jump forward a single step and re-running. The issue I guess could be that some parts of step did not complete so it's a little risky. Given how long it takes to deploy to get to step 60 I'd be tempted to try this.

    Cheers

    Charlie

    Tuesday, October 24, 2017 8:11 AM
  • Hello,

    We are currently investigating deployment failure at or around step 60.140.14X in ASDK 1.0.170928.3.  We need to collect the logs files to provider fix or workaround as we have yet to reproduce this error in our Labs.

     

    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. 

     

    Please include the following in the body of the email

     

    Build/Version:  

    Get-Content"C:\CloudDeployment\Configuration\Version\version.xml"  

     

    Directory type:  

    Azure AD or ADFS 

     

    Network:  

    Static or DHCP.  

     

    The method used to access the Internet:  

    NAT, Web Proxy, Transparent  Proxy, DMZ or Closed 

     

    BareMetal or Nested Hyper-V: 

     

        

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

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

        

     Thanks


    Gary Gallanes

    Friday, October 27, 2017 12:54 AM
  • Hello Saul,

    Just an FYI – We’ve had a couple ASDK Customers get past the deployment at or around 60.140.14X by redeploying from scratch.  We have customer log file and working on finding Root Cause and resolution.

    For now, you may be able to get past by downloading a fresh CloudBuilder.vhdx and redeploying from scratch.  

           

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

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

          

     Thanks


    Gary Gallanes

    Monday, October 30, 2017 5:26 PM