Scheduled reboot does not start the VDAs - EventID 3012 and EventID 3053

Scheduled reboot does not start the VDAs - EventID 3012 and EventID 3053

book

Article ID: CTX463889

calendar_today

Updated On:

Description

Scheduled reboots don't work on a few VDAs, you would see the below behavior

  • The scheduled reboot action shuts down the VDAs but does not power them on.
  • The same behavior is seen restarting a VDA manually from Studio, the VDA shuts down but does not start up
  • The same behavior is seen trying to start a turned-off VDA from Studio
  • The creation of a new MCS catalog using the same Master Image, and scheduled reboot works as expected
  • A newly added VDA into the same machine catalog/Delivery group reboots as expected

You might have 2 main errors in the event viewer of the DDC :

EventID 3012
The Citrix Broker Service detected that the power action 'TurnOn' (origin: Admin) on virtual machine 'XXX' failed.
This problem is most likely due to a host issue. Check that the configuration of the virtual machine on the host does not prohibit the requested power action. Verify that there are no storage problems on the host. Check that the host connection information is correct.
Error details: Exception 'Failure in ResetVM, GeneralFailure' of type 'Citrix.Cds.HostingManagement.McsResetVMFailedException'.

EventID 3053
The Citrix Broker Service successfully communicated with the Citrix Machine Creation Service, but the Citrix Machine Creation Service failed to reset the image for virtual machine 'XXX' on host connection 'YYY' to its default state.
This problem could be due to a timing issue or an internal error.
Error details: Exception 'Failure in ResetVM, GeneralFailure' of type 'Citrix.Cds.HostingManagement.McsResetVMFailedException'.

Resolution

Recreate the VDA by deleting it from the Delivery group, Machine catalog and re-add them.

If you need to use the same Machine account, you can select the  'Remove the virtual machines from the catalog and delete the virtual machines > Remove the accounts from the catalog but do not remove them from Active directory".


Problem Cause

Possible corruption on the affected VDA