Event Id # 1069, Microsoft-Windows-FailoverClustering

Question

_{Wednesday, November 1, 2017 5:18 AM}

Event viewer is showing errors about some VMs that cluster role is failed while they are working fine, Can anyone tell me how to fix this error.

The error description is mentioned below.

All replies (11)

_{Monday, December 4, 2017 1:47 PM ✅Answered}

As stated earlier, the 1069 error is the generic event reporting that something failed in the cluster.  It is simply telling you that the virtual machine failed.  You need to investigate why that particular virtual machine is failing.  And that might be a bit difficult because Windows Server 2003 is not a supported operating system.  Your best course of action is to build a new VM running a supported operating system and install whatever application you are running on the 2003 VM onto the newly created VM.

tim

_{Wednesday, November 1, 2017 12:37 PM}

Whatever editor you are using to enter your post messed up the text of the message.  Please just enter it with plain text.

Here is the generic description for cluster event 1069 - https://technet.microsoft.com/en-us/library/cc756225(v=ws.10).aspx.  That basically states that a resource failed.

You may want to run the cluster validation wizard to see what sort of warnings are detected.  Each warning needs to be investigated.  If this is a production cluster, you can selectively remove the disks used by the VMs from the wizard so the VMs will not failover.  That means you will miss testing the disk resources, and the cause of your issue might be there.  To get some of the disk tests, it is a good idea to have a disk witness.  Then you can leave in the disk tests for the disk witness and those tests will not impact the operation of the cluster.  You still miss the disk tests for the VMs, so you may consider running the complete suite of tests during a maintenance cycle.  The VMs will then automatically failover across nodes as the disks are tested.

tim

_{Friday, November 3, 2017 8:52 AM}

Hi FahadAhmed,

>Cluster resource 'Virtual Machine Prime_SessionState' of type 'Virtual Machine' in clustered role 'Prime_SessionState' failed.

What is the cluster role "Prime_SessionState", please check if there's a resource in the cluster is failed to bring online.

And as Tim suggested, please check the result of Cluster Validation Wizard, check if there's any error or warning.

Best Regards,

Anne

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, November 6, 2017 6:08 AM}

Hi FahadAhmed,

Just to check if you get any progress with your issue, could the above reply be of help? Welcome to feedback.

Best Regards,

Anne

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, November 13, 2017 8:51 AM}

I have checked all the cluster resources properly everything is fine, even the virtual machine"Prime_SessionState" is also working but it is showing error in failover event.

_{Monday, November 13, 2017 8:53 AM}

should I need to put the physical server in maintenance mode in order to run "Cluster Validation Wizard"?

_{Monday, November 13, 2017 9:10 AM}

No, the host has to be online.

Follow Tim's instruction on how to run the Cluster Validation.

_{Friday, November 24, 2017 8:12 AM}

If I run the Cluster validation will it effect the VMs that are running in the production Cluster?

_{Friday, November 24, 2017 2:40 PM}

It depends upon how you run the wizard.  The wizard is designed to be used as a troubleshooting tool, and to be used on production environments.  As I noted in my first post, running the disk portion of the wizard can cause the failover (not live migration) of VMs.  Do not include any of the disks on which VM files are stored, and VMs will not be affected.  It is not a complete test, as you are not testing those disks, but it does run a lot of other very useful tests.  And, if you have a disk witness, you can run the disk tests just against that disk.

tim

_{Monday, December 4, 2017 6:21 AM}

Thanks Tim for your valuable response, during troubleshooting, I have found that this error 1069 is only showing with win 2003 Server while the servers are not showing this error in the cluster (e.g win 2008, 2008 R2, Win 2012 & 2012 R2.

This error 1069 is showing in other clusters also with same win 2003 servers, although VMs are working fine errors 1069 are frequently occurring in "Cluster Event". Cluster Functional level is Win 2012 R2. Error details are mentioned below.

"Cluster resource 'Virtual Machine Primeweb_bk' of type 'Virtual Machine' in clustered role 'Primeweb_bk' failed.

Based on the <g class="gr_ gr_13 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling" data-gr-id="13" id="13">failure</g> 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".

<Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**"\>

- <System>

  <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />

  <EventID>1069</EventID>

  <Version>1</Version>

  <Level>2</Level>

  <Task>3</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000000000000000</Keywords>

  <TimeCreated SystemTime="2017-11-27T05:44:38.538530800Z" />

  <EventRecordID>2539568</EventRecordID>

  <Correlation />

  <Execution ProcessID="3284" ThreadID="14924" />

  <Channel>System</Channel>

  <Computer>PKKHICS02V04.domestic.hbl.com</Computer>

  <Security UserID="S-1-5-18" />

  </System>

- <EventData>

  <Data Name="ResourceName">Virtual Machine Primeweb_bk</Data>

  <Data Name="ResourceGroup">Primeweb_bk</Data>

  <Data Name="ResTypeDll">Virtual Machine</Data>

  </EventData>

  </Event>

_{Friday, December 8, 2017 4:55 AM}

Thanks for your support.