none
Azure Stack TP2 Deployment Error

    Question

  • Hi, I was trying to install Azure Stack TP2 and stuck with below error at step 60, Any clue what caused the issue ?

    Invoke-EceAction : 1> Action: Invocation of step 60.61 failed. Stopping invocation of action plan. - 9/28/2016 9:11:07 PM
    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:353 char:1
    + Invoke-EceAction -RolePath Cloud -ActionType Deployment -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (:) [Invoke-EceAction], Exception
    + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: 1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'. - 9/28/2016 9:11:07 PM
    COMPLETE: Task Cloud - Deployment-Phase2-ConfigureStack
    VERBOSE: 1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'. - 9/28/2016 9:11:07 PM
    VERBOSE: Step: Status of step 'Phase 2 - ConfigureVMs' is 'Error'. - 9/28/2016 9:11:07 PM

    Invoke-EceAction : Action: Invocation of step 60 failed. Stopping invocation of action plan. - 9/28/2016 9:11:07 PM
    At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:353 char:1
    + Invoke-EceAction -RolePath Cloud -ActionType Deployment -Verbose
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (:) [Invoke-EceAction], Exception
    + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet


    DKP

    Wednesday, September 28, 2016 1:48 PM

All replies

  • If you look in the folder named c:\clouddeployment\logs, you'll see some files that begin with Deployment.  If you open the most recent one, you'll find the logs leading up to this.  If you then post the lines leading up to the first instance of "Error" then we might be able to help.
    Wednesday, September 28, 2016 4:16 PM
  • If you look in the folder named c:\clouddeployment\logs, you'll see some files that begin with Deployment.  If you open the most recent one, you'll find the logs leading up to this.  If you then post the lines leading up to the first instance of "Error" then we might be able to help.

    I have exactly the same.. here is the run-up to the error:

    2016-09-28 13:02:52 Error    1> 5> Task: Invocation of interface 'Configure' of role 'Cloud\Fabric\Gateway' failed: 
    
    Function 'ConfigureGwy' in module 'Roles\Gateway\Gateway.psd1' raised an exception:
    
    Connecting to remote server MAS-Gwy01 failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.
    at CreateConfigurationDataObjectConfigurePhase, C:\CloudDeployment\Roles\Gateway\Gateway.psm1: line 363
    at ConfigureGwy, C:\CloudDeployment\Roles\Gateway\Gateway.psm1: line 441
    at <ScriptBlock>, <No file>: line 18
    2016-09-28 13:02:52 Verbose  1> 5> Step: Status of step '(NET) Configure GW VMs' is 'Error'.
    2016-09-28 13:02:52 Error    1> 5> Action: Invocation of step 60.61.95 failed. Stopping invocation of action plan.
    2016-09-28 13:02:52 Verbose  1> 5> Action: Status of 'Deployment-Phase3-DeployGatewayAndIDNS' is 'Error'.
    2016-09-28 13:02:52 Verbose  1> 5> Task: Status of action 'Deployment-Phase3-DeployGatewayAndIDNS' of role 'Cloud' is 'Error'.
    2016-09-28 13:02:54 Verbose  1> 1> Searching resourceId for instance id [133b4690-5c12-44a8-a817-102583e6e7db].
    2016-09-28 13:02:54 Verbose  1> 1> JSON Get [/networkinterfaces]
    2016-09-28 13:02:54 Verbose  1> 1> JSON Get [/LoadBalancers/d6fc9182-9553-4e51-8606-c19e0c4d9fa3]
    2016-09-28 13:02:54 Verbose  1> 1> JSON Get [/NetworkInterfaces/6084f66f-6275-4680-902e-ffd2bf3b9e55]
    2016-09-28 13:02:54 Verbose  1> 1> Configuring port mapping named 'CRPExtension' with ports: '12648' and '12648'; protocol: 'TCP'; and VIP IPv4 address '192.168.102.7'.
    2016-09-28 13:02:54 Verbose  1> 1> JSON Get [/LoadBalancerManager/Config]
    2016-09-28 13:02:54 Verbose  1> 1> JSON Get [/logicalnetworks/f8f67956-3906-4303-94c5-09cf91e7e311]
    2016-09-28 13:02:54 Verbose  1> 1> Getting port profile for [MAS-Xrp01] on [WIN-2CMSNCNV26N]
    2016-09-28 13:02:57 Verbose  1> 1> Searching resourceId for instance id [133b4690-5c12-44a8-a817-102583e6e7db].
    2016-09-28 13:02:57 Verbose  1> 1> JSON Get [/networkinterfaces]
    2016-09-28 13:02:57 Verbose  1> 1> JSON Get [/LoadBalancers/d6fc9182-9553-4e51-8606-c19e0c4d9fa3]
    2016-09-28 13:02:57 Verbose  1> 1> JSON Get [/NetworkInterfaces/6084f66f-6275-4680-902e-ffd2bf3b9e55]
    2016-09-28 13:02:57 Verbose  1> 1> Configuring port mapping named 'TenantExtension' with ports: '12649' and '12649'; protocol: 'TCP'; and VIP IPv4 address '192.168.102.7'.
    2016-09-28 13:02:57 Verbose  1> 1> JSON Get [/LoadBalancerManager/Config]
    2016-09-28 13:02:57 Verbose  1> 1> JSON Get [/logicalnetworks/f8f67956-3906-4303-94c5-09cf91e7e311]
    2016-09-28 13:02:57 Verbose  1> 1> Getting port profile for [MAS-Xrp01] on [WIN-2CMSNCNV26N]
    2016-09-28 13:03:00 Verbose  1> 1> Searching resourceId for instance id [133b4690-5c12-44a8-a817-102583e6e7db].
    2016-09-28 13:03:00 Verbose  1> 1> JSON Get [/networkinterfaces]
    2016-09-28 13:03:00 Verbose  1> 1> JSON Get [/LoadBalancers/d6fc9182-9553-4e51-8606-c19e0c4d9fa3]
    2016-09-28 13:03:00 Verbose  1> 1> JSON Get [/NetworkInterfaces/6084f66f-6275-4680-902e-ffd2bf3b9e55]
    2016-09-28 13:03:00 Verbose  1> 1> Configuring port mapping named 'HealthExtension' with ports: '12650' and '12650'; protocol: 'TCP'; and VIP IPv4 address '192.168.102.7'.
    2016-09-28 13:03:00 Verbose  1> 1> JSON Get [/LoadBalancerManager/Config]
    2016-09-28 13:03:00 Verbose  1> 1> JSON Get [/logicalnetworks/f8f67956-3906-4303-94c5-09cf91e7e311]
    2016-09-28 13:03:00 Verbose  1> 1> Getting port profile for [MAS-Xrp01] on [WIN-2CMSNCNV26N]
    2016-09-28 13:03:02 Verbose  1> 1> Searching resourceId for instance id [133b4690-5c12-44a8-a817-102583e6e7db].
    2016-09-28 13:03:02 Verbose  1> 1> JSON Get [/networkinterfaces]
    2016-09-28 13:03:02 Verbose  1> 1> JSON Get [/LoadBalancers/d6fc9182-9553-4e51-8606-c19e0c4d9fa3]
    2016-09-28 13:03:02 Verbose  1> 1> JSON Get [/NetworkInterfaces/6084f66f-6275-4680-902e-ffd2bf3b9e55]
    2016-09-28 13:03:02 Verbose  1> 1> Interface: Interface Prerequisite completed.
    2016-09-28 13:03:02 Verbose  1> 1> Task: Task completed.
    2016-09-28 13:03:02 Verbose  1> 1> Step: Status of step '(FBI) Deploy Azure Stack Fabric Ring Services - FabricRing PreRequisite' is 'Success'.
    2016-09-28 13:03:02 Verbose  1> 1> Step: Running step 82 - (FBI) Deploy Azure Stack Fabric Ring Services - Deploy Fabric Ring Cluster
    2016-09-28 13:03:02 Verbose  1> 1> Task: Running interface 'Deployment' of role 'Cloud\Fabric\FabricRingServices\FabricRing'.
    2016-09-28 13:03:02 Verbose  1> 1> Interface: Path to module: C:\CloudDeployment\Roles\FabricRing\FabricRing.psd1
    2016-09-28 13:03:02 Verbose  1> 1> Interface: Running interface Deployment (Roles\FabricRing\FabricRing.psd1, Deploy-FabricRing)
    2016-09-28 13:03:08 Warning  1> 1> The names of some imported commands from the module 'FabricRing' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
    2016-09-28 13:03:08 Verbose  1> 1> Copy Azure Stack Installer modules into module path on [MAS-Xrp01.AzureStack.local]
    2016-09-28 13:04:01 Verbose  1> 1> Add account into administrators group
    2016-09-28 13:04:03 Verbose  1> 1> Installing Service Fabric binaries for each computer from machine MAS-Xrp01.AzureStack.local.
    2016-09-28 13:04:08 Verbose  1> 8> & : END on WIN-2CMSNCNV26N as AZURESTACK\AzureStackAdmin
    2016-09-28 13:04:08 Verbose  1> 8> Interface: Interface Prerequisite completed.
    2016-09-28 13:04:08 Verbose  1> 8> Task: Task completed.
    2016-09-28 13:04:08 Verbose  1> 8> Step: Status of step '(Katal) Setup prerequisites for WAS VMs.' is 'Success'.
    2016-09-28 13:04:08 Verbose  1> 8> Step: Running step 102 - (Katal) Setup WAS VMs
    2016-09-28 13:04:08 Verbose  1> 8> Task: Running interface 'Deployment' of role 'Cloud\Fabric\WAS'.
    2016-09-28 13:04:08 Verbose  1> 8> Interface: Path to module: C:\CloudDeployment\Roles\WAS\WAS.psd1
    2016-09-28 13:04:08 Verbose  1> 8> Interface: Running interface Deployment (Roles\WAS\WAS.psd1, DeployWAS)
    2016-09-28 13:04:15 Verbose  1> 8> & : BEGIN on WIN-2CMSNCNV26N as AZURESTACK\AzureStackAdmin
    2016-09-28 13:04:15 Verbose  1> 8> & : Invoking command on "MAS-WAS01" as AzureStack\FabricAdmin
    2016-09-28 13:04:16 Verbose  1> 3> Interface: Interface PreRequisite completed.
    2016-09-28 13:04:16 Verbose  1> 3> Task: Task completed.
    2016-09-28 13:04:16 Verbose  1> 3> Step: Status of step '(FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite' is 'Success'.
    2016-09-28 13:04:16 Verbose  1> 3> Step: Running step 88 - (FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite
    2016-09-28 13:04:16 Verbose  1> 3> Task: Running interface 'Prerequisite' of role 'Cloud\Fabric\FabricRingServices\ASAppGateway'.
    2016-09-28 13:04:16 Verbose  1> 3> Interface: Path to module: C:\CloudDeployment\Roles\FabricRingApplications\FabricRingApplications.psd1
    2016-09-28 13:04:16 Verbose  1> 3> Interface: Running interface Prerequisite (Roles\FabricRingApplications\FabricRingApplications.psd1, PreDeployAppGateway)
    2016-09-28 13:04:22 Warning  1> 3> The names of some imported commands from the module 'FabricRingApplications' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
    2016-09-28 13:04:22 Verbose  1> 3> Prepare the certificate(s) for the application...
    2016-09-28 13:04:27 Verbose  1> 3> Certificate(s) for application generated successfully.
    2016-09-28 13:04:27 Verbose  1> 3> Import certificate(s) to machine(s) [MAS-Xrp01] and update application manifest file...
    2016-09-28 13:04:32 Verbose  1> 3> Finished certificate(s) import on machine(s)[MAS-Xrp01]...
    2016-09-28 13:04:32 Verbose  1> 3> Modify Gateway config setting file on [MAS-Xrp01]
    2016-09-28 13:04:35 Verbose  1> 3> Finished pre deploy AppGateway
    2016-09-28 13:04:36 Verbose  1> 3> Interface: Interface Prerequisite completed.
    2016-09-28 13:04:36 Verbose  1> 3> Task: Task completed.
    2016-09-28 13:04:36 Verbose  1> 3> Step: Status of step '(FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite' is 'Success'.
    2016-09-28 13:04:36 Verbose  1> 3> Step: Running step 89 - (FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite
    2016-09-28 13:04:36 Verbose  1> 3> Task: Running interface 'Prerequisite' of role 'Cloud\Fabric\FabricRingServices\StorageController'.
    2016-09-28 13:04:36 Verbose  1> 3> Interface: Path to module: C:\CloudDeployment\Roles\FabricRingApplications\FabricRingApplications.psd1
    2016-09-28 13:04:36 Verbose  1> 3> Interface: Running interface Prerequisite (Roles\FabricRingApplications\FabricRingApplications.psd1, PreDeployServiceFabricApplication)
    2016-09-28 13:04:41 Warning  1> 3> The names of some imported commands from the module 'FabricRingApplications' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
    2016-09-28 13:04:42 Verbose  1> 3> Prepare the certificate(s) for the application...
    2016-09-28 13:04:47 Verbose  1> 3> Certificate(s) for application generated successfully.
    2016-09-28 13:04:47 Verbose  1> 3> Import certificate(s) to machine(s) [MAS-Xrp01] and update application manifest file...
    2016-09-28 13:04:52 Verbose  1> 3> Finished certificate(s) import on machine(s)[MAS-Xrp01]...
    2016-09-28 13:04:52 Verbose  1> 3> Interface: Interface Prerequisite completed.
    2016-09-28 13:04:52 Verbose  1> 3> Task: Task completed.
    2016-09-28 13:04:52 Verbose  1> 3> Step: Status of step '(FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite' is 'Success'.
    2016-09-28 13:04:52 Verbose  1> 3> Step: Running step 90 - (FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite
    2016-09-28 13:04:52 Verbose  1> 3> Task: Running interface 'Prerequisite' of role 'Cloud\Fabric\FabricRingServices\HealthMonitoring'.
    2016-09-28 13:04:52 Verbose  1> 3> Interface: Path to module: C:\CloudDeployment\Roles\FabricRingApplications\FabricRingApplications.psd1
    2016-09-28 13:04:52 Verbose  1> 3> Interface: Running interface Prerequisite (Roles\FabricRingApplications\FabricRingApplications.psd1, PreDeployServiceFabricApplication)
    2016-09-28 13:04:57 Warning  1> 3> The names of some imported commands from the module 'FabricRingApplications' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
    2016-09-28 13:04:57 Verbose  1> 3> Prepare the certificate(s) for the application...
    2016-09-28 13:05:02 Verbose  1> 3> Certificate(s) for application generated successfully.
    2016-09-28 13:05:02 Verbose  1> 3> Import certificate(s) to machine(s) [MAS-Xrp01] and update application manifest file...
    2016-09-28 13:05:07 Verbose  1> 3> Finished certificate(s) import on machine(s)[MAS-Xrp01]...
    2016-09-28 13:05:07 Verbose  1> 3> Interface: Interface Prerequisite completed.
    2016-09-28 13:05:07 Verbose  1> 3> Task: Task completed.
    2016-09-28 13:05:07 Verbose  1> 3> Step: Status of step '(FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite' is 'Success'.
    2016-09-28 13:05:07 Verbose  1> 3> Step: Running step 91 - (FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite
    2016-09-28 13:05:07 Verbose  1> 3> Task: Running interface 'Prerequisite' of role 'Cloud\Fabric\FabricRingServices\ECE'.
    2016-09-28 13:05:07 Verbose  1> 3> Interface: Path to module: C:\CloudDeployment\Roles\FabricRingApplications\FabricRingApplications.psd1
    2016-09-28 13:05:07 Verbose  1> 3> Interface: Running interface Prerequisite (Roles\FabricRingApplications\FabricRingApplications.psd1, PreDeployServiceFabricApplication)
    2016-09-28 13:05:12 Warning  1> 3> The names of some imported commands from the module 'FabricRingApplications' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
    2016-09-28 13:05:12 Verbose  1> 3> Prepare the certificate(s) for the application...
    2016-09-28 13:05:18 Verbose  1> 3> Certificate(s) for application generated successfully.
    2016-09-28 13:05:18 Verbose  1> 3> Import certificate(s) to machine(s) [MAS-Xrp01] and update application manifest file...
    2016-09-28 13:05:26 Verbose  1> 3> Finished certificate(s) import on machine(s)[MAS-Xrp01]...
    2016-09-28 13:05:26 Verbose  1> 3> Interface: Interface Prerequisite completed.
    2016-09-28 13:05:26 Verbose  1> 3> Task: Task completed.
    2016-09-28 13:05:26 Verbose  1> 3> Step: Status of step '(FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite' is 'Success'.
    2016-09-28 13:05:26 Verbose  1> 3> Step: Running step 92 - (FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite
    2016-09-28 13:05:26 Verbose  1> 3> Task: Running interface 'Prerequisite' of role 'Cloud\Fabric\FabricRingServices\PMM'.
    2016-09-28 13:05:26 Verbose  1> 3> Interface: Path to module: C:\CloudDeployment\Roles\FabricRingApplications\FabricRingApplications.psd1
    2016-09-28 13:05:26 Verbose  1> 3> Interface: Running interface Prerequisite (Roles\FabricRingApplications\FabricRingApplications.psd1, PreDeployServiceFabricApplication)
    2016-09-28 13:05:31 Warning  1> 3> The names of some imported commands from the module 'FabricRingApplications' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
    2016-09-28 13:05:32 Verbose  1> 3> Prepare the certificate(s) for the application...
    2016-09-28 13:05:36 Verbose  1> 3> Certificate(s) for application generated successfully.
    2016-09-28 13:05:36 Verbose  1> 3> Import certificate(s) to machine(s) [MAS-Xrp01] and update application manifest file...
    2016-09-28 13:05:42 Verbose  1> 3> Finished certificate(s) import on machine(s)[MAS-Xrp01]...
    2016-09-28 13:05:42 Verbose  1> 3> Interface: Interface Prerequisite completed.
    2016-09-28 13:05:42 Verbose  1> 3> Task: Task completed.
    2016-09-28 13:05:42 Verbose  1> 3> Step: Status of step '(FBI) Deploy Azure Stack Fabric Ring Controller Services -  Prerequisite' is 'Success'.
    2016-09-28 13:05:42 Verbose  1> 3> Action: Action plan 'Deployment-Phase3-FabricControllerServicesPrerequisites' completed.
    2016-09-28 13:05:42 Verbose  1> 3> Action: Status of 'Deployment-Phase3-FabricControllerServicesPrerequisites' is 'Success'.
    2016-09-28 13:05:42 Verbose  1> 3> Task: Status of action 'Deployment-Phase3-FabricControllerServicesPrerequisites' of role 'Cloud' is 'Success'.
    2016-09-28 13:05:58 Verbose  1> 8> & : END on WIN-2CMSNCNV26N as AZURESTACK\AzureStackAdmin
    2016-09-28 13:05:58 Verbose  1> 8> Interface: Interface Deployment completed.
    2016-09-28 13:05:58 Verbose  1> 8> Task: Task completed.
    2016-09-28 13:05:58 Verbose  1> 8> Step: Status of step '(Katal) Setup WAS VMs' is 'Success'.
    2016-09-28 13:05:58 Verbose  1> 8> Action: Action plan 'Deployment-Phase3-DeployWAS' completed.
    2016-09-28 13:05:58 Verbose  1> 8> Action: Status of 'Deployment-Phase3-DeployWAS' is 'Success'.
    2016-09-28 13:05:58 Verbose  1> 8> Task: Status of action 'Deployment-Phase3-DeployWAS' of role 'Cloud' is 'Success'.
    2016-09-28 13:07:28 Verbose  1> 1> Service fabric cluster and Azure Stack powershell installed on MAS-Xrp01.AzureStack.local
    2016-09-28 13:07:28 Verbose  1> 1> Interface: Interface Deployment completed.
    2016-09-28 13:07:28 Verbose  1> 1> Task: Task completed.
    2016-09-28 13:07:28 Verbose  1> 1> Step: Status of step '(FBI) Deploy Azure Stack Fabric Ring Services - Deploy Fabric Ring Cluster' is 'Success'.
    2016-09-28 13:07:28 Verbose  1> 1> Step: Running step 83 - (FBI) Deploy Admin Extensions for Resource providers
    2016-09-28 13:07:28 Verbose  1> 1> Task: Running interface 'Deployment' of role 'Cloud\Fabric\Extensions'.
    2016-09-28 13:07:28 Verbose  1> 1> Interface: Path to module: C:\CloudDeployment\Roles\Extensions\Extensions.psd1
    2016-09-28 13:07:28 Verbose  1> 1> Interface: Running interface Deployment (Roles\Extensions\Extensions.psd1, Add-Extensions)
    2016-09-28 13:07:32 Verbose  1> 1> Install Extensions
    2016-09-28 13:07:32 Verbose  1> 1> Installing Extension for [NRP]...
    2016-09-28 13:07:32 Verbose  1> 1> Setup Extension: AdminExtension
    2016-09-28 13:07:32 Verbose  1> 1> Generate Certificate for extension if necessary
    2016-09-28 13:07:37 Verbose  1> 1> Generate Certificate for extension finished.
    2016-09-28 13:07:37 Verbose  1> 1> Set up extension on each node
    2016-09-28 13:07:37 Verbose  1> 1> Set up extension on node(s): [MAS-Xrp01.AzureStack.local]
    2016-09-28 13:07:52 Verbose  1> 1> Set up extension on node(s) [MAS-Xrp01.AzureStack.local] finished.
    2016-09-28 13:07:52 Verbose  1> 1> Extension installed.
    2016-09-28 13:07:52 Verbose  1> 1> Installing Extension for [CRP]...
    2016-09-28 13:07:52 Verbose  1> 1> Setup Extension: AdminExtension
    2016-09-28 13:07:52 Verbose  1> 1> Generate Certificate for extension if necessary
    2016-09-28 13:07:56 Verbose  1> 1> Generate Certificate for extension finished.
    2016-09-28 13:07:56 Verbose  1> 1> Set up extension on each node
    2016-09-28 13:07:56 Verbose  1> 1> Set up extension on node(s): [MAS-Xrp01.AzureStack.local]
    2016-09-28 13:08:07 Verbose  1> 1> Set up extension on node(s) [MAS-Xrp01.AzureStack.local] finished.
    2016-09-28 13:08:07 Verbose  1> 1> Extension installed.
    2016-09-28 13:08:07 Verbose  1> 1> Installing Extension for [HRP]...
    2016-09-28 13:08:07 Verbose  1> 1> Setup Extension: AdminExtension
    2016-09-28 13:08:07 Verbose  1> 1> Generate Certificate for extension if necessary
    2016-09-28 13:08:11 Verbose  1> 1> Generate Certificate for extension finished.
    2016-09-28 13:08:11 Verbose  1> 1> Set up extension on each node
    2016-09-28 13:08:11 Verbose  1> 1> Set up extension on node(s): [MAS-Xrp01.AzureStack.local]
    2016-09-28 13:08:22 Verbose  1> 1> Set up extension on node(s) [MAS-Xrp01.AzureStack.local] finished.
    2016-09-28 13:08:22 Verbose  1> 1> Extension installed.
    2016-09-28 13:08:22 Verbose  1> 1> Installing Extension for [SRP]...
    2016-09-28 13:08:22 Verbose  1> 1> Setup Extension: AdminExtension
    2016-09-28 13:08:22 Verbose  1> 1> Generate Certificate for extension if necessary
    2016-09-28 13:08:26 Verbose  1> 1> Generate Certificate for extension finished.
    2016-09-28 13:08:26 Verbose  1> 1> Set up extension on each node
    2016-09-28 13:08:26 Verbose  1> 1> Set up extension on node(s): [MAS-Xrp01.AzureStack.local]
    2016-09-28 13:08:37 Verbose  1> 1> Set up extension on node(s) [MAS-Xrp01.AzureStack.local] finished.
    2016-09-28 13:08:37 Verbose  1> 1> Extension installed.
    2016-09-28 13:08:38 Verbose  1> 1> Interface: Interface Deployment completed.
    2016-09-28 13:08:38 Verbose  1> 1> Task: Task completed.
    2016-09-28 13:08:38 Verbose  1> 1> Step: Status of step '(FBI) Deploy Admin Extensions for Resource providers' is 'Success'.
    2016-09-28 13:08:38 Verbose  1> 1> Action: Action plan 'Deployment-Phase3-FabricRingDeployment' completed.
    2016-09-28 13:08:38 Verbose  1> 1> Action: Status of 'Deployment-Phase3-FabricRingDeployment' is 'Success'.
    2016-09-28 13:08:38 Verbose  1> 1> Task: Status of action 'Deployment-Phase3-FabricRingDeployment' of role 'Cloud' is 'Success'.
    2016-09-28 13:19:08 Verbose  1> 2> Trying to restart Azure consistent-Storage VMs...
    2016-09-28 13:19:08 Verbose  1> 2> Trying to enable WMI firewall
    2016-09-28 13:19:12 Verbose  1> 2> WMI firewall is enabled
    2016-09-28 13:22:04 Verbose  1> 2> Reboot finished.
    2016-09-28 13:22:04 Verbose  1> 2> Interface: Interface Deployment completed.
    2016-09-28 13:22:04 Verbose  1> 2> Task: Task completed.
    2016-09-28 13:22:04 Verbose  1> 2> Step: Status of step '(ACS) Setup Azure-consistent Storage in cluster level.' is 'Success'.
    2016-09-28 13:22:04 Verbose  1> 2> Action: Action plan 'Deployment-Phase3-WOSSDeployment' completed.
    2016-09-28 13:22:04 Verbose  1> 2> Action: Status of 'Deployment-Phase3-WOSSDeployment' is 'Success'.
    2016-09-28 13:22:04 Verbose  1> 2> Task: Status of action 'Deployment-Phase3-WOSSDeployment' of role 'Cloud' is 'Success'.
    2016-09-28 13:22:04 Verbose  1> Step: Status of step 'Phase 3 - ConfigureVMs-Part1' is 'Error'.
    2016-09-28 13:22:04 Error    1> Action: Invocation of step 60.61 failed. Stopping invocation of action plan.
    2016-09-28 13:22:04 Verbose  1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'.
    2016-09-28 13:22:04 Verbose  1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'.
    2016-09-28 13:22:04 Verbose  Step: Status of step 'Phase 2 - ConfigureVMs' is 'Error'.
    2016-09-28 13:22:04 Error    Action: Invocation of step 60 failed. Stopping invocation of action plan.
    


    Wednesday, September 28, 2016 8:36 PM
  • This is a known bug in the way Active Directory is employed within Azure Stack.  We're working on the fix.  In order to get past this, please retry the deployment with the following command in the window which showed the error:

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

    Wednesday, September 28, 2016 10:07 PM
  • Hi Jake,

    Thanks for you reply, find here the error details from Deployment logs:

    2016-09-28 21:48:13 Verbose  Creating a scheduled task trigger on 'MAS-NC01' with '30' seconds delay.
    2016-09-28 21:48:13 Verbose  Registering the task with DateTime value for trigger: '09/28/2016 21:48:43'.
    2016-09-28 21:48:13 Verbose  Waiting for the scheduled task 'NC_Config_20160928-214812' to finish on machine 'MAS-NC01' for '45' minutes.
    2016-09-28 21:50:25 Error    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 client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".'.
    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
    2016-09-28 21:50:25 Verbose  Step: Status of step '(NET) Configure NC on VMs' is 'Error'.
    2016-09-28 21:50:25 Error    Action: Invocation of step 40.46 failed. Stopping invocation of action plan.
    2016-09-28 21:50:25 Verbose  Action: Status of 'Deployment-Phase1-CreateVMs' is 'Error'.
    2016-09-28 21:50:25 Verbose  Task: Status of action 'Deployment-Phase1-CreateVMs' of role 'Cloud' is 'Error'.
    2016-09-28 21:50:25 Verbose  Step: Status of step 'Phase 1 - CreateVMs' is 'Error'.
    2016-09-28 21:50:25 Error    Action: Invocation of step 40 failed. Stopping invocation of action plan.

    Thursday, September 29, 2016 3:34 AM
  • @Deepak_Azure: For this error, please try running this command in the window where the error showed:

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


    This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.

    Thursday, September 29, 2016 5:34 AM
  • @Mahmoud, Following your provided command still getting this below error:

    Creating a scheduled task trigger on 'MAS-NC01' with '30' seconds delay.
    2016-09-29 14:34:07 Verbose  Registering the task with DateTime value for trigger: '09/29/2016 14:34:37'.
    2016-09-29 14:34:07 Verbose  Waiting for the scheduled task 'NC_Config_20160929-143406' to finish on machine 'MAS-NC01' for '45' minutes.
    2016-09-29 14:36:19 Error    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 client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".'.
    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
    2016-09-29 14:36:19 Verbose  Step: Status of step '(NET) Configure NC on VMs' is 'Error'.
    2016-09-29 14:36:19 Error    Action: Invocation of step 40.46 failed. Stopping invocation of action plan.
    2016-09-29 14:36:19 Verbose  Action: Status of 'Deployment-Phase1-CreateVMs' is 'Error'.
    2016-09-29 14:36:19 Verbose  Task: Status of action 'Deployment-Phase1-CreateVMs' of role 'Cloud' is 'Error'.
    2016-09-29 14:36:19 Verbose  Step: Status of step 'Phase 1 - CreateVMs' is 'Error'.
    2016-09-29 14:36:19 Error    Action: Invocation of step 40 failed. Stopping invocation of action plan.

    Thursday, September 29, 2016 6:58 AM
  • I did that and got the following:

    PS C:\CloudDeployment\Configuration> Invoke-EceAction -RolePath Cloud -ActionType deployment -Verbo
    se -Start 60
    VERBOSE: Loading customer configuration.
    VERBOSE: Progress file : 'Progress.deployment.xml'
    Invoke-EceAction : The given key was not present in the dictionary.
    At line:1 char:1
    + Invoke-EceAction -RolePath Cloud -ActionType deployment -Verbose -Sta ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Invoke-EceAction], KeyNotFoundException
        + FullyQualifiedErrorId : System.Collections.Generic.KeyNotFoundException,CloudEngine.Cmdlets
       .InvokeCmdlet

    Thursday, September 29, 2016 8:21 AM
  • I have exactly the same problem from the deployment log

     Installed Windows Fabric binaries for each computer successfully.
    2016-09-29 14:38:44 Verbose  1> 2> Copy Azure Stack Installer modules into module path
    2016-09-29 14:38:45 Error    1> 4> Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\IdentityProvider' failed: 

    Function 'Create-ActiveDirectoryApplication' in module 'Roles\IdentityProvider\IdentityProvider.psd1' raised an exception:

    An error occurred while trying to verify connection to the graph endpoint 'https://login.windows.net/********/.well-known/openid-configuration': 

    FullException: The remote name could not be resolved: 'login.windows.net'
    at Assert-GraphConnection, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 238
    at Get-GraphToken, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 273
    at Update-GraphAccessToken, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 341
    at Initialize-GraphEnvironment, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 169
    at Create-ActiveDirectoryApplication, C:\CloudDeployment\Roles\IdentityProvider\IdentityProvider.psm1: line 51
    at <ScriptBlock>, <No file>: line 18
    2016-09-29 14:38:45 Verbose  1> 4> Step: Status of step '(Katal) Create AzureStack Service Principals' is 'Error'.
    2016-09-29 14:38:45 Error    1> 4> Action: Invocation of step 60.61.93 failed. Stopping invocation of action plan. 

    Tried running redeployment from step 60 but returns exactly the same error, if I run from step 60.61.94 I can continue but errors further down the line appear to relate to this original error.

    Any help appreciated

    Thursday, September 29, 2016 2:17 PM
  • @Jim Sefton: The ActionType parameter is case sensitive. Please specify the parameter as "Deployment", not "deployment".


    This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.

    Thursday, September 29, 2016 2:24 PM
  • @StormRa: What output do you get from running the following commands on the computer that you are deploying Azure Stack on?

    nslookup login.windows.net

    ping www.bing.com


    This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.

    Thursday, September 29, 2016 2:31 PM
  • Hi Mahmoud

    Thanks for any help

    Results as follows


    >nslookup login.windows.net
    DNS request timed out.
        timeout was 2 seconds.
    Server:  UnKnown
    Address:  192.168.200.3

    DNS request timed out.
        timeout was 2 seconds.
    DNS request timed out.
        timeout was 2 seconds.
    *** Request to UnKnown timed-out

    C:\Users\AzureStackAdmin>ping www.bing.com
    Ping request could not find host www.bing.com. Please check the name and try again.

    I only had the one network adaptor enabled as per the pre-req's and let the install do its things regards creating the Hyper-V network adaptors, here is the route table it created, should I modify the route table so the server can access the internet again ?

    Interface List
     14... ......Hyper-V Virtual Ethernet Adapter #2
      6... ......Hyper-V Virtual Ethernet Adapter #3
     16.. ......Microsoft Failover Cluster Virtual Adapter
     11... ......Hyper-V Virtual Ethernet Adapter
      1...........................Software Loopback Interface 1
    ===========================================================================

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0    192.168.200.1    192.168.200.2  65515
              0.0.0.0          0.0.0.0   172.23.103.254   172.23.103.134     25
            127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
            127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
      127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
       172.23.103.128  255.255.255.128         On-link    172.23.103.134    281
       172.23.103.134  255.255.255.255         On-link    172.23.103.134    281
       172.23.103.135  255.255.255.255         On-link    172.23.103.134    281
       172.23.103.255  255.255.255.255         On-link    172.23.103.134    281
        192.168.100.0  255.255.255.224         On-link     192.168.100.2    271
        192.168.100.2  255.255.255.255         On-link     192.168.100.2    271
       192.168.100.31  255.255.255.255         On-link     192.168.100.2    271
        192.168.101.0  255.255.255.192    192.168.200.1    192.168.200.2    271
        192.168.102.0    255.255.255.0    192.168.200.1    192.168.200.2    271
        192.168.105.0  255.255.255.224    192.168.200.1    192.168.200.2    271
        192.168.200.0    255.255.255.0         On-link     192.168.200.2    271
        192.168.200.2  255.255.255.255         On-link     192.168.200.2    271
       192.168.200.18  255.255.255.255         On-link     192.168.200.2    271
      192.168.200.255  255.255.255.255         On-link     192.168.200.2    271
            224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
            224.0.0.0        240.0.0.0         On-link    172.23.103.134    281
            224.0.0.0        240.0.0.0         On-link     192.168.200.2    271
            224.0.0.0        240.0.0.0         On-link     192.168.100.2    271
      255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      255.255.255.255  255.255.255.255         On-link    172.23.103.134    281
      255.255.255.255  255.255.255.255         On-link     192.168.200.2    271
      255.255.255.255  255.255.255.255         On-link     192.168.100.2    271
    ===========================================================================
    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
        192.168.101.0  255.255.255.192    192.168.200.1  Default
              0.0.0.0          0.0.0.0    192.168.200.1   65500
        192.168.102.0    255.255.255.0    192.168.200.1  Default
        192.168.105.0  255.255.255.224    192.168.200.1  Default

    Thursday, September 29, 2016 2:50 PM
  • @Deepak_Azure and @StormRa: I am looking for information that can help with the error conditions that you encountered. I or somebody else may get back to you later.

    This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.


    Thursday, September 29, 2016 3:03 PM
  • That worked and it started again... this time I got this:

    2016-09-29 08:28:32 Verbose  1> 1> Getting port profile for [MAS-Xrp01] on [WIN-2CMSNCNV26N]
    2016-09-29 08:28:33 Error    1> 5> Task: Invocation of interface 'Configure' of role 'Cloud\Fabric\Gateway' failed: 
    
    Function 'ConfigureGwy' in module 'Roles\Gateway\Gateway.psd1' raised an exception:
    
    Connecting to remote server MAS-Gwy01 failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
    at CreateConfigurationDataObjectConfigurePhase, C:\CloudDeployment\Roles\Gateway\Gateway.psm1: line 363
    at ConfigureGwy, C:\CloudDeployment\Roles\Gateway\Gateway.psm1: line 441
    at <ScriptBlock>, <No file>: line 18
    2016-09-29 08:28:33 Verbose  1> 5> Step: Status of step '(NET) Configure GW VMs' is 'Error'.
    2016-09-29 08:28:33 Error    1> 5> Action: Invocation of step 60.61.95 failed. Stopping invocation of action plan.
    2016-09-29 08:28:33 Verbose  1> 5> Action: Status of 'Deployment-Phase3-DeployGatewayAndIDNS' is 'Error'.
    2016-09-29 08:28:33 Verbose  1> 5> Task: Status of action 'Deployment-Phase3-DeployGatewayAndIDNS' of role 'Cloud' is 'Error'.
    2016-09-29 08:28:34 Verbose  1> 1> Searching resourceId for instance id [133b4690-5c12-44a8-a817-102583e6e7db].


    Thursday, September 29, 2016 5:44 PM
  • I would like to level-set on this across the folks that may still have a failed deployment at a particular step.

    First, if you have any deployment issues, please review the following:

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

    That said, if we can understand the following from each of the folks that have replied here so far, we can get you going in the right direction:

    1. What is your current state?

    2. Did you -Rerun without identifying a step?

    3. Did you -Rerun without providing a precise step (precise step example: 60.61.93)?

    4. How many times did you attempt rerun (regardless of #2 and #3 above)?

    -Charles

    PS. In the event that you need to redeploy from scratch (start over), please reference the following article: https://azure.microsoft.com/en-us/documentation/articles/azure-stack-redeploy/ The file referenced (BootMenuNoKVM.ps1) is available from the same AzureStack-Tools repository as the PrepareBootFromVHD.ps1 file.


    Charles Joy [MSFT] http://blogs.technet.com/b/charlesjoy/



    Thursday, September 29, 2016 6:13 PM
    Owner
  • Thanks for your reply Charles,

    To clarify my scenario

    1.Current State, retrying for the second time with fresh Cloudbuilder.vhdx, failed again at exactly the same point step 60.61.93

    2. In my first effort failed on 60.61.93, I retried without identifying a precise step following earlier advice above.

    3. Retried in first effort using a precise step 60.61.93, error in deployment logs referred to not being able to access login.windows.net. I was unsure as to which machine required access, whether one of the stack created VM's or the physical host running the installation script. It appears the host running the installation script needed access to the internet, however after physical server host reboot initiated by install script it could no longer access the internet DNS had been changed to 192.168.200.3 on all network adapters I added login.windows.net to the physical server host file, it failed again now needing access to graph.windows so I added this to the hosts file and run the precise step, it continued for 10 mins or so then failed on couldn't find userrealm "user_realm_discovery_failed: User realm discovery failed"  NAT VM could access the internet fine 

    4. Rerun many times once on generic step 60 and numerous times on precise steps that failed.

    I have retried once on my second attempt at precise point 60.61.93 and fails at this point, the host server can no longer access the internet following the script initial reboot  on the "deployment", " storage" and "management" Hyper-V adaptors all their DNS is 192.168.200.3 which contains no entries regarding external sites error from deployment log pasted below, any advice would be greatly appreciated, Thanks

    Error    1> 4> Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\IdentityProvider' failed: 

    Function 'Create-ActiveDirectoryApplication' in module 'Roles\IdentityProvider\IdentityProvider.psd1' raised an exception:

    An error occurred while trying to verify connection to the graph endpoint 'https://login.windows.net/********/.well-known/openid-configuration': 

    FullException: The remote name could not be resolved: 'login.windows.net'
    at Assert-GraphConnection, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 238
    at Get-GraphToken, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 273
    at Update-GraphAccessToken, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 341
    at Initialize-GraphEnvironment, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 169
    at Create-ActiveDirectoryApplication, C:\CloudDeployment\Roles\IdentityProvider\IdentityProvider.psm1: line 51

     

    Thursday, September 29, 2016 8:35 PM
  • @Deepak_Azure
    On the computer that you are deploying Azure Stack on, you will find a VM with the name MAS-NC01. Please collect all log files with the name deploync*.log under the C:\mocslogs folder in that VM, and send these log files to my email address <firstname>.<lastname>@microsoft.com.

    This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.

    Friday, September 30, 2016 7:27 AM
  • @StormRa
    From the computer that you are deploying Azure Stack on, please collect the following:
    - The output of ipconfig /all
    - The output of tracert 192.168.200.3
    - All *.log files under C:\CloudDeployment\Logs
    You will also find a VM with the name MAS-BGPNAT01 running on this computer. Please collect the output of ipconfig /all on this VM.
    Please send this information to my email address <firstname>.<lastname>@microsoft.com.


    This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.

    Friday, September 30, 2016 7:34 AM
  • do you have more detail on this bug?  i encounted the same issue and steps and i am able to get to the login site. 

    i also have retried number of time and it is still failing at this steps. 

    thanks

    andy 

    Friday, September 30, 2016 7:17 PM
  • @StormRa - Thanks for your response. In addition to what has been requested above, could you please also check that the DNS forwarding is working properly?

    Open DNS on the HOST, attach to the MAS-DC01 VM, and check the DNS forwarders. These should be DNS servers in your environment (either set via DHCP or STATICALLY on the single NIC of the HOST before deployment).


    Charles Joy [MSFT] http://blogs.technet.com/b/charlesjoy/

    Friday, September 30, 2016 7:54 PM
    Owner
  • @Mahmoud, Log has been sent !
    Monday, October 3, 2016 10:32 AM
  • I have the exact same results as @StormRa when installing TP2.

    Failed deployment at 60.61.93. Cannot reach login.windows.net.

    No DNS' are reachable outside my AzureStack environment. All adapters point to 192.168.200.3.
    We have a closed down environement. I have no DHCP on this specific network the host is installed on. I have manually specified IP, subnet, default GW and timeserver to the deploymentscript. This worked fine in TP1.

    I noticed that in MAS-BGPNAT01 the adapter pointing to the outside world was wrongly configured. I corrected this, and I can telnet the outside again. However, when using nslookup it still resolves to 192.168.200.3. I checked Forwarders in the DNS on 192.168.200.3 (MAS-DC01) and it points to our companys DNS. I can telnet this dns on port 53 from MAS-BGPNAT01 so the communication works. When looking at RRAS on MAS-BGPNAT01 it is not working. Tried to restart the service, but it gives me the error:

    "The Remote Access Connection Manager service terminated with the following service-specific error:
    (TDI Event Pending) The TDI indication has entered the pending state."

    Monday, October 3, 2016 2:54 PM
  • Thanks for the help in here, 

    Charles the DNS forwarders on MAS-DC01 VM  appeared not to be set, I reran with environment DNS parameter got further.  Then a further error regards the authentication token being earlier than the current time so I reran with the additional timestamp parameter using a time server in my environment

    I am now up and running to confirm in order to get this to work properly I hold to use the deployment script with the following parameters. 

    .\InstallAzureStackPOC.ps1 
    -NatIPv4Subnet  -NatIPv4Address  -NatIPv4DefaultGateway -EnvironmentDNS -TimeServer

    I still had a couple of failures at point 60.61.93 and 60.61.95 but rerunning the 

    Invoke-EceAction -RolePath Cloud -ActionType Deployment -Verbose -Start 60.61.93 (and 95)

    allowed the deployment to move past the initial errors


    Monday, October 3, 2016 7:35 PM
  • Hi,

    I had the same error and -//

    After Error 60.61.95 I just rebooted the MAS-gwy01 VM and triggered the following command

    Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 60.61.93

    ---- regards

    Tuesday, October 4, 2016 6:18 PM
  • @StormRa thanks for your valuable input.

    It seems like if the installation is on a firewalled net without any DHCP and just 2 company IP-adresses, the correct installation would be to supply all the parameters you suggested. The key for me was to add the -EnvironmentDNS and -TimeServer.

    So suppling all these parameters

    .\InstallAzureStackPOC.ps1 -NatIPv4Subnet  -NatIPv4Address  -NatIPv4DefaultGateway -EnvironmentDNS -TimeServer

    worked for me.

    the installation still failed at 60.61.93

    I reran

    Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 60.61.93

    and after error at step 95

    Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 60.61.95

    After that my installation went through.


    Thursday, October 6, 2016 9:43 AM
  • Same to me. 

    I have the exact same results when installing TP2.

    Failed deployment at 60.61.93 and also cannot reach login.windows.net even configuring a DNS forwarder.

    Is it possible setup MAS TP2 from a corporate network? The proxies does not seems transparent as requested.

    regards,

    Ivan

    Friday, October 7, 2016 1:25 PM
  • I seem to be having a similar issue with steps 60.61.93.  I've already tried re-run and complete rebuild without success.  DNS appears to resolve correctly.  Here's the error I'm getting in the summary log file:

    <Task RolePath="Cloud" ActionType="Deployment-Phase3-CreateServicePrincipals" StartTimeUtc="2016-10-09T01:56:40.605191Z" Status="Error" EndTimeUtc="2016-10-09T01:56:43.8872548Z">
                    <Action Type="Deployment-Phase3-CreateServicePrincipals" Scope="Internal" StartTimeUtc="2016-10-09T01:56:40.605191Z" Status="Error" EndTimeUtc="2016-10-09T01:56:43.8872548Z">
                      <Steps>
                        <Step Index="93" Name="(Katal) Create AzureStack Service Principals" Description="Create Azure Graph Applications and Service Principals in AAD." StartTimeUtc="2016-10-09T01:56:40.605191Z" Status="Error" EndTimeUtc="2016-10-09T01:56:43.8872548Z">
                          <Task RolePath="Cloud\Fabric\IdentityProvider" InterfaceType="Deployment" StartTimeUtc="2016-10-09T01:56:40.605191Z" Status="Error" EndTimeUtc="2016-10-09T01:56:43.8872548Z">
                            <Exception>
                              <Message>Function 'Create-ActiveDirectoryApplication' in module 'Roles\IdentityProvider\IdentityProvider.psd1' raised an exception:
    
    The remote server returned an error: (400) Bad Request.
    at Invoke-GraphApi, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 449
    at Get-GraphToken, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 325
    at Update-GraphAccessToken, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 341
    at Initialize-GraphEnvironment, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 169
    at Create-ActiveDirectoryApplication, C:\CloudDeployment\Roles\IdentityProvider\IdentityProvider.psm1: line 51
    at &lt;ScriptBlock&gt;, &lt;No file&gt;: line 18</Message>
                              <StackTrace>   at CloudEngine.Actions.PowerShellHost.Invoke(InterfaceParameters parameters, Object legacyConfigurationObject, CancellationToken token)
       at CloudEngine.Actions.InterfaceTask.Invoke(Configuration roleConfiguration, Object legacyConfigurationObject, MultiLevelIndexRange indexRange, CancellationToken token)</StackTrace>
                              <Raw>CloudEngine.Actions.InterfaceInvocationFailedException: Function 'Create-ActiveDirectoryApplication' in module 'Roles\IdentityProvider\IdentityProvider.psd1' raised an exception:
    
    The remote server returned an error: (400) Bad Request.
    at Invoke-GraphApi, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 449
    at Get-GraphToken, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 325
    at Update-GraphAccessToken, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 341
    at Initialize-GraphEnvironment, C:\CloudDeployment\Roles\IdentityProvider\GraphAPI.psm1: line 169
    at Create-ActiveDirectoryApplication, C:\CloudDeployment\Roles\IdentityProvider\IdentityProvider.psm1: line 51
    at &lt;ScriptBlock&gt;, &lt;No file&gt;: line 18
       at CloudEngine.Actions.PowerShellHost.Invoke(InterfaceParameters parameters, Object legacyConfigurationObject, CancellationToken token)
       at CloudEngine.Actions.InterfaceTask.Invoke(Configuration roleConfiguration, Object legacyConfigurationObject, MultiLevelIndexRange indexRange, CancellationToken token)</Raw>
                            </Exception>
                          </Task>

    Any ideas how to get past this?  Thanks.


    boom


    • Edited by boomboom21 Sunday, October 9, 2016 2:17 AM
    Sunday, October 9, 2016 2:12 AM
  • I got past this issue by creating a new Azure AD instance.   I was trying to use our existing AD instance that's sync'd with our on-prem directory.  I'm guessing that isn't currently supported?

    boom

    Wednesday, October 12, 2016 6:58 PM
  • RE: 400 bad request

    @boomboom21 I had the same issue. 

    I discovered my Azure AD user didn't have "Global Admin Privileges." Make sure you set them in the new Azure AD portal UI. I set "Global Admin Privileges" in the old portal UI and they didn't take.

    Friday, October 14, 2016 7:31 PM
  • Getting the same errors everyone else has mentioned. (InvalidOperation: (:)...)

    I'm stuck at 60.120. It won't go any further.

    After 10 unsuccessful deploys I'm done with this. I'm guessing there's no such thing as Continuous Integration and testing in MS land?

    Shouldn't this Clouddeployment code be put on Github so we can submit PRs? 

    Friday, October 14, 2016 7:40 PM
  • I, too, am finding it impossible to move forward from 60.61.93.  It simply appears as though Internet access goes completely south by this time in the installation.  I am in a corporate environment so there are a fair number of hops between this server and the Internet.  However, I do not need a Proxy server to get out.  I deployed a TP2 POC node at another location directly onto a DMZ with less hoops to jump through to get to the Internet, and that server deployed without a problem.

    I'm assuming at this point that there is something environmentally specific (NAT rules, reverse proxies, etc.) that this POC deployment does not like.  Does anyone have thoughts about what might still be done to move forward in corporate environments?

    Thanks.

    Monday, October 31, 2016 6:05 PM
  • Maybe it would help to better understand the network traffic patterns after the Azure Stack environment starts getting setup.  I am assuming that the MAS-BGPNAT01 server becomes the edge router for the environment.  What would be the source IP address range for getting out to the Internet by Step 60.61?  I may need to make sure the appropriate network is allowed to go outbound through a pair of firewalls, as NATing at these firewalls help eliminate the need for a proxy server.

    Thanks.

    Tuesday, November 1, 2016 1:48 PM