The following forum(s) have migrated to Microsoft Q&A (Preview): Azure Virtual Machines!
Visit Microsoft Q&A (Preview) to post new questions.

Learn More

 locked
New-AzureRmVM : Long running operation failed with status 'Failed'. RRS feed

  • Question

  • I am trying to deploy VM out of specialized VHD. While running "New-AzureRmVM -ResourceGroupName $RGPName -Location $location -VM $vm -Verbose -Debug " I am getting following error:

    Status: Failed
    ErrorCode: VMAgentStatusCommunicationError
    ErrorMessage: VM 'VM1' has not reported status for VM agent or extensions. Please verify the VM has a running VM agent,
     and can establish outbound connections to Azure storage.
    [Y] Yes  [A] Yes to All  [H] Halt Command  [S] Suspend  [?] Help (default is "Y"):
    New-AzureRmVM : Long running operation failed with status 'Failed'.
    StartTime: 8/14/2016 12:11:09 PM
    EndTime: 8/14/2016 12:36:39 PM
    OperationID:
    Status: Failed
    ErrorCode: VMAgentStatusCommunicationError
    ErrorMessage: VM 'VM1' has not reported status for VM agent or extensions. Please verify the VM has a running VM
    agent, and can establish outbound connections to Azure storage.
    At line:1 char:1
    + New-AzureRmVM -ResourceGroupName $RGPName -Location $location -VM $vm -Verbose - ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : CloseError: (:) [New-AzureRmVM], ComputeCloudException
        + FullyQualifiedErrorId : Microsoft.Azure.Commands.Compute.NewAzureVMCommand

    DEBUG: AzureQoSEvent: CommandName - New-AzureRmVM; IsSuccess - False; Duration - 00:27:47.5759844; Exception -
    Microsoft.Azure.Commands.Compute.Common.ComputeCloudException: Long running operation failed with status 'Failed'.
    StartTime: 8/14/2016 12:11:09 PM
    EndTime: 8/14/2016 12:36:39 PM
    OperationID:
    Status: Failed
    ErrorCode: VMAgentStatusCommunicationError
    ErrorMessage: VM 'VM1' has not reported status for VM agent or extensions. Please verify the VM has a running VM agent,
     and can establish outbound connections to Azure storage. ---> Microsoft.Rest.Azure.CloudException: Long running
    operation failed with status 'Failed'.
       at Microsoft.Rest.Azure.AzureClientExtensions.<GetPutOrPatchOperationResultAsync>d__1`2.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.Rest.Azure.AzureClientExtensions.<GetPutOrPatchOperationResultAsync>d__0`1.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at
    Microsoft.Azure.Management.Compute.VirtualMachineExtensionsOperations.<CreateOrUpdateWithHttpMessagesAsync>d__5.MoveNex
    t()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.Azure.Commands.Compute.NewAzureVMCommand.<ExecuteCmdlet>b__4()
       at Microsoft.Azure.Commands.Compute.ComputeClientBaseCmdlet.ExecuteClientAction(Action action)
       --- End of inner exception stack trace ---
       at Microsoft.Azure.Commands.Compute.ComputeClientBaseCmdlet.ExecuteClientAction(Action action)
       at Microsoft.Azure.Commands.Compute.NewAzureVMCommand.ExecuteCmdlet()
       at Microsoft.WindowsAzure.Commands.Utilities.Common.AzurePSCmdlet.ProcessRecord();
    DEBUG: Finish sending metric.
    DEBUG: 12:37:04 PM - NewAzureVMCommand end processing.
    DEBUG: 12:37:04 PM - NewAzureVMCommand end processing.

    VM status is running, however I cannot RDP into VM. 

    Further, Extension status says:

    BGInfo  Microsoft.Compute.BGInfo 2* unavailable

    JUST FYI:

    I have already followed all the STEPS mentions in 

    https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-windows-troubleshoot-rdp-connection/#fix-common-remote-desktop-errors

    Any help would be highly appreciated

    Sunday, August 14, 2016 7:22 AM

All replies

  • Hello ,
    Greetings from Microsoft Azure.

    Do you have a Network Security Group that is blocking outbound connectivity from your VM? VM Agent and Extensions has to update a file Status Upload Blob   which is in the storage account of the OS VHD.
    If HTTPS is blocked to this storage account then you will get this error message. More information here http://www.deployazure.com/compute/virtual-machines/azure-vm-agent-extensions-deep-dive-part-3/

    Hope this helps  !!!

    Regards,
    Monika
    _______________________________________________________________________________________
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer so that other customers can benefit from it.

    Sunday, August 14, 2016 3:56 PM
  • Hello,

    I face the same error when I am trying to create a Windows 10 Pro VM using Azure Marketplace through Powershell. But if I select Windows Server 2012 R2 image, (instead of Windows10 Image) it works perfectly without any error. I don't know what's wrong with it. 

    Kindly help.

    Thanks,

    -Aayush 



    -Thanks AB



    Friday, December 15, 2017 12:54 PM
  • Were VM agent already there in the previous VM?

    -----------------------------------------------------------------------------------------------

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.


    Sunday, December 17, 2017 10:33 AM