Last week i finally got my first Azure Stack TP2 deployment completed after weeks of error’s as a blogged before. After that i needed to redeploy several times and ran into different issue’s every time.
This time it stopped at step 0.20. After retrying the deployment with:
Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.20 -Verbose
It stopped at the same error. See below for te error message.
2016-11-08 20:45:06 Verbose VMs to create: MAS-BGPNAT01 2016-11-08 20:45:06 Verbose Updating management nodes for HyperConverged deployment. 2016-11-08 20:45:12 Verbose Skipping deployment of the VM named 'MAS-BGPNAT01'. It is accessible via remote Powershell. 2016-11-08 20:45:12 Verbose Waiting for the following VMs to be remotely accessible: MAS-BGPNAT01. 2016-11-08 20:45:13 Verbose The VM 'MAS-BGPNAT01' has successfully started. 2016-11-08 20:45:15 Error Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\VirtualMachines' failed: Function 'Add-GuestVMs' in module 'Roles\VirtualMachine\VirtualMachine.psd1' raised an exception: The WS-Management service cannot process the request because the XML is invalid. at Wait-VMPSConnection, C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1: line 1683 at Add-GuestVMs, C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1: line 265 at <ScriptBlock>, <No file>: line 18 2016-11-08 20:45:15 Verbose Step: Status of step '(NET) Deploy BGP VM' is 'Error'. 2016-11-08 20:45:15 Error Action: Invocation of step 0.20 failed. Stopping invocation of action plan. 2016-11-08 20:45:15 Verbose Action: Status of 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' is 'Error'.
The MAS-BGPNAT01 VM was accessible and i didn’t notice any errors in relation to the error above in the eventlogs. After a reboot of the MAS-BGPNAT01 VM I started the deployment from step 1, without the -start parameter: