locked
60.120 seems to be a common issue but does not say how to fix RRS feed

  • Question

  • Hi I have this error that keeps coming up. I have checked that I have a subscription in Azure Public, the subscription is based on both regular CSP subscription and EA subscription. I have read that the 60.120 is related to timezone and I have seen when the InstallAzureStackPoc restarts the first time it reverts to US timezone. I don´t know why anyways I change again to correct one but still fails. Here is the error I get

    VERBOSE: 1> 1> Task: Status of action 'Deployment-Phase4-DeploySRPControllerServices' of role
    'Cloud' is 'Success'. - 10/21/2016 4:48:43 PM
    VERBOSE: 1> Step: Status of step 'Phase 4 - ConfigureVMs-Part2' is 'Error'. - 10/21/2016 4:48:43
    PM
    Invoke-EceAction : 1> Action: Invocation of step 60.120 failed. Stopping invocation of action
    plan. - 10/21/2016 4:48:43 PM
    At line:7 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'. - 10/21/2016 4:48:43
    PM
    COMPLETE: Task Cloud - Deployment-Phase2-ConfigureStack
    VERBOSE: 1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'.
    - 10/21/2016 4:48:43 PM
    VERBOSE: Step: Status of step 'Phase 2 - ConfigureVMs' is 'Error'. - 10/21/2016 4:48:43 PM
    Invoke-EceAction : Action: Invocation of step 60 failed. Stopping invocation of action plan. -
    10/21/2016 4:48:43 PM
    At line:7 char:2
    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.16  ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    When I run InstallAzureStackPoc with the Rerun I get a different error

    VERBOSE: Registering the task with DateTime value for trigger: '10/22/2016 13:17:08'. - 10/22/2016
     1:16:39 PM
    VERBOSE: Waiting for the scheduled task 'NC_Config_20161022-131638' to finish on machine
    'MAS-NC01' for '45' minutes. - 10/22/2016 1:16:40 PM
    Invoke-EceAction : Task: Invocation of interface 'Configure' of role 'Cloud\Fabric\NC' failed:
    Function 'ConfigureNC' in module 'Roles\NC\NC.psd1' raised an exception:
    Task failed with the following error: 'The WinRM client sent a request to the remote
    WS-Management service and was notified that the request size exceeded the configured
    MaxEnvelopeSize quota.'.
    At C:\CloudDeployment\Roles\Common\RoleHelpers.psm1:83.
    +         $status.ErrorMessage
    at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 52
    at Start-PSScriptUsingTask, C:\CloudDeployment\Roles\Common\RoleHelpers.psm1: line 83
    at ConfigureNC, C:\CloudDeployment\Roles\NC\NC.psm1: line 620
    at <ScriptBlock>, <No file>: line 18 - 10/22/2016 1:20:37 PM
    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:353 char:1
    + Invoke-EceAction -RolePath Cloud -ActionType Deployment -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OperationStopped: (Task failed wit...us.ErrorMessage:String) [Invok
       e-EceAction], Exception
        + FullyQualifiedErrorId : Task failed with the following error: 'The WinRM client sent a requ
       est to the remote WS-Management service and was notified that the request size exceeded the c
      onfigured MaxEnvelopeSize quota.'.
    At C:\CloudDeployment\Roles\Common\RoleHelpers.psm1:83.
    +         $status.ErrorMessage,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: Step: Status of step '(NET) Configure NC on VMs' is 'Error'. - 10/22/2016 1:20:37 PM
    Invoke-EceAction : Action: Invocation of step 40.46 failed. Stopping invocation of action plan. -
    10/22/2016 1:20:37 PM

    Anyone have this issue ?



    Gisli Gudmundsson

    Pro: Windows Server 2008, Server Administrator

    TS: Windows Server 2008 Technology Specialist

    My Blog : http://appvid.blogspot.com

    Twitter : #gamertopro

    LinkedIn : Gisli

    Saturday, October 22, 2016 1:21 PM

Answers

All replies

  • Hello,

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

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

     

    Regards,

    Ashok

    Sunday, October 23, 2016 9:46 AM
  • Can I do something to help to figure this out ?


    Gisli Gudmundsson

    Pro: Windows Server 2008, Server Administrator

    TS: Windows Server 2008 Technology Specialist

    My Blog : http://appvid.blogspot.com

    Twitter : #gamertopro

    LinkedIn : Gisli

    Sunday, October 23, 2016 8:20 PM
  • I am also having this issue when installing Azure Stack. What should I do to solve this issue?? If possible, contact me about it.

    Tuesday, November 8, 2016 5:40 PM
  • Any news on this, I´m really looking forward to try Azure Stack, it´s like waiting for a new car from a factory.


    Gisli Gudmundsson

    Pro: Windows Server 2008, Server Administrator

    TS: Windows Server 2008 Technology Specialist

    My Blog : http://appvid.blogspot.com

    Twitter : #gamertopro

    LinkedIn : Gisli

    Monday, November 14, 2016 10:28 PM
  • Hi Gisli,

    Are you using DHCP for the PoC-Host. If so, did you configured a static-DHCP for it?

    Don't I did and I had the strangest errors.

    Erik

    Wednesday, November 16, 2016 7:11 AM
  • Hi Gisli, 

    I had this error. I recommend you trace it back to the specific step 60.120.x and then re-run from there.

    Re-run like this:

    Import-Module C:\CloudDeployment\CloudDeployment.psd1 -Force

    Import-Module C:\CloudDeployment\ECEngine\EnterpriseCloudEngine.psd1 -Force

    Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 60.120.x -Verbose

    I have also seen strange failures due to networking issues on 60.120. If re-running from the specific step does not work try to re-run from the beginning including your network info like this:

    .\InstallAzureStackPOC.ps1 -AdminPassword $adminpass -AADAdminCredential $aadcred -AADDirectoryTenantName X.onmicrosoft.com -NatIPv4Subnet 192.168.5.0/24 -NatIPv4Address 192.168.5.3 -NatIPv4DefaultGateway 192.168.5.1 -EnvironmentDNS 192.168.5.1 -Verbose

    HTH



    My Blog | www.buchatech.com | www.systemcenterportal.com
    If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion in a test environment before implementing!



    Sunday, November 20, 2016 9:40 AM
  • Hi,

    Please try installing using the November refresh of Azure Stack TP2.

    If you still have this failure, you can simply use the -rerun switch to retry. (This is new in the refresh)

    Thanks

    Daniel

    Monday, November 21, 2016 7:50 PM
  • Hello,

    You may have seen that we released a November refresh build of TP2: https://azure.microsoft.com/en-us/blog/new-azure-paas-services-available-for-azure-stack-technical-preview-2-tp2/

    In this release, we fixed a number of deployment issues which were reported.

    If possible, please start another deployment based on this new build (20161104.1), and let us know how it goes.

     

    Regards,

    Pradeep

    Tuesday, November 22, 2016 4:42 PM
  • I'm trying with TP3 but same error. 

    I checked clock, internet connection from

    - physical host 

    - NAT VM 

    but every thing is fine since I'm behind of trans parent proxy where proxy setup is not needed,

    except that installation is failing. 

    Thursday, March 9, 2017 4:12 PM
  • Hello,

    Deployment failure at step 60.120 typically involves a network issue.

    Are you behind a proxy server?

    Please run the following command to validate your network connectivity

    Invoke-command-Computername MAS-WAS01 -ScriptBlock {TNC BING.COM -port 443}

    Invoke-command-Computername MAS-DC01 -ScriptBlock {TNC BING.COM -port 443}

    Invoke-command-Computername MAS-WAS01 -ScriptBlock `

    {tnc portal.local.azurestack.external -port 443}

     

    If TCPtestSuucceeded = True 

    then test a 443 web request to login.windows.net

     

    Invoke-command-Computer MAS-WAS01 -ScriptBlock `

     {Invoke-WebRequest https://login.windows.net/common/.well-known/openid-configuration -UseBasicParsing -Verbose}

      

    If the test returns =  StatusCode:200 StatusDescription:OK

    Redeploy Azure Stack TP3 using the following command:

     

    Import-ModuleC:\CloudDeployment\CloudDeployment.psd1 -Force

    Import-ModuleC:\CloudDeployment\ECEngine\EnterpriseCloudEngine.psd1 -Force

    Invoke-EceAction-RolePath Cloud -ActionType Deployment -Start 60.120 -Verbose

    # and if that fails

    Invoke-EceAction-RolePath Cloud -ActionType Deployment -Start 60 -Verbose

    Let us know how is goes.

     

    TP3 Azure Stack Docs:

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

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

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

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

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

     

    Thanks,


    Gary Gallanes

    Friday, March 10, 2017 3:25 AM