locked
AzureStack TP2 failed to provision VM RRS feed

  • Question

  • I've just installed Azure Stack TP2 successfully and I am unable to provision a VM, other things seem to work ok. I have tried this a few times with the same result.

    Error:

    {
      "status": "Failed",
      "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The resource operation completed with terminal provisioning state 'Failed'.",
        "details": [
          {
            "code": "InternalExecutionError",
            "message": "Failed to create VM 'vm04' "
          }
        ]
      }
    }

    Monday, January 23, 2017 11:17 PM

Answers

All replies

  • Hi,

    Could you provide a little more information.

    Operational details in the deployment logs should provide additional clues as to why this failed.

    Please,

    -          Go to the Resource Group created when you deployed your VM

    -          Go to Settings \ Deployments

    -          In the right ‘Blade’ you will see a list of all deployments performed for that resource group

    -          Click on the deployment logs for the failed VM deployment

    -          Go to the Events link and check for logs with a Status of Failed or Error

    -          Click to view verbose details and copy/paste error/exception back to Forum

    -          Go to Operation Details and check for logs with a Status of Failed or Error

    -          Click to view verbose details and copy/paste error/exception back to Forum

    Thanks,


    Gary Gallanes

    Tuesday, January 24, 2017 12:05 AM
  • Below are the Event errors and Operation Detail errors.

    Event error

    Operation Name
     
     Microsoft.Compute/virtualMachines/write  

    Status
     
     Failed  

    Event Timestamp
     
     Mon Jan 23 2017 15:44:08 GMT-0600 (Central Standard Time)  

    UTC Timestamp
     
     Mon, 23 Jan 2017 21:44:08 GMT  

    Authorization

    action:Microsoft.Compute/virtualMachines/write
     
    role:
     
    scope:/subscriptions/d07605a5-3a04-4f0a-875b-88840fa383a6/resourcegroups/mystuff2/providers/Microsoft.Compute/virtualMachines/vm04

    Resource Uri
     
     /subscriptions/d07605a5-3a04-4f0a-875b-88840fa383a6/resourcegroups/mystuff2/providers/Microsoft.Compute/virtualMachines/vm04  

    Subscription ID
     
     d07605a5-3a04-4f0a-875b-88840fa383a6  

    Event Submission Timestamp
     
     Mon Jan 23 2017 15:44:30 GMT-0600 (Central Standard Time)  

    Operation ID
     
     b8f547de-d676-4870-9311-f06478c422e3  

    Correlation ID
     
     97404839-08b2-4c5d-bbb7-15673e9fa79c  

    Level
     
     Error  

    Resource Group
     
     mystuff2  

    Resource Provider
     
     Microsoft.Compute  

    Category
     
     Administrative  

    Properties

    statusCode:Conflict
     
    statusMessage:{"status":"Failed","error":{"code":"ResourceDeploymentFailure","message":"The resource operation completed with terminal provisioning state 'Failed'.","details":[{"code":"InternalExecutionError","message":"Failed to create VM 'vm04' "}]}}

    Operation Details

    Operation Id

    FC48E762F84C8B52

    Tracking Id

    b8f547de-d676-4870-9311-f06478c422e3

    Status

    Conflict

    Provisioning State

    Failed

    Timestamp

    ?1?/?23?/?2017? ?3?:?44?:?08? ?PM


    Duration


    5 minutes 29 seconds


    Type

    Microsoft.Compute/virtualMachines

    Resource Id

    /subscriptions/d07605a5-3a04-4f0a-875b-88840fa383a6/resourceGroups/mystuff2/providers/Microsoft.Compute/virtualMachines/vm04

    StatusMessage

    {
      "status": "Failed",
      "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The resource operation completed with terminal provisioning state 'Failed'.",
        "details": [
          {
            "code": "InternalExecutionError",
            "message": "Failed to create VM 'vm04' "
          }
        ]
      }
    }

    Tuesday, January 24, 2017 2:46 PM
  • Hi,

    Thanks for replying back with the logs.

    I noticed a strange timestamp at the point of failure in the logs.  This may indicate a known issue we’ve seen with the Time falling out of sync between MAS-DC01 & MAS-BGPNAT.

    Status Conflict

    Provisioning State Failed

    Timestamp   ?1?/?23?/?2017? ?3?:?44?:?08? ?PM

    Does vm04 show up in the Azure Stack Portal?

    If so, is it running?  My first few VMs failed installing an optional extensions and status was then set to ‘Deployment Failed’ although my VMs were actually up and running.   

    If not, run the following in PowerShell to compare the Time on MAS-DC01, MAS-WAS01 & MAS-BGPNAT.

    $NETVMS= @("MAS-BGPNAT","MAS-DC01","MAS-WAS01")

    Invoke-command-Computername $ALLVMS -ScriptBlock {Get-Date}

    If the time is out of sync run the following command on the VM that is out of sync with MAS-DC01.

    net time \\<DC_name_or_IP> /set /y

    If not, try deleting the all the resource groups created when failing to deploy the VMs.

    Restart the all the Azure Stack management  VMs through Hyper-V manager on the deployment server, wait a few minutes, validate all Services set to ‘Automatic’ are running and then go to the Market Place in the Azure Stack Portal and try deploying your VM again.

    Let us know how it goes.

    Thanks,


    Gary Gallanes

    Thursday, January 26, 2017 6:08 AM
  • I think my logs did not copy over right. Below is the log again and the timestamp looks right.

    I ran your PS script and the dates are all the same. I also restarted all of the vms and I get the same error message when provisioning.

    The VM is never created, I periodically monitor Hyper-V manager and I never see the VM appear in the console.

    I made sure that all of the services set to 'Automatic' start were running. I did get one error on a service

    Failed to start service 'Remote Access Connection Manager (RasMan)'.

        + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service], ServiceCommandExcept

       ion

        + FullyQualifiedErrorId : StartServiceFailed,Microsoft.PowerShell.Commands.StartServiceCommand

        + PSComputerName        : MAS-BGPNAT01

    Operation Id
    FC48E762F84C8B52
    • Tracking Id
      b8f547de-d676-4870-9311-f06478c422e3
    • Status
      Conflict
    • Provisioning State
      Failed
    • Timestamp
      ‎1‎/‎23‎/‎2017‎ ‎3‎:‎44‎:‎08‎ ‎PM
    • Duration
      5 minutes 29 seconds
    • Type
      Microsoft.Compute/virtualMachines
    • Resource Id
      /subscriptions/d07605a5-3a04-4f0a-875b-88840fa383a6/resourceGroups/mystuff2/providers/Microsoft.Compute/virtualMachines/vm04
    • StatusMessage
      {
        "status": "Failed",
        "error": {
          "code": "ResourceDeploymentFailure",
          "message": "The resource operation completed with terminal provisioning state 'Failed'.",
          "details": [
            {
              "code": "InternalExecutionError",
              "message": "Failed to create VM 'vm04' "
            }
          ]
        }
      }
    • Resource
      vm04

    Thursday, January 26, 2017 9:56 PM
  • Hi,

    The conflict error indicates in most cases that not all required services are running on the xRPVM.
    Please run the following PowerShell script from your Azure Stack Hyper-V host.

    Afterwards try to deploy a VM again.

    $Credential=Get-Credential

    Invoke-Command -VMName "xRPVM" -Credential $Credential -ScriptBlock{

    Get-Service CRP|Start-Service -Verbose

    Get-Service AvailabilitySetController|Start-Service -Verbose

    Get-Service BlobManager|Start-Service -Verbose

    Get-Service ClusterManager|Start-Service -Verbose

    Get-Service ComputeController|Start-Service -Verbose

    Get-Service DiagnosabilityManager|Start-Service -Verbose

    Get-Service ExtensionManager|Start-Service -Verbose

    Get-Service GuestArtifactRepository|Start-Service -Verbose

    Get-Service IsoManager|Start-Service -Verbose

    Get-Service ManifestProvider|Start-Service -Verbose

    Get-Service MetadataServer|Start-Service -Verbose

    Get-Service NetworkManager|Start-Service -Verbose

    Get-Service PlacementManager|Start-Service -Verbose

    Get-Service PlatformImageRepository|Start-Service -Verbose

    Get-Service TopologyManager|Start-Service -Verbose

    }

    If the deployment still fails we'll need to analyze the log files under C:\CrpServices\Diagnostics on xRPVM to continue our investigation.
    Please email us at ascustfeedback@microsoft.com and we will set up a workspace where you can upload the logs.

    Thanks,


    Gary Gallanes

    Friday, January 27, 2017 12:07 AM
  • 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:26 PM