Share via

Event ID: 1069 - Restarted VMs

Richelle Lanuza 96 Reputation points
2021-07-27T07:29:16.827+00:00

May I know if you any idea why our Virtual Machines are being restarted?

The Cluster Events Error we have got see below:

Cluster resource 'Virtual Machine CS-FileServer' of type 'Virtual Machine' in clustered role 'CS-FileServer' failed.

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.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,199 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,730 questions

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Yuhan Deng 3,766 Reputation points Microsoft Vendor
    2021-07-28T02:42:11.017+00:00

    Hi Rslanuza，
    These events are very generic. Issue the command:
    cluster log /g
    This will generate a cluster.log file in the c:\windows\cluster\reports folder, review this log file for a better understanding why this resource is failing.
    You might also consider running cluster validation to check on the disks.
    Here’s a similar case:
    https://social.technet.microsoft.com/Forums/windows/en-US/0dbec820-69cf-4bad-91fd-5ddb09c06a3b/issue-with-setting-up-a-file-server-role-error-12541205-and-1069?forum=winserverClustering

    Thanks for your time.
    Best Regards,
    Danny

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments
  2. Leon Bollerup - Netsolutions AB 1 Reputation point
    2021-08-27T08:41:23.14+00:00

    I have the same issue - like always, i asume MS have messed up something in a update - its a hardware issue or its a update issue.

    Btw Yuhan, that command no longer works....

    PS C:\Windows\system32> cluster log /g
    Get-Cluster : A positional parameter cannot be found that accepts argument '/g'.
    At line:1 char:1

    • cluster log /g
    • ~~~~~~~~~~~~~~
    • CategoryInfo : InvalidArgument: (:) [Get-Cluster], ParameterBindingException
    • FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.FailoverClusters.PowerShell.GetClusterCommand
    0 comments
  3. Pompy George 136 Reputation points
    2021-09-21T08:12:40.383+00:00

    Any ideas ? Same issue here..

    Cluster resource Server of type 'Virtual Machine' in clustered role Server failed

    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.

    0 comments
  4. Leon Bollerup - Netsolutions AB 1 Reputation point
    2021-09-21T11:46:55.407+00:00

    One of our techs. found another post which seemed to indicate that it was a problem with Dynamic memory allocation.

    After disabling dynamic memory allocation, it seemed the issue stopped.

  5. Pompy George 136 Reputation points
    2021-09-23T07:27:42.43+00:00

    I have opened a Microsoft Support call and will post results here.
    VM's in question completely stable after changing from Dynamic to Static RAM.. Hummm

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.