locked
Unable to start VM - The server encountered an internal error. Please retry the request RRS feed

  • Question

  • My Virtual Machine is suddenly stopped (Unable to start VM - The server encountered an internal error. Please retry the request) when i start getting this error, My subscription is fine. this server was working fine from past 10 Months.


    • Edited by SBAVS Tuesday, October 27, 2015 12:36 PM
    Tuesday, October 27, 2015 12:32 PM

Answers

  • Hi,

    In some cases as availability of free blades or free space within a blade in a cluster fluctuates, the constraints to find an allocation for the service may not be met. When these constraints are not satisfied, we return back an allocation failure error message.

    To avoid this error create multiple affinity groups to house services that are not required to be placed together, spin up smaller numbers of VM’s at a time, ensure retry logic is in place when an operation is unsuccessful and also utilize multiple data centers for your deployments. 

    Try Multiple Restarts for the VM, however if the VM still does not start, please try the below steps

    • Resize the Virtual Machine from the Portal but ensure to Back up the Data in the Temporary Drive ( D:\) since the data will be lost while Resizing.
    • If the issue is still not fixed, please recreate the VM by retaining the attached Disk’s and attaching the same to the new VM
    • However sometimes it could also be because of a time out issue which is usually fixed within a day or so.

    However, if your deployment is in Southeast Asia region, there is an ongoing outage. Please check the Azure status for more details.

    https://azure.microsoft.com/en-us/status/

    Girish Prajwal

    Tuesday, October 27, 2015 1:25 PM

All replies

  • Hi,

    In some cases as availability of free blades or free space within a blade in a cluster fluctuates, the constraints to find an allocation for the service may not be met. When these constraints are not satisfied, we return back an allocation failure error message.

    To avoid this error create multiple affinity groups to house services that are not required to be placed together, spin up smaller numbers of VM’s at a time, ensure retry logic is in place when an operation is unsuccessful and also utilize multiple data centers for your deployments. 

    Try Multiple Restarts for the VM, however if the VM still does not start, please try the below steps

    • Resize the Virtual Machine from the Portal but ensure to Back up the Data in the Temporary Drive ( D:\) since the data will be lost while Resizing.
    • If the issue is still not fixed, please recreate the VM by retaining the attached Disk’s and attaching the same to the new VM
    • However sometimes it could also be because of a time out issue which is usually fixed within a day or so.

    However, if your deployment is in Southeast Asia region, there is an ongoing outage. Please check the Azure status for more details.

    https://azure.microsoft.com/en-us/status/

    Girish Prajwal

    Tuesday, October 27, 2015 1:25 PM
  • Hi,

    The issue has been mitigated. Please check and let us know if you are still facing the issue.

    Girish Prajwal

    Tuesday, October 27, 2015 6:01 PM