question

rslanuza07 avatar image
0 Votes"
rslanuza07 asked LeonBollerupNetsolutionsAB-3256 commented

Event ID: 1069 - Restarted VMs

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-serverwindows-server-hyper-v
· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi Rslanuza,

I would like to check if the reply could be of help? If yes, please help accept answer, so that others meet a similar issue can find useful information quickly. If you have any other concerns or questions, please feel free to feedback.

Best Regards,
Danny

0 Votes 0 ·

Hi Rslanuza,

I would like to check if the issue has been fixed? If yes, please help accept answer, so that others meet a similar issue can find useful information quickly. If you have any other concerns or questions, please feel free to feedback.

Best Regards,
Danny

0 Votes 0 ·

Same issue here, only happening on a couple of VM's out of 40+, however they are the largest RAM usage VM's.

I've generated a cluster.log file and that shows nothing telling me where the issue is. Event viewer gives mixed messages.

Followed advice from others here and moving them from Dynamic RAM to Static, hopefully this helps... 38 pissed off RDS users isn't good!

If that doesn't work I'll have to take it off the failover cluster and just host it on one of the Hyper-V servers as a standalone server.

0 Votes 0 ·
PompyGeorge avatar image PompyGeorge SteveMcNeice-5408 ·

The VM's in question are instantly stable after changing from Dynamic to Static :-( :-)
I have opened a support call with Microsoft to investigate and will update here.

0 Votes 0 ·
YuhanDeng-MSFT avatar image
0 Votes"
YuhanDeng-MSFT answered

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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LeonBollerupNetsolutionsAB-3256 avatar image
0 Votes"
LeonBollerupNetsolutionsAB-3256 answered LeonBollerupNetsolutionsAB-3256 published

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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PompyGeorge avatar image
0 Votes"
PompyGeorge answered

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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LeonBollerupNetsolutionsAB-3256 avatar image
0 Votes"
LeonBollerupNetsolutionsAB-3256 answered PompyGeorge edited

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.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Ahh interesting, any idea why ?

0 Votes 0 ·

No, sadly not - other than when we stopped using it, the random reboots stopped - the only difference i can see here versus before the issue started is Windows updates.

0 Votes 0 ·
PompyGeorge avatar image PompyGeorge LeonBollerupNetsolutionsAB-3256 ·

And who knows what Windows Updates do ;-)

0 Votes 0 ·
PompyGeorge avatar image
0 Votes"
PompyGeorge answered LeonBollerupNetsolutionsAB-3256 commented

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

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Good.. are your machines in cluster aswell ? and are you on 2016 or 2019 ?

0 Votes 0 ·
PompyGeorge avatar image PompyGeorge LeonBollerupNetsolutionsAB-3256 ·

Cluster is 2016 - VM's 2019

Oddly, many 2019 VM's work fine with Virtual Memory, just not these 6.
I wonder if it is when you reconfigure one way and then the other.

We added RAM and switched to Virtual if I remember, but you had thought just a reboot of the VM needed.

0 Votes 0 ·

All of our machines with problems is RDP session host servers... storage, DC etc. is all fine.. but RDS with dynamic memory seems to be th culprit here

0 Votes 0 ·