none
Can't move VMs in cluster to a particular host RRS feed

  • Question

  • I have a 3 node, 2016 Datacenter cluster. Multiple VMs. Right now, all VMs are on hosts 1 and host 2. If I try to live migrate to host 3, I get event id 1069 and 21502. I can migrate between hosts 1 and 2 at will with no problem. Even when I try a quick migrate, the VM appears to move to host 3, but when I start it, it fails immediately.

    The thing I've noticed is that I can access the Cluster Shared Volume from windows explorer on host 1 and host 2. If I try to access it on host 3 I get:

    C:\clusterstorage\volume1 is not accessible. The referenced account is currently locked out and may not be logged on to.

    The 1069 error reads:

    Cluster resource 'Virtual Machine X' of type 'Virtual Machine' in clustered role 'X' failed. The error code was '0x775' ('The referenced account is currently locked out and may not be logged on to.').


    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

    The 21502 error mentions:

    'Virtual Machine X' failed to start.

    'X' failed to start. (Virtual machine ID blah_blah)

    'X' failed to start worker process: The referenced account is currently locked out and may not be logged on to. (0x80070775). (Virtual machine ID blah_blah)

    'Virtual Machine Name Unavailable' could not initialize. (Virtual machine ID blah_blah)

    'Virtual Machine Name Unavailable' could not read or update virtual machine configuration: The referenced account is currently locked out and may not be logged on to. (0x80070775). (Virtual machine ID blah_blah)

    What account is it referring to? Shouldn't this be happening across all hosts instead of host 3?

    Any help is much appreciated.

    Wednesday, November 13, 2019 10:21 PM

All replies

  • More info. It looks like the CLIUSR account is repeatedly being locked by host 3, but not on host 3. For example, if I go to host 1 and look at the CLIUSR account, it shows locked. If I unlock it, and check the security logs, it shows it was immediately locked by host 3. 
    Wednesday, November 13, 2019 11:49 PM
  • Hi,

    Thank you for posting in forum!

    1.Please provide me with more details.

    What’s the current account logon on host 3 for accessing CSV?

    2. Please follow the following methods.

    1)Please change the minimum password length in Default Domain Policy from 15 to 14 and try to live migrate again, see if the same issue occurs.

    2)Please change ownership of the CSV to host 3, and see if host 3 can access CSV.

    3)Try to evict host 3 from the cluster and add host 3 back to the cluster and see if the same issue occurs.

    For more information, please refer to the similar post:

    https://social.technet.microsoft.com/Forums/ie/en-US/41291ef2-59fe-49ea-978f-f844d669d2ba/clusterstorage-unavailable?forum=winserverhyperv

    Hope this can help you. Please let us know if you would like further assistance.

    Best Regards,

    Lily Yang



    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, November 14, 2019 9:00 AM
  • Have you run a cluster validation wizard?  That is designed to help troubleshoot issues.

    If this is a production machine, you may want to add a test disk to the cluster and run the disk tests just on that disk.  Otherwise, the wizard will try to fail ownership of each disk to each node, resulting in movement of the VMs.  As you are having issues with that capability, unless you are willing to see VMs go up and down, it might not be wise to test the live environment.  Another way would be to run the wizard during a maintenance period.  Turn off all the VMs except one (maybe a test VM) that can be moved around and you don't care if it fails.


    tim

    Thursday, November 14, 2019 2:31 PM
  • Please do restart the HOST 3 and run the cluster validation.

    This might help you.

    Thursday, November 14, 2019 2:43 PM
  • Thanks for responding. This is a production system, so I must tread carefully with any possible solutions.

    The current logon account on host 3 is the same logon account used on host 1 and host 2. Let's call it user1. I have no issues getting to the CSV on host 1 and host 2.

    The minimum password length was changed in September, but I saw that same post you mentioned and changed the minimum length to 13 and still the error occurs.

    I can unlock the CLIUSR account on host 1 and almost immediately, it's re-locked by host 3. Clearly Host 3 has an incorrect password for CLIUSR.

    I will try the change of ownership during off hours.

    I will try the evict and re-add.

    Thursday, November 14, 2019 6:22 PM
  • Thanks for responding.

    I have not run the validation wizard because it is a production environment. I will have to schedule a time to do this with only a single VM active.

    Thursday, November 14, 2019 6:24 PM
  • Thanks for responding.

    I have restarted host 3 several times and will do a cluster validation during a maintenance window.

    Thursday, November 14, 2019 6:24 PM
  • Please share the cluster validation screenshot with us. Next could you please verify all the network connectivirty.

    Could you please explain about the cluster shared volume .

    Is is FC or iscsi.

    Friday, November 15, 2019 8:13 PM
  • Hi,

    Was your issue resolved? 

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Lily

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 18, 2019 8:46 AM
  • Hi,

    Just checking in to see if the information provided was helpful. 

    Please let us know if you would like further assistance.

    Best Regards,

    Lily

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, November 20, 2019 1:18 AM