Меню

Подключение к виртуальной машине приложение обнаружило ошибку при попытке изменить состояние

  • Remove From My Forums
  • Вопрос

  • Windows Server 2016. Установил роль Hyper-V. Создаю новую виртуальную машину. Добавляю образ для установки и всё.

    Не запускается. Перечитал несколько тем с подобными ошибками. Ничего не помогло. Переустановил роль. Результат одинаковый.

    Пишет — Приложение обнаружило ошибку при попытке изменить состояние виртуальной машины. Права на папку с виртуальной машиной установил ВСЕ-полный доступ. Не могу понять что не так. Помогите пожалуйста.

Ответы

  • В общем сегодня принял решение больше не мучиться. Нет ни сил, ни времени, ни нервов.

    Тем более сегодня обнаружил ещё один трабл. Со вчерашнего вечера скачивание обновлений стоит на 0%.

    Переустановлю по чистому.

    Всем большое спасибо за помощь. 

    • Помечено в качестве ответа

      9 марта 2021 г. 8:45

  • Remove From My Forums

 locked

Unable to change VM state — cannot turn off/on

  • Question

  • Hi,

    Had an issue today where shortly after a DPM backup started one of our VMs (the one being backed up) went offline (couldn’t ping or access any services across the network). In Hyper-V manager the virtual machine appeared to be running and the status of the
    virtual machine showed «Backing up». When opening the virtual machine console it showed the Ctrl+alt+del screen but sending a ctrl+alt+del got no response. When attempting to shutdown or turn off the VM we were met with the error:

    ===================

    «The application encountered an error while attempting to change the state of ‘vmname’. 

    ‘vmname’ failed to change state.

    The operation cannot be performed while the object is in its current state. 

    ================

    In failover cluster manager the status of the machine showed as Running (locked). Same errors as in Hyper-V manager when trying to turn off the VM.

    We stopped the job in DPM and even restarted the DPM server but no change.

    We managed to turn off the VM by killing the instance of vmwp.exe that related to the VM. However we were then unable to start it as were still getting the above error. In the end we had to live migrate all our other VMs off the host and restart the host
    (had to press the button as the host hung on shutting down). The VM then fired up on the other host in the cluster.

    Obviously this is a rubbish solution as we incurred an unacceptable amount of downtime waiting for the live migrations and host shutdown.

    I’ve looked at other forum posts but can’t see any suggestions other than the host shutdown. Ever come across this and have a fix or better workaround than restarting the host?

    Thanks

Answers

    • Marked as answer by

      Wednesday, August 27, 2014 8:14 AM

    • Marked as answer by
      Alex Lv
      Wednesday, August 27, 2014 8:14 AM
  • Remove From My Forums

 locked

Unable to change VM state — cannot turn off/on

  • Question

  • Hi,

    Had an issue today where shortly after a DPM backup started one of our VMs (the one being backed up) went offline (couldn’t ping or access any services across the network). In Hyper-V manager the virtual machine appeared to be running and the status of the
    virtual machine showed «Backing up». When opening the virtual machine console it showed the Ctrl+alt+del screen but sending a ctrl+alt+del got no response. When attempting to shutdown or turn off the VM we were met with the error:

    ===================

    «The application encountered an error while attempting to change the state of ‘vmname’. 

    ‘vmname’ failed to change state.

    The operation cannot be performed while the object is in its current state. 

    ================

    In failover cluster manager the status of the machine showed as Running (locked). Same errors as in Hyper-V manager when trying to turn off the VM.

    We stopped the job in DPM and even restarted the DPM server but no change.

    We managed to turn off the VM by killing the instance of vmwp.exe that related to the VM. However we were then unable to start it as were still getting the above error. In the end we had to live migrate all our other VMs off the host and restart the host
    (had to press the button as the host hung on shutting down). The VM then fired up on the other host in the cluster.

    Obviously this is a rubbish solution as we incurred an unacceptable amount of downtime waiting for the live migrations and host shutdown.

    I’ve looked at other forum posts but can’t see any suggestions other than the host shutdown. Ever come across this and have a fix or better workaround than restarting the host?

    Thanks

Answers

    • Marked as answer by

      Wednesday, August 27, 2014 8:14 AM

    • Marked as answer by
      Alex Lv
      Wednesday, August 27, 2014 8:14 AM

0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии

А вот еще интересные материалы:

  • Яшка сломя голову остановился исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Подойдя ближе это оказались крупные ягоды боярышника тип ошибки
  • Подключение к беспроводной сети не выполнено ошибка аутентификации