Skip to main content

 none
VM cannot be started RRS feed

  • Question

  • This morning a lot of VMs (windows 2016in our org cannot be started. It went to "Updating", then "failed". Restart (or Stop then start) brought VM to "Updating" again, then failed a gain. 

    The error read: 

    Provisioning failed. An unexpected error occured while processing the network profile of the VM. Please retry later.. NetworkingInternalOperationError


    ProvisioningState/failed/NetworkingInternalOperationError

    The VM may install the following ( I saw it for a VM that is running because of insufficient storage). 

    • 2019-10 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4519998).

    Any suggestions? This is an urgent issue for our group since most dev works are in Azure VMs. 

    Monday, October 21, 2019 5:20 PM

All replies

  • Can you try redeploying the VM to see if that helps? 

    Essentially there was an error on the backend with the start operation and allocating the resources. So a redeploy might fix the issue. 

    Monday, October 21, 2019 6:39 PM
    Moderator
  • Hello,

    Any update on the issue?

    Just checking in if you got a chance to see previous reply from Micah and give the suggestion a try.

    If the suggested response helped you resolve your issue, do click on "Mark as Answer" and "Up-Vote" for the answer that helped you for benefit of the community.

    Thanks.

    Tuesday, October 29, 2019 2:56 PM
    Moderator