locked
Problem deploying Azure Stack TP2 " Connecting to remote server MAS-SUS01 failed with the following error message : Access is denied." RRS feed

  • Question

  • Hey, the deploy failed at step 40, and this is the tail end of the log:

    2017-02-02 20:23:18 Verbose  Adding Machine Account Group memberships in AD.

    2017-02-02 20:23:25 Verbose  Resetting kerberos ticket cache and group policy on VMs 'MAS-NC01'

    2017-02-02 20:23:44 Verbose  Resetting kerberos ticket cache and group policy on VMs 'MAS-SLB01'

    2017-02-02 20:24:00 Verbose  Resetting kerberos ticket cache and group policy on VMs 'MAS-Gwy01'

    2017-02-02 20:24:16 Verbose  Resetting kerberos ticket cache and group policy on VMs 'MAS-Con01'

    2017-02-02 20:24:44 Verbose  Resetting kerberos ticket cache and group policy on VMs 'MAS-ASql01'

    2017-02-02 20:25:05 Verbose  Resetting kerberos ticket cache and group policy on VMs 'MAS-SUS01'

    2017-02-02 20:25:05 Error    Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\VirtualMachines' failed: Function 'Add-GuestVMs' in module 'Roles\VirtualMachine\VirtualMachine.psd1' raised an exception:Connecting to remote server MAS-SUS01 failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.

    at Add-GuestVMs, C:\CloudDeployment\Roles\VirtualMachine\VirtualMachine.psm1: line 314at <ScriptBlock>, <No file>: line 18

    2017-02-02 20:25:05 Verbose  Step: Status of step '(CPI) Create guest VMs' is 'Error'.

    2017-02-02 20:25:05 Error    Action: Invocation of step 40.41 failed. Stopping invocation of action plan.

    2017-02-02 20:25:05 Verbose  Action: Status of 'Deployment-Phase1-CreateVMs' is 'Error'.

    2017-02-02 20:25:05 Verbose  Task: Status of action 'Deployment-Phase1-CreateVMs' of role 'Cloud' is 'Error'.

    2017-02-02 20:25:05 Verbose  Step: Status of step 'Phase 1 - CreateVMs' is 'Error'.

    2017-02-02 20:25:05 Error    Action: Invocation of step 40 failed. Stopping invocation of action plan.

    What's best to do for me now? Run deploy script with -Rerun? And do you have any suggestion as to why the above error would occur?
    Thursday, February 2, 2017 8:44 PM

Answers

All replies

  • I also found the following error in a logfile from this deploy:

    2017-02-02 19:23:07 Error    Cannot find the Windows PowerShell data file 'WindowsPackageCab.Strings.psd1' in directory 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DSCClassResources\WindowsPackageCab\en\', or in any parent culture directories.

    Could it be related? 

    Thursday, February 2, 2017 9:00 PM
  • Maybe. Check if the MAS-DC01 is running and can be authenticated to.
    Then try '-rerun', if that fails then try the following commands to start at previous possibly failed deployment steps.

    Import-Module C:\CloudDeployment\CloudDeployment.psd1 -Force
    Import-Module C:\CloudDeployment\ECEngine\EnterpriseCloudEngine.psd1 -Force 
    Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 40 -Verbose
    # and if that fails
    Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.22 -Verbose


    Cheers,

    Ruud
    Twitter:    Blog: AzureStack.Blog  LinkedIn:    
    Note: Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.



    Friday, February 3, 2017 9:29 AM
  • Thanks for the reply. I tried rerunning the deployment from the step it failed after manually connecting to MAS-SUS01. In the end I ended up rerunning the entire deployment since it was getting late, and I had to head home. I'll update if I get the same error this time around
    Friday, February 3, 2017 10:40 AM
  • Thanks for the feedback. Lets hope it goes past step 40.41

    Cheers,

    Ruud
    Twitter:    Blog: AzureStack.Blog  LinkedIn:    
    Note: Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Friday, February 3, 2017 3:31 PM
  • It got past that step, currently stopped on 60.120.124. Issue here is the time is one hour off, so I'm trying to see if there's some timezone changes in the BIOS of my Dell PowerEdge R810, as I guess that is the culprit. ( Time was however correct before it booted into the vhdx ).
    Friday, February 3, 2017 5:56 PM
  • Hello,
    The commands below should help to troubleshoot, correct and resync the time and -rerun the deployment. Let us know how it goes.


    ### Create array of VMs
    $ALLVMS = @("MACS-ACS01","MAS-ADFS01","MAS-ASql01","MAS-BGPNAT01","MAS-CA01","MAS-Con01","MAS-DC01","MAS-Gwy01","MAS-NC01", "MAS-SLB01", "MAS-SUS01", "MAS-WAS01", "MAS-Xrp01")

    # Compare server time between Host and VMs
    Invoke-command -Computername $ALLVMS -ScriptBlock {Get-Date}
    Get-Date

    # Compare server time with external time server
    w32tm /stripchart /Computer:time.windows.com /dataonly

    # Sync time to server time.windows.com
    W32tm /resync /Computer:10.224.122.201 /nowait

    # Syncs all VMs with MAS-DC01
    Invoke-Command -Computer $ALLVMS -ScriptBlock { gsv w32time | sasv; w32tm /resync /force }

    # Compare server time between Host and VMs
    Invoke-command -Computername $ALLVMS -ScriptBlock {Get-Date}
    Get-Date


    Once the time is synced between all Server VMs redeploy using the -rerun parameter

    cd C:\CloudDeployment\Configuration
    .\InstallAzureStackPOC.ps1 -rerun

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


    Thanks,


    Friday, February 3, 2017 7:29 PM
  • 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/

    Thanks,


    Gary Gallanes

    Wednesday, March 1, 2017 5:27 PM