Microsoft-Windows-FailoverClustering

762 events across 6 channels

Event ID	Title	Channel
1000	Cluster service suffered an unexpected fatal error at line %1 of source module …	System
1000		Operational
1001	Cluster service failed a validity check on line %1 of source module %2.	System
1001		Operational
1002	Cluster service handled an unexpected error at line %1 of source module %2.	System
1002		Operational
1006	Cluster service was halted due to incomplete connectivity with other cluster …	System
1006		Operational
1007	A new node, %1, has been added to the failover cluster.	Operational
1011	Cluster node %1 has been evicted from the failover cluster.	System
1011		Operational
1024	The registry checkpoint for cluster resource '.	System
1024		Operational
1034	Cluster physical disk resource '.	System
1034		Operational
1035	While disk resource '.	System
1035		Operational
1037	The file system for one or more partitions on the disk for resource '.	System
1037		Operational
1038	Ownership of cluster disk '.	System
1038		Operational
1039	Generic application '.	System
1039		Operational
1040	Generic service '.	System
1040		Operational
1041	Generic service '.	System
1041		Operational
1042	Generic service '.	System
1042		Operational
1044	Encountered a failure when attempting to create a new NetBIOS interface while …	System
1044		Operational
1045	No matching network interface found for resource '.	System
1045		Operational
1046	Cluster IP address resource '.	System
1046		Operational
1047	Cluster IP address resource '.	System
1047		Operational
1048	Cluster IP address resource '.	System
1048		Operational
1049	Cluster IP address resource '.	System
1049		Operational
1050	Cluster network name resource '.	System
1050		Operational
1051	Cluster network name resource '.	System
1051		Operational
1052	Cluster Network Name resource '.	System
1052		Operational
1053	Cluster File Share '.	System
1053		Operational
1054	Health check for file share resource '.	System
1054		Operational
1055	Health check for file share resource '.	System
1055		Operational
1057	The cluster database could not be loaded.	System
1057		Operational
1061	The Cluster service successfully formed the failover cluster '.	Operational
1062	This node has successfully joined the failover cluster '.	Operational
1063	The Cluster service was successfully stopped.	Operational
1066	Cluster disk resource '.	System
1066		Operational
1068	Cluster file share resource '.	System
1068		Operational
1069	Cluster resource '.	System
1069		Operational
1070	The node failed to join failover cluster '.	System
1070		Operational
1071	The operation attempted on cluster resource '.	System
1071		Operational
1073	The Cluster service was halted to prevent an inconsistency within the failover …	System
1073		Operational
1077	Health check for IP interface '.	System
1077		Operational
1078	Cluster IP address resource '.	System
1078		Operational
1080	The Cluster service failed to update the cluster database (error code '%1').	System
1080		Operational
1090	The Cluster service cannot be started.	System
1090		Operational
1092	Failed to form cluster '.	System
1092		Operational
1093	The Cluster service cannot identify node '.	System
1093		Operational
1094	The cluster common property SecurityLevel cannot be changed on this cluster.	System
1094		Operational
1105	The Cluster service failed to start because it was unable to register …	System
1105		Operational
1116	Cluster network name resource '.	Operational
1119	Cluster network name resource '.	System
1119		Operational
1121	Encrypted settings for cluster resource '.	System
1121		Operational
1125	Cluster network interface '.	Operational
1126	Cluster network interface '.	System
1126		Operational
1127	Cluster network interface '.	System
1127		Operational
1128	Cluster network '.	Operational
1129	Cluster network '.	System
1129		Operational
1130	Cluster network '.	System
1130		Operational
1131	Cluster network interface '.	Operational
1132	Cluster network interface '.	Operational
1133	Cluster network '.	Operational
1134	Cluster network '.	Operational
1135	Cluster node '.	System
1135		Operational
1136	The cluster service has detected an Azure host maintenance event is about to …	System
1136		Operational
1137	Move of cluster role '.	System
1137		Operational
1138	Cluster file share resource '.	System
1138		Operational
1139	The cluster service has detected an Azure host maintenance event has been …	System
1139		Operational
1140	The cluster service has detected an Azure host maintenance event has been …	System
1140		Operational
1141	Cluster file share resource '.	System
1141		Operational
1142	Cluster file share resource '.	System
1142		Operational
1146	The cluster Resource Hosting Subsystem (RHS) process was terminated and will be …	System
1146		Operational
1149	The DNS Host (A) and Pointer (PTR) records associated with Cluster resource '.	System
1149		Operational
1150	The removal of the DNS Pointer (PTR) record '.	System
1150		Operational
1151	The removal of the DNS Host (A) record '.	System
1151		Operational
1153	The Cluster service is attempting to fail over the clustered role '.	Operational
1154	The Cluster service is attempting to fail back the clustered role '.	Operational
1155	The pending move for the role '.	System
1155		Operational
1156	Cluster resource '.	Operational
1157	Cluster resource '.	Operational
1158	Cluster role '.	Operational
1159	Cluster role '.	Operational
1177	The Cluster service is shutting down because quorum was lost.	System
1177		Operational
1181	Cluster resource '.	System
1181		Operational
1182	Cluster resource '.	System
1182		Operational
1183	Cluster disk resource '.	System
1183		Operational
1186	The password associated with the Cluster service domain account is being updated …	Operational
1190	Cluster network name resource '.	Operational
1191	Cluster network name resource '.	System
1191		Operational
1192	Cluster network name resource '.	System
1192		Operational
1193	Cluster network name resource '.	System
1193		Operational
1194	Cluster network name resource '.	System
1194		Operational
1195	Cluster network name resource '.	System
1195		Operational
1196	Cluster network name resource '.	System
1196		Operational
1197	Cluster network name resource '.	System
1197		Operational
1198	Cluster network name resource '.	System
1198		Operational
1200	The Cluster service is attempting to bring the clustered role '.	Operational
1201	The Cluster service successfully brought the clustered role '.	Operational
1203	The Cluster service is attempting to bring the clustered role '.	Operational
1204	The Cluster service successfully brought the clustered role '.	Operational
1205	The Cluster service failed to bring clustered role '.	System
1205		Operational
1206	The computer object associated with the cluster network name resource '.	System
1206		Operational
1207	The computer object associated with the cluster network name resource '.	System
1207		Operational
1208	Cluster disk resource '.	System
1208		Operational
1209	Cluster service is requesting a bus reset for device '.	Operational
1211	Cluster network name resource '.	System
1211		Operational
1212	Cluster network name resource '.	System
1212		Operational
1213	Cluster network name resource '.	System
1213		Operational
1214	Cluster Network Name resource cannot be registered with Netbios.	System
1214		Operational
1215	Cluster network name resource '.	System
1215		Operational
1216	A name change operation on the cluster core netname resource has failed.	System
1216		Operational
1217	Cluster network name resource '.	Operational
1218	Cluster network name resource '.	System
1218		Operational
1219	Cluster network name resource '.	System
1219		Operational
1220	The computer account for resource '.	System
1220		Operational
1221	Cluster network name resource '.	System
1221		Operational
1222	The computer object associated with cluster network name resource '.	System
1222		Operational
1223	Cluster IP address resource '.	System
1223		Operational
1224	Cluster IP address resource '.	Operational
1226	Network Name resource '.	System
1226		Operational
1227	Network Name resource '.	System
1227		Operational
1228	Cluster network name resource '.	System
1228		Operational
1229	Cluster network name resource '.	System
1229		Operational
1230	A component on the server did not respond in a timely fashion.	System
1230		Operational
1231	Cluster network name resource '.	System
1231		Operational
1232	Entry point '.	System
1232		Operational
1233	Cluster generic script resource '.	System
1233		Operational
1234	The Cluster service has detected that its service account is missing one or more …	System
1234		Operational
1237	Cluster resource '.	Operational
1238	Cluster resource '.	Operational
1239	Cluster IP address resource '.	Operational
1240	Cluster IP address resource '.	System
1240		Operational
1241	Cluster IP address resource '.	Operational
1242	Lease of IP address '.	System
1242		Operational
1243	Cluster IP address resource '.	System
1243		Operational
1244	Cluster IP address resource '.	Operational
1245	Cluster IP address resource '.	System
1245		Operational
1246	Settings have changed for cluster network '.	Operational
1247	The Security Identifier (SID) type for the cluster service is configured as '.	System
1247		Operational
1248	The Security Identifier (SID) '.	System
1248		Operational
1249	Cluster IPv6 tunnel address resource '.	Operational
1250	Cluster resource '.	System
1250		Operational
1251	Clustered role '.	System
1251		Operational
1252	Cluster resource '.	Operational
1253	Resource '.	Operational
1254	Clustered role '.	System
1254		Operational
1255	Cluster resource '.	System
1255		Operational
1256	Cluster network name resource failed registration of one or more associated DNS …	System
1256		Operational
1257	Cluster network name resource failed registration of one or more associated DNS …	System
1257		Operational
1258	Cluster network name resource failed registration of one or more associated DNS …	System
1258		Operational
1259	Cluster network name resource failed registration of one or more associated DNS …	System
1259		Operational
1260	Cluster network name resource failed to modify the DNS registration.	System
1260		Operational
1261	Cluster network name resource failed to modify the DNS registration.	System
1261		Operational
1263	Cluster network name resource failed to publish the PTR record in the DNS …	System
1263		Operational
1264	Cluster network name resource failed to publish the PTR record in the DNS …	System
1264		Operational
1265	Cluster resource type '.	System
1265		Operational
1280	Sponsor tried to Create Security Context using Package='.	Operational
1281	Joiner tried to Create Security Context using Package='.	Operational
1282	Security Handshake between local and remote endpoints '.	System
1282		Operational
1289	The Cluster Service was unable to access network adapter '.	System
1289		Operational
1360	Cluster IP address resource '.	System
1360		Operational
1361	IPv6 Tunnel address resource '.	System
1361		Operational
1362	Cluster IP address resource '.	System
1362		Operational
1363	IPv6 tunnel address resource '.	System
1363		Operational
1537	A backup operation of the cluster configuration data has been initiated.	Operational
1538	The backup operation for the cluster configuration data completed successfully.	Operational
1539	A restore operation of the cluster configuration data has been initiated.	Operational
1540	The restore operation for the cluster configuration data completed successfully.	Operational
1541	The backup operation for the cluster configuration data has been aborted because …	System
1541		Operational
1542	The restore request for the cluster configuration data has failed.	System
1542		Operational
1543	The restore operation of the cluster configuration data has failed.	System
1543		Operational
1544	The backup operation for the cluster configuration data has been canceled.	System
1544		Operational
1545	The restore operation for the cluster configuration data has failed.	System
1545		Operational
1546	Node '.	System
1546		Operational
1547	Node '.	System
1547		Operational
1548	Node '.	System
1548		Operational
1549	Node '.	Operational
1550	Node '.	System
1550		Operational
1551	Node '.	System
1551		Operational
1552	The cluster service detected that the witness disk designation has changed - …	Operational
1553	This cluster node has no network connectivity.	System
1553		Operational
1554	This cluster node has lost all network connectivity.	System
1554		Operational
1555	Attempting to use IPv4 for '.	System
1555		Operational
1556	The cluster service encountered an unexpected problem and will be shut down.	System
1556		Operational
1557	Cluster service failed to update the cluster configuration data on the witness …	System
1557		Operational
1558	The cluster service detected a problem with the witness resource.	System
1558		Operational
1559	File share '.	System
1559		Operational
1560	Cluster file share resource '.	System
1560		Operational
1561	Cluster service failed to start because this node detected that it does not have …	System
1561		Operational
1562	File share witness resource '.	System
1562		Operational
1563	File share witness resource '.	System
1563		Operational
1564	File share witness resource '.	System
1564		Operational
1565	This cluster node is running with a different message security level ('%1') than …	Operational
1566	Cluster network name resource '.	System
1566		Operational
1567	Cluster service failed to change the trace log size.	System
1567		Operational
1568	Cluster disk resource '.	System
1568		Operational
1569	Network '.	System
1569		Operational
1570	Node '.	System
1570		Operational
1571	Node '.	System
1571		Operational
1572	Node '.	System
1572		Operational
1573	Node '.	System
1573		Operational
1574	The failover cluster database could not be unloaded.	System
1574		Operational
1575	An attempt to forcibly start the cluster service has failed because the cluster …	System
1575		Operational
1576	Cluster network name resource '.	System
1576		Operational
1577	Cluster network name resource '.	System
1577		Operational
1578	Cluster network name resource '.	System
1578		Operational
1579	Cluster network name resource '.	System
1579		Operational
1580	Cluster network name resource '.	System
1580		Operational
1581	The restore request for the cluster configuration data failed to make a copy of …	System
1581		Operational
1582	Cluster Service failed to move the restored cluster hive at '.	System
1582		Operational
1583	Cluster service failed to disable Internet Protocol security (IPsec) on the …	System
1583		Operational
1584	A backup application initiated a VSS snapshot on Cluster Shared Volume '.	System
1584		Operational
1585	Cluster file server resource '.	System
1585		Operational
1586	Cluster file server resource '.	System
1586		Operational
1587	Cluster file server resource '.	System
1587		Operational
1588	Cluster file server resource '.	System
1588		Operational
1589	Cluster network name resource '.	System
1589		Operational
1592	Cluster node '.	System
1592		Operational
1593	The failover cluster database could not be unloaded and any potentially …	System
1593		Operational
1594	Cluster service successfully upgraded the cluster functional level.	System
1594		Operational
1600	Cluster service failed to set the permissions on the cluster computer object '.	System
1600		Operational
1601	The Cluster service successfully brought the Scale-out file server clone online.	Operational
1602	The Cluster service successfully brought the Scale-out file server clone …	Operational
1603	Cluster service failed to create a clone of the Scale Out File Server resource.	System
1603		Operational
1604	Cluster disk resource '.	System
1604		Operational
1605	Cluster disk resource '.	System
1605		Operational
1606	Cluster disk resource '.	System
1606		Operational
1607	Cluster disk resource '.	System
1607		Operational
1608	File Server could not start because expected dependency on 'Network Name' …	System
1608		Operational
1609	Scale Out File Server could not start because expected dependency on …	System
1609		Operational
1632	The creation of the cluster failed.	System
1632		Operational
1633	The Cluster service failed to bring clustered role '.	Operational
1634	Clustered service or application '.	Operational
1635	Cluster resource '.	Operational
1636	The Cluster service has changed the password of account '.	Operational
1637	Cluster resource '.	Operational
1638	Cluster resource '.	Operational
1639	Cluster resource '.	Operational
1640	Clustered roles with priority less than '.	Operational
1641	Clustered role '.	Operational
1648	Clustered role '.	Operational
1649	Cluster resource '.	Operational
1650	Cluster has established a UDP connection from local endpoint %1 connected to …	Operational
1651	Cluster has received notification that Adapter %1 is now in a connected state.	Operational
1652	Cluster node '.	System
1652		Operational
1653	Cluster node '.	System
1653		Operational
1654	Cluster Disjoint IP address resource '.	System
1654		Operational
1655	Cluster Disjoint IP address resource '.	System
1655		Operational
1656	Failed to add the IP Address '.	System
1656		Operational
1657	Health check for IP interface '.	System
1657		Operational
1658	Cloud witness resource could not reach Microsoft Azure storage services.	System
1658		Operational
1659	Cloud witness resource failed to authenticate with Microsoft Azure storage …	System
1659		Operational
1664	Upgrading the functional level of the cluster failed.	System
1664		Operational
1665	Online operation for the Physical Disk resource '.	Operational
1666	Online operation for the Physical Disk resource '.	Operational
1667	Offline operation for the Physical Disk resource '.	Operational
1668	Offline operation for the Physical Disk resource '.	Operational
1669	Cluster physical disk resource took longer than expected to reach an online …	Operational
1670	Cluster physical disk resource successfully brought the resource online.	Operational
1671	Cluster physical disk resource cannot be brought online.	System
1671		Operational
1672	Cluster node '.	System
1672		Operational
1673	Cluster node '.	System
1673		Operational
1674	Group '.	Operational
1675	Cluster node '.	System
1675		Operational
1676	Local cluster node has been quarantined by '.	System
1676		Operational
1677	Node drain failed on Cluster node %1.	System
1677		Operational
1680	Cluster node '.	System
1680		Operational
1681	Virtual machines on node '.	System
1681		Operational
1682	Virtual machine '.	System
1682		Operational
1683	The cluster service was unable to reach any available domain controller on the …	System
1683		Operational
1684	Cluster network name resource failed to find the associated computer object in …	System
1684		Operational
1685	Cluster network name resource failed to find the associated computer object in …	System
1685		Operational
1686	Cluster network name resource found the associated computer object in Active …	System
1686		Operational
1687	Cluster network name resource found the associated computer object in Active …	System
1687		Operational
1688	Cluster network name resource detected that the associated computer object in …	System
1688		Operational
1689	The cluster service detected a service which is not compatible with Failover …	System
1689		Operational
1690	The cluster role was not brought online automatically because …	System
1690		Operational
1691	The cluster service started with the IgnorePersistentStateOnStartup parameter …	System
1691		Operational
1792	Cluster physical disk resource failed periodic health check.	System
1792		Operational
1793	Cluster physical disk resource failed to come online.	System
1793		Operational
1794	Cluster physical disk resource failed to go offline.	System
1794		Operational
1795	Cluster physical disk resource encountered an error while attempting to …	System
1795		Operational
1808	The cluster load balancer has identified the current node is exceeding the CPU …	Operational
1809	This node has been joined to a cluster that has Storage Spaces Direct enabled, …	System
1809		Operational
1810	Cluster Physical Disk Resource added a protector to a BitLocker encrypted …	Operational
1811	Cluster Physical Disk Resource failed to add a protector to a BitLocker …	Operational
1812	Cluster Physical Disk Resource completed a storage operation.	Operational
1813	Cluster Physical Disk Resource completed resource online.	Operational
1814	Cluster Physical Disk Resource completed resource offline.	Operational
1815	Cluster Physical Disk Resource completed resource terminate.	Operational
1816	Cluster Physical Disk Resource could not find expected number of usable data …	Operational
1817	Cluster resource '.	Operational
1824	Cluster Physical Disk Resource contains a BitLocker protected volume, but the …	Operational
1825	Cluster Physical Disk Resource saved a protector to a BitLocker encrypted …	Operational
1826	Node drain failed on Cluster node %1.	Operational
1827	Node drain succeeded on Cluster node %1.	Operational
1828	Node drain started on Cluster node %1.	Operational
1829	Node drain started second attempt on Cluster node %1.	Operational
1830	Node failback failed on Cluster node %1.	Operational
1831	Node failback succeeded on Cluster node %1 after being called from %2.	Operational
1832	Node Resume started on Cluster node %1.	Operational
1833	Node failback started on Cluster node %1 due to being called from %2.	Operational
1840	Node Failback did not run on Cluster node %1 after being called from %2.	Operational
1841	Node resume succeeded on Cluster node %1 after being called from %2.	Operational
2049		Operational
2049		Diagnostic
2050		Operational
2050		Diagnostic
2051		Operational
2051		Diagnostic
2052		Operational
2052		Diagnostic
4096		Operational
4096	[NETFTAPI] received %1 for %2 (%3).	Diagnostic
4097		Operational
4097	[NETFTAPI] received %1 for %2 (%3).	Diagnostic
4098		Operational
4098	[NETFTAPI] received %1 for %2.	Diagnostic
4099		Operational
4099	[NETFTAPI] received %1 for %2.	Diagnostic
4100		Operational
4100	[NETFTAPI] received %1.	Diagnostic
4101		Operational
4101	[NETFTAPI] Signaled %1 event for %2.	Diagnostic
4102		Operational
4102	[NETFTAPI] Signaled %1 event for %2.	Diagnostic
4103		Operational
4103	[NETFTAPI] Signaled %1 event, local address %2:%3 remote address %4:%5.	Diagnostic
4104		Operational
4104	[NETFTAPI] Signaled %1 event, local address [%2]:%3 remote address [%4]:%5.	Diagnostic
4105		Operational
4105	[NETFTAPI] Signaled %1 event, alias %2.	Diagnostic
4106		Operational
4106	[NETFTAPI] Failed to allocate %1 network address entry (status %2).	Diagnostic
4107		Operational
4107	[NETFTAPI] Failed to allocate %1 network address entry (status %2).	Diagnostic
4108		Operational
4108	[NETFTAPI] Failed to query initialization parameters for %1 (status %2).	Diagnostic
4109		Operational
4109	[NETFTAPI] Failed to query initialization parameters for %1 (status %2).	Diagnostic
4110		Operational
4110	[NETFTAPI] Failed to query parameters for %1 (status %2).	Diagnostic
4111		Operational
4111	[NETFTAPI] Failed to query parameters for %1 (status %2).	Diagnostic
4112		Operational
4112	[NETFTAPI] Subscriber thrown exception %1 processing NETFT notification.	Diagnostic
4113		Operational
4113	[NETFTAPI] Failed to allocate %1 network interface entry (status %2).	Diagnostic
4114		Operational
4114	[NETFTAPI] The IPv4/802 provider is not present	Diagnostic
4115		Operational
4115	[NETFTAPI] The IPv6/802 provider is not present	Diagnostic
4116		Operational
4116	[NETFTAPI] Event processing thread failed to register for NETFT event (status …	Diagnostic
4117		Operational
4117	[NETFTAPI] Event processing thread completed processing loop (status %1).	Diagnostic
4118		Operational
4118	[NETFTAPI] The watchdog miniport is halting.	Diagnostic
4608	The list of clustered disks has been retrieved during cluster node cleanup.	Operational
4609		Operational
4609	Cluster service failed to retrieve the list of clustered disks while destroying …	System
4610	Clustered disks have been released by the Partition Manager while destroying the …	Operational
4611		Operational
4611	Clustered disk with ID '.	System
4612	The clustered disks database has been cleared as part of cluster node cleanup.	Operational
4613		Operational
4613	The cluster service failed to properly cleanup a clustered disk with ID '.	System
4614	The cluster service has been stopped and set as disabled as part of cluster node …	Operational
4615		Operational
4615	Disabling the cluster service during cluster node cleanup, has failed.	System
4616		Operational
4616	Termination of the cluster service during cluster node cleanup has not completed …	System
4617	The cluster service registry entries on this machine have been reset as part of …	Operational
4618		Operational
4618	Resetting cluster service registry entries during cluster node cleanup failed.	System
4619	The cluster Windows registry hive has been unloaded.	Operational
4620		Operational
4620	Unloading the cluster service registry hive during cluster node cleanup failed.	System
4621		Operational
4621	This node was sucessfully removed from the cluster.	System
4622		Operational
4622	The Cluster service encountered an error during node cleanup.	System
4623	The IPSec security association timeout has been reset on this machine as part of …	Operational
4624		Operational
4624	Resetting the IPSec security association timeout registry value failed during …	System
4625		Operational
4625	Resetting the IPSec security association timeout registry value failed during …	System
4626	All clustered tasks on this node have been deleted as part of node cleanup.	Operational
4627		Operational
4627	Deletion of clustered tasks during node cleanup failed.	System
4628	During node cleanup, the local user account that is managed by the cluster was …	Operational
4629		Operational
4629	During node cleanup, the local user account that is managed by the cluster was …	System
4864		Operational
4864	Volume shadow copy service task resource '.	System
4865		Operational
4865	Volume shadow copy service task resource '.	System
4866		Operational
4866	Volume shadow copy service task resource '.	System
4867		Operational
4867	Volume shadow copy service task resource '.	System
4868		Operational
4868	Cluster service failed to start the cluster log trace session.	System
4869		Operational
4869	User mode health monitoring has detected that the system is not being …	System
4870		Operational
4870	User mode health monitoring has detected that the system is not being …	System
4871		Operational
4871	The cluster service failed to start.	System
4872		Operational
4872	The failover cluster virtual adapter failed to generate a unique MAC address.	System
4873		Operational
4873	The cluster service has detected that the failover cluster virtual adapter has …	System
4874		Operational
4874	User mode health monitoring has detected that the system is not being …	System
5120		Operational
5120	Cluster Shared Volume '.	System
5121		Operational
5121	Cluster Shared Volume '.	System
5122	Cluster Shared Volume '.	Operational
5123		Operational
5123	Cluster service failed to create the Cluster Shared Volumes root directory '.	System
5124		Operational
5124	Cluster Shared Volumes root directory '.	System
5125		Operational
5125	Cluster Shared Volume '.	System
5126		Operational
5126	Cluster Shared Volume '.	System
5128		Operational
5128	Physical disk resource '.	System
5129	Cluster Shared Volumes has been enabled on this cluster by user '.	Operational
5130	Cluster Shared Volumes has been disabled on this cluster by user '.	Operational
5131	Cluster Disk '.	Operational
5132	Cluster Disk '.	Operational
5133		Operational
5133	Cluster Disk '.	System
5134		Operational
5134	Cluster service failed to set the permissions (ACL) on the Cluster Shared …	System
5135		Operational
5135	Cluster service failed to set the permissions on the Cluster Shared Volume …	System
5136		Operational
5136	Cluster Shared Volume '.	System
5137	Cluster Shared Volume '.	Operational
5138	Cluster Shared Volume '.	Operational
5139	Cluster Shared Volume '.	Operational
5140	Cluster Shared Volume '.	Operational
5141	Cluster Shared Volume '.	Operational
5142		Operational
5142	Cluster Shared Volume '.	System
5143		Operational
5143	Move of the disk ('%2') is vetoed based on the current state of the Cache …	System
5144		Operational
5144	While adding the disk ('%1') to Cluster Shared Volumes, setting explicit …	System
5145		Operational
5145	Cluster disk resource '.	System
5146		Operational
5146	Move of the Cluster Shared Volume resource '.	System
5147		Operational
5147	Move of the Cluster Shared Volume resource '.	System
5148		Operational
5148	Move of the Cluster Shared Volume resource '.	System
5149		Operational
5149	Cache size resized to '.	System
5150		Operational
5150	Cluster physical disk resource '.	System
5151	Cluster Shared Volume '.	Operational
5152	Cluster Shared Volume '.	Operational
5153	Cluster Shared Volume '.	Operational
5154	Cluster Shared Volume '.	Operational
5155	Cluster Shared Volume resource '.	Operational
5156		Operational
5156	Cluster Shared Volume '.	System
5157		Operational
5157	Cluster Shared Volume '.	System
5158	SMB client connection to server '.	Operational
5159	SMB client connection from source address '.	Operational
5160	SMB client disconnect state for connection to server '.	Operational
5161	The volume name '.	Operational
5162		Operational
5162	Move of the Cluster Shared Volume resource '.	System
5163	Cluster service disabled RDMA on the SMB instance for %1 IO on this node.	Operational
5164	Cluster service enabled RDMA on the SMB instance for %1 IO on this node.	Operational
5200		Operational
5200	Cluster service failed to create a cluster identity token for Cluster Shared …	System
5216		Operational
5216	Software snapshot creation on Cluster Shared Volume '.	System
5217		Operational
5217	Software snapshot creation on Cluster Shared Volume(s) ('%1') with snapshot set …	System
5218		Operational
5218	Cluster physical disk resource '.	System
5219		Operational
5219	Cluster service failed to register the Cluster Shared Volumes snapshot provider …	System
5220		Operational
5220	Cluster Service detected the fault domain settings may not be configured …	System
5235	Task '.	Operational
5237	Task '.	Operational
5245	Task '.	Operational
5264	Physical Disk resource '.	Operational
5265	Cluster network '.	Operational
5266	Cluster network interface '.	Operational
5267	ClusterMrr API request timed out because some nodes did not reply to the request …	Operational
5268	Too many ClusterMrr API requests are outstanding on this node.	Operational
5269	ClusterMrr API request handler timed out on this node.	Operational
5377		Operational
5377	An internal Cluster service operation exceeded the defined threshold of '.	System
5393	The Cluster detected that this node is slower than others and degrade Cluster …	Operational
5394		Operational
5394	The Cluster service encountered some storage errors while trying to bring …	System
5395		Operational
5395	Cluster is moving the group for storage pool '.	System
5396		Operational
5396	The Cluster service on this node is shutting down because it has detected that …	System
5397		Operational
5397	The cluster resource '.	System
5398		Operational
5398	Cluster failed to start.	System
5399		Operational
5399		DiagnosticVerbose
5400		Operational
5400		DiagnosticVerbose
5401		Operational
5401		DiagnosticVerbose
5408		Operational
5408		DiagnosticVerbose
5409		Operational
5409		ClusterSetDiagnostic
5410		Operational
5410		ClusterSetDiagnostic
5411		Operational
5411		ClusterSetDiagnostic
5412		Operational
5412		ClusterSetDiagnostic
5413		Operational
5413	The cluster has cold started.	System
5414		Operational
5414	Failed to create the clustered role ".	System
5415	Group is about to move to new owner.	Operational
5416	Property change has occured.	Operational
5417	Cluster Service has terminated due to a fatal error.	Operational
5424		Operational
5424	Clusapi handle of type %1 has been marked as dead.	System
43968		Operational
43968	Volume %1 activating.	Performance-CSV
43969		Operational
43969	Volume %1 deactivating.	Performance-CSV
43970		Operational
43970	IO %1 is of type %2.	Performance-CSV
43971		Operational
43971	IO %1 now in state %2.	Performance-CSV
43972		Operational
43972	fsContext %1 opened for file %3.	Performance-CSV
43973		Operational
43973	fsContext %1 closed.	Performance-CSV
43974		Operational
43974	fsContext %1 is in state %2.	Performance-CSV

Event ID 1000 — Cluster service suffered an unexpected fatal error at line %1 of source module %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service suffered an unexpected fatal error at line %1 of source module %2. The error code was %3.

Fields

Name	Description
`Parameter1`	—
`Parameter2`	—
`Parameter3`	—

Event ID 1000 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Parameter1`	—
`Parameter2`	—
`Parameter3`	—

Event ID 1001 — Cluster service failed a validity check on line %1 of source module %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed a validity check on line %1 of source module %2. "%3"

Fields

Name	Description
`Parameter1`	—
`Parameter2`	—
`Parameter3`	—
`NodeName`	—

Event ID 1001 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Parameter1`	—
`Parameter2`	—
`Parameter3`	—
`NodeName`	—

Event ID 1002 — Cluster service handled an unexpected error at line %1 of source module %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service handled an unexpected error at line %1 of source module %2. The error code was %3.

Fields

Name	Description
`Parameter1`	—
`Parameter2`	—
`Parameter3`	—
`NodeName`	—

Event ID 1002 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Parameter1`	—
`Parameter2`	—
`Parameter3`	—
`NodeName`	—

Event ID 1006 — Cluster service was halted due to incomplete connectivity with other cluster nodes.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service was halted due to incomplete connectivity with other cluster nodes.

Fields

Name	Description
`NodeName`	—

Event ID 1006 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1007 — A new node, %1, has been added to the failover cluster.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

A new node, %1, has been added to the failover cluster.

Fields

Name	Description
`NodeName`	—

Event ID 1011 — Cluster node %1 has been evicted from the failover cluster.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster node %1 has been evicted from the failover cluster.

Fields

Name	Description
`NodeName`	—

Event ID 1011 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1024 — The registry checkpoint for cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The registry checkpoint for cluster resource '%1' could not be restored to registry key HKEY_LOCAL_MACHINE\%2. The resource may not function correctly. Make sure that no other processes have open handles to registry keys in this registry subtree.

Fields

Name	Description
`ResourceName`	—
`RegistryPath`	—

Event ID 1024 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`RegistryPath`	—

Event ID 1034 — Cluster physical disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster physical disk resource '%1' cannot be brought online because the associated disk could not be found. The expected signature of the disk was '%2'. If the disk was replaced or restored, in the Failover Cluster Manager snap-in, you can use the Repair function (in the properties sheet for the disk) to repair the new or restored disk. If the disk will not be replaced, delete the associated disk resource.

Fields

Name	Description
`ResourceName`	—
`DiskSignature`	—

Event ID 1034 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DiskSignature`	—

Event ID 1035 — While disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

While disk resource '%1' was being brought online, access to one or more volumes failed with error '%2'. Run the Validate a Configuration wizard to check your storage configuration. Optionally you may want to run Chkdsk to verify the integrity of all volumes on this disk.

Fields

Name	Description
`ResourceName`	—
`Status`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1035 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1037 — The file system for one or more partitions on the disk for resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The file system for one or more partitions on the disk for resource '%1' may be corrupt. Run the Validate a Configuration wizard to check your storage configuration. Optionally, you may want to run Chkdsk to verify the integrity of all volumes on this disk.

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1037 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1038 — Ownership of cluster disk '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Ownership of cluster disk '%1' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1038 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1039 — Generic application '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Generic application '%1' could not be brought online (with error '%2') during an attempt to create the process.  Possible causes include: the application may not be present on this node, the path name may have been specified incorrectly, the binary name may have been specified incorrectly.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1039 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1040 — Generic service '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Generic service '%1' could not be brought online (with error '%2') during an attempt to open the service.  Possible causes include: the service is either not installed or the specified service name is invalid.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1040 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1041 — Generic service '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Generic service '%1' could not be brought online (with error '%2') during an attempt to start the service.  Possible cause: the specified service parameters might be invalid.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1041 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1042 — Generic service '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Generic service '%1' failed with error '%2'. Please examine the application event log.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1042 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1044 — Encountered a failure when attempting to create a new NetBIOS interface while bringing resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Encountered a failure when attempting to create a new NetBIOS interface while bringing resource '%1' online (error code '%2'). The maximum number of NetBIOS names may have been exceeded.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1044 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1045 — No matching network interface found for resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

No matching network interface found for resource '%1' IP address '%2' (return code was '%3').  If your cluster nodes span different subnets, this may be normal.

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`Status`	—

Event ID 1045 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`Status`	—

Event ID 1046 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' cannot be brought online because the subnet mask value is invalid.  Please check your IP address resource properties.

Fields

Name	Description
`ResourceName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1046 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1047 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' cannot be brought online because the address value is invalid.  Please check your IP address resource properties.

Fields

Name	Description
`ResourceName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1047 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1048 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' failed to come online. Configuration data for the network adapter corresponding to cluster network interface '%2' could not be determined (error code was '%3'). Please check that the IP address resource is configured with the correct address and network properties.

Fields

Name	Description
`ResourceName`	—
`NetInterfaceName`	—
`Status`	—

Event ID 1048 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`NetInterfaceName`	—
`Status`	—

Event ID 1049 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' cannot be brought online because a duplicate IP address '%2' was detected on the network.  Please ensure all IP addresses are unique.

Fields

Name	Description
`ResourceName`	—
`Parameter2`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1049 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Parameter2`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1050 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' cannot be brought online because name '%2' matches this cluster node name.  Ensure that network names are unique.

Fields

Name	Description
`ResourceName`	—
`Name`	—

Event ID 1050 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Name`	—

Event ID 1051 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' cannot be brought online. Ensure that the network adapters for dependent IP address resources have access to at least one DNS server. Alternatively, enable NetBIOS for dependent IP addresses.

Fields

Name	Description
`ResourceName`	—

Event ID 1051 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 1052 — Cluster Network Name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Network Name resource '%1' cannot be brought online because the name could not be added to the system. The associated error code is stored in the data section.

Fields

Name	Description
`ResourceName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1052 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1053 — Cluster File Share '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster File Share '%1' cannot be brought online because the share could not be created.

Fields

Name	Description
`ResourceName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1053 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1054 — Health check for file share resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Health check for file share resource '%1' failed.  Retrieving information for share '%2' (scoped to network name %3) returned error code '%4'.  Ensure the share exists and is accessible.

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`ShareScopeName`	—
`Status`	—

Event ID 1054 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`ShareScopeName`	—
`Status`	—

Event ID 1055 — Health check for file share resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Health check for file share resource '%1' failed.  Retrieving information for share '%2' (scoped to network name %3) indicated that the share does not exist (error code '%4').  Please ensure the share exists and is accessible.

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`ShareScopeName`	—
`Status`	—

Event ID 1055 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`ShareScopeName`	—
`Status`	—

Event ID 1057 — The cluster database could not be loaded.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster database could not be loaded. The file may be missing or corrupt. Automatic repair might be attempted.

Event ID 1057 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 1061 — The Cluster service successfully formed the failover cluster '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service successfully formed the failover cluster '%1'.

Fields

Name	Description
`ClusterName`	—
`NodeName`	—

Event ID 1062 — This node has successfully joined the failover cluster '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

This node has successfully joined the failover cluster '%1'.

Fields

Name	Description
`ClusterName`	—
`NodeName`	—

Event ID 1063 — The Cluster service was successfully stopped.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service was successfully stopped.

Event ID 1066 — Cluster disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster disk resource '%1' indicates corruption for volume '%2'. Chkdsk is being run to repair problems. The disk will be unavailable until Chkdsk completes. Chkdsk output will be logged to file '%3'.
 Chkdsk may also write information to the Application Event Log.

Fields

Name	Description
`ResourceName`	—
`VolumeID`	—
`ChkdskLogFile`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1066 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`VolumeID`	—
`ChkdskLogFile`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1068 — Cluster file share resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster file share resource '%1' cannot be brought online.  Creation of file share '%2' (scoped to network name %3) failed due to error '%4'.  This operation will be automatically retried.

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`ShareScopeName`	—
`Status`	—

Event ID 1068 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`ShareScopeName`	—
`Status`	—

Event ID 1069 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster resource '%1' in clustered role '%2' failed.

Fields

Name	Description
`ResourceName`	—
`ResourceGroup`	—
`ResTypeDll`	—

Event ID 1069 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ResourceGroup`	—
`ResTypeDll`	—

Event ID 1070 — The node failed to join failover cluster '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The node failed to join failover cluster '%1' due to error code '%2'.

Fields

Name	Description
`ClusterName`	—
`Status`	—
`NodeName`	—

Event ID 1070 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ClusterName`	—
`Status`	—
`NodeName`	—

Event ID 1071 — The operation attempted on cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The operation attempted on cluster resource '%1' of type '%3' in clustered role '%2' could not be completed because the resource or one of its providers has locked status.

Fields

Name	Description
`ResourceName`	—
`ResourceGroup`	—
`ResTypeDll`	—

Event ID 1071 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ResourceGroup`	—
`ResTypeDll`	—

Event ID 1073 — The Cluster service was halted to prevent an inconsistency within the failover cluster.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service was halted to prevent an inconsistency within the failover cluster. The error code was '%1'.

Fields

Name	Description
`Status`	—
`NodeName`	—

Event ID 1073 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—
`NodeName`	—

Event ID 1077 — Health check for IP interface '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Health check for IP interface '%1' (address '%2') failed (status is '%3'). Run the Validate a Configuration wizard to ensure that the network adapter is functioning properly.

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`Status`	—

Event ID 1077 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`Status`	—

Event ID 1078 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' cannot be brought online because WINS registration failed on interface '%2' with error '%3'. Ensure that a valid, accessible WINS server has been specified.

Fields

Name	Description
`ResourceName`	—
`InterfaceName`	—
`Status`	—

Event ID 1078 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`InterfaceName`	—
`Status`	—

Event ID 1080 — The Cluster service failed to update the cluster database (error code '%1').

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service failed to update the cluster database (error code '%1'). Possible causes are insufficient disk space or file system corruption.

Fields

Name	Description
`Status`	—
`NodeName`	—

Event ID 1080 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—
`NodeName`	—

Event ID 1090 — The Cluster service cannot be started.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error '%1'. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data.

Fields

Name	Description
`Status`	—
`NodeName`	—

Event ID 1090 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—
`NodeName`	—

Event ID 1092 — Failed to form cluster '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Failed to form cluster '%1' with error code '%2'. Failover cluster will not be available.

Fields

Name	Description
`ClusterName`	—
`Status`	—
`NodeName`	—

Event ID 1092 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ClusterName`	—
`Status`	—
`NodeName`	—

Event ID 1093 — The Cluster service cannot identify node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service cannot identify node '%1' as a member of failover cluster '%2'. If the computer name for this node was recently changed, consider reverting to the previous name. Alternatively, add the node to the failover cluster and if necessary, reinstall clustered applications.

Fields

Name	Description
`NodeName`	—
`ClusterName`	—

Event ID 1093 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`ClusterName`	—

Event ID 1094 — The cluster common property SecurityLevel cannot be changed on this cluster.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster common property SecurityLevel cannot be changed on this cluster. The cluster security level cannot be changed because the cluster is currently configured for no authentication mode.

Event ID 1094 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 1105 — The Cluster service failed to start because it was unable to register interface(s) with the RPC service.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service failed to start because it was unable to register interface(s) with the RPC service.  The error code was '%1'.

Fields

Name	Description
`Status`	—
`NodeName`	—

Event ID 1105 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—
`NodeName`	—

Event ID 1116 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network name resource '%1' failed to renew its DNS registration. Ensure that the network adapters for dependent IP address resources have access to at least one DNS server. Alternatively, enable NetBIOS for dependent IP addresses. It is possible that the DNS server may be temporarily unavailable - the DNS registration attempt will be retried.

Fields

Name	Description
`ResourceName`	—

Event ID 1119 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to register DNS name '%2' over adapter '%4' for the following reason: 

'%3'

Fields

Name	Description
`ResourceName`	—
`Name`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1119 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Name`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1121 — Encrypted settings for cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Encrypted settings for cluster resource '%1' could not be successfully applied to the container name '%2' on this node.

Fields

Name	Description
`ResourceName`	—
`ContainerName`	—

Event ID 1121 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ContainerName`	—

Event ID 1125 — Cluster network interface '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network interface '%1' for cluster node '%2' on network '%3' is operational (up). The node can communicate with all other available failover cluster nodes on the network.

Fields

Name	Description
`InterfaceName`	—
`NodeName`	—
`NetworkName`	—

Event ID 1126 — Cluster network interface '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network interface '%1' for cluster node '%2' on network '%3' is unreachable by at least one other cluster node attached to the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Fields

Name	Description
`InterfaceName`	—
`NodeName`	—
`NetworkName`	—

Event ID 1126 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`InterfaceName`	—
`NodeName`	—
`NetworkName`	—

Event ID 1127 — Cluster network interface '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network interface '%1' for cluster node '%2' on network '%3' failed. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Fields

Name	Description
`InterfaceName`	—
`NodeName`	—
`NetworkName`	—

Event ID 1127 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`InterfaceName`	—
`NodeName`	—
`NetworkName`	—

Event ID 1128 — Cluster network '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network '%1' is operational (up). All available failover cluster nodes attached to the network can communicate using it.

Fields

Name	Description
`NetworkName`	—

Event ID 1129 — Cluster network '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network '%1' is partitioned. Some attached failover cluster nodes cannot communicate with each other over the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Fields

Name	Description
`NetworkName`	—

Event ID 1129 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NetworkName`	—

Event ID 1130 — Cluster network '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network '%1' is down. None of the available nodes can communicate using this network. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Fields

Name	Description
`NetworkName`	—

Event ID 1130 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NetworkName`	—

Event ID 1131 — Cluster network interface '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network interface '%1' was added for node '%2' on network '%3'.

Fields

Name	Description
`InterfaceName`	—
`NodeName`	—
`NetworkName`	—

Event ID 1132 — Cluster network interface '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network interface '%1' for node '%2' on network '%3' was removed.

Fields

Name	Description
`InterfaceName`	—
`NodeName`	—
`NetworkName`	—

Event ID 1133 — Cluster network '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network '%1' was added to the failover cluster.

Fields

Name	Description
`NetworkName`	—

Event ID 1134 — Cluster network '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network '%1' was removed from the failover cluster.

Fields

Name	Description
`NetworkName`	—

Event ID 1135 — Cluster node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster node '%1' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Fields

Name	Description
`NodeName`	—

Event ID 1135 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1136 — The cluster service has detected an Azure host maintenance event is about to occur.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service has detected an Azure host maintenance event is about to occur.  This maintenance event may cause the virtual machine hosting this node to become unavailable during this time. 

 Node: %1 
 Approximate Time: %2 
 Details: %3

Fields

Name	Description
`NodeName`	—
`MaintenanceTime`	—
`Metadata`	—

Event ID 1136 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`MaintenanceTime`	—
`Metadata`	—

Event ID 1137 — Move of cluster role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Move of cluster role '%1' for drain could not be completed.  The operation failed with error code %2.

Fields

Name	Description
`ResourceGroup`	—
`ApplicationErrorCode`	—

Event ID 1137 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceGroup`	—
`ApplicationErrorCode`	—

Event ID 1138 — Cluster file share resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster file share resource '%1' cannot be brought online. Creation of DFS namespace root failed with error '%3'. This may be due to failure to start the 'DFS Namespace' service or failure to create the DFS-N root for share '%2'.

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`Status`	—

Event ID 1138 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`Status`	—

Event ID 1139 — The cluster service has detected an Azure host maintenance event has been scheduled.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service has detected an Azure host maintenance event has been scheduled.  This maintenance event may cause the virtual machine hosting this node to become unavailable during this time. 

 Node: %1 
 Approximate Time: %2 
 Details: %3

Fields

Name	Description
`NodeName`	—
`MaintenanceTime`	—
`Metadata`	—

Event ID 1139 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`MaintenanceTime`	—
`Metadata`	—

Event ID 1140 — The cluster service has detected an Azure host maintenance event has been rescheduled.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service has detected an Azure host maintenance event has been rescheduled.  This maintenance event may cause the virtual machine hosting this node to become unavailable during this time. 

 Node: %1 
 Original Time: %2 
 New Time: %3

Fields

Name	Description
`NodeName`	—
`MaintenanceTime`	—
`Metadata`	—

Event ID 1140 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`MaintenanceTime`	—
`Metadata`	—

Event ID 1141 — Cluster file share resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster file share resource '%1' cannot be brought online. Resynchronization of DFS root target '%2' failed with error '%3'.

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`Status`	—

Event ID 1141 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`Status`	—

Event ID 1142 — Cluster file share resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster file share resource '%1' for DFS Namespace cannot be brought online due to error '%2'.

Fields

Name	Description
`ResourceName`	—
`Status`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1142 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1146 — The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.

Fields

Name	Description
`NodeName`	—

Event ID 1146 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1149 — The DNS Host (A) and Pointer (PTR) records associated with Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The DNS Host (A) and Pointer (PTR) records associated with Cluster resource '%1' were not removed from the resource's associated DNS server. If necessary, they can be deleted manually. Contact your DNS administrator to assist with this effort.

Fields

Name	Description
`ResourceName`	—

Event ID 1149 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 1150 — The removal of the DNS Pointer (PTR) record '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The removal of the DNS Pointer (PTR) record '%2' for host '%3' which is associated with the cluster network name resource '%1' failed with error '%4'. If necessary, the record can be deleted manually. Contact your DNS administrator for assistance.

Fields

Name	Description
`ResourceName`	—
`PTRRecord`	—
`HostName`	—
`Status`	—

Event ID 1150 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`PTRRecord`	—
`HostName`	—
`Status`	—

Event ID 1151 — The removal of the DNS Host (A) record '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The removal of the DNS Host (A) record '%2' associated with the cluster network name resource '%1' failed with error '%3'. If necessary, the record can be deleted manually. Contact your DNS administrator for assistance.

Fields

Name	Description
`ResourceName`	—
`ARecord`	—
`Status`	—

Event ID 1151 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ARecord`	—
`Status`	—

Event ID 1153 — The Cluster service is attempting to fail over the clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service is attempting to fail over the clustered role '%1' from node '%2' to node '%3'.

Fields

Name	Description
`ResourceGroup`	—
`FromNode`	—
`ToNode`	—

Event ID 1154 — The Cluster service is attempting to fail back the clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service is attempting to fail back the clustered role '%1' from node '%2' to node '%3'.

Fields

Name	Description
`ResourceGroup`	—
`FromNode`	—
`ToNode`	—

Event ID 1155 — The pending move for the role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The pending move for the role '%1' did not complete.

Fields

Name	Description
`ResourceGroup`	—
`ApplicationErrorCode`	—

Event ID 1155 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceGroup`	—
`ApplicationErrorCode`	—

Event ID 1156 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' was added to the failover cluster.

Fields

Name	Description
`ResourceName`	—

Event ID 1157 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' was removed from the failover cluster.

Fields

Name	Description
`ResourceName`	—

Event ID 1158 — Cluster role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster role '%1' was added to the failover cluster.

Fields

Name	Description
`ResourceGroup`	—

Event ID 1159 — Cluster role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster role '%1' was removed from the failover cluster.

Fields

Name	Description
`ResourceGroup`	—

Event ID 1177 — The Cluster service is shutting down because quorum was lost.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. 
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Fields

Name	Description
`NodeName`	—

Event ID 1177 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1181 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster resource '%1' cannot be brought online because the associated service failed to start. The service return code is '%2'. Please check for additional events associated with the service and ensure the service starts correctly.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1181 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1182 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster resource '%1' cannot be brought online because the associated service failed an attempted restart. The error code is '%2'. The service required a restart in order to update parameters. However, the service failed before it could be stopped and restarted. Please check for additional events associated with the service and ensure the service is functioning correctly.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1182 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1183 — Cluster disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster disk resource '%1' contains an invalid mount point. Both the source and target disks associated with the mount point must be clustered disks, and must be members of the same group. 
Mount point '%2' for volume '%3' references an invalid source disk. Please ensure that the source disk is also a clustered disk and in the same group as the target disk (hosting the mount point).

Fields

Name	Description
`ResourceName`	—
`MountPoint`	—
`VolumeID`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1183 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`MountPoint`	—
`VolumeID`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1186 — The password associated with the Cluster service domain account is being updated on this node.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The password associated with the Cluster service domain account is being updated on this node.

Event ID 1190 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network name resource '%1' successfully deleted its associated computer object in domain '%2'. The object was deleted due to failure of network name resource '%1' to come online.

Fields

Name	Description
`ResourceName`	—
`DomainName`	—

Event ID 1191 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to delete its associated computer object in domain '%2'. The error code was '%3'. 
Please have a domain administrator manually delete the computer object from the Active Directory domain.

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`Status`	—

Event ID 1191 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`Status`	—

Event ID 1192 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to delete its associated computer object in domain '%2' for the following reason:
%3. 

Please have a domain administrator manually delete the computer object from the Active Directory domain.

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`StatusString`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1192 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`StatusString`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1193 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to create its associated computer object in domain '%2' for the following reason: %3.

The associated error code is: %5

Please work with your domain administrator to ensure that:
- The cluster identity '%4' can create computer objects. By default all computer objects are created in the 'Computers' container; consult the domain administrator if this location has been changed.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity '%4' has 'Full Control' permission to that computer object using the Active Directory Users and Computers tool.

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`FailureString`	—
`ClusterIdentity`	—
`Status`	—

Event ID 1193 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`FailureString`	—
`ClusterIdentity`	—
`Status`	—

Event ID 1194 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to create its associated computer object in domain '%2' during: %3.

The text for the associated error code is: %4

Please work with your domain administrator to ensure that:
- The cluster identity '%5' has Create Computer Objects permissions. By default all computer objects are created in the same container as the cluster identity '%5'.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity '%5' has 'Full Control' permission to that computer object using the Active Directory Users and Computers tool.

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`FailureString`	—
`Status`	—
`ClusterIdentity`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1194 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`FailureString`	—
`Status`	—
`ClusterIdentity`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1195 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed registration of one or more associated DNS name(s). The error code was '%2'. Ensure that the network adapters associated with dependent IP address resources are configured with access to at least one DNS server.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1195 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1196 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed registration of one or more associated DNS name(s) for the following reason:
%2.

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.

Fields

Name	Description
`ResourceName`	—
`StatusString`	—

Event ID 1196 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`StatusString`	—

Event ID 1197 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to delete or disable its associated computer object '%2' during resource deletion. The error code was '%3'. 
Please check if the site is Read-Only. Ensure that the cluster name object has the appropriate permissions on the '%2' object in Active Directory.

Fields

Name	Description
`ResourceName`	—
`ObjectName`	—
`Status`	—

Event ID 1197 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ObjectName`	—
`Status`	—

Event ID 1198 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to delete computer object with guid '%2'. The error code was '%3'. 
Please check if the site is Read-Only. Ensure that the cluster name object has the appropriate permissions on the '%2' object in Active Directory.

Fields

Name	Description
`ResourceName`	—
`ObjectGuid`	—
`Status`	—

Event ID 1198 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ObjectGuid`	—
`Status`	—

Event ID 1200 — The Cluster service is attempting to bring the clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service is attempting to bring the clustered role '%1' online.

Fields

Name	Description
`ResourceGroup`	—

Event ID 1201 — The Cluster service successfully brought the clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service successfully brought the clustered role '%1' online.

Fields

Name	Description
`ResourceGroup`	—

Event ID 1203 — The Cluster service is attempting to bring the clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service is attempting to bring the clustered role '%1' offline.

Fields

Name	Description
`ResourceGroup`	—

Event ID 1204 — The Cluster service successfully brought the clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service successfully brought the clustered role '%1' offline.

Fields

Name	Description
`ResourceGroup`	—

Event ID 1205 — The Cluster service failed to bring clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service failed to bring clustered role '%1' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.

Fields

Name	Description
`ResourceGroup`	—

Event ID 1205 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceGroup`	—

Event ID 1206 — The computer object associated with the cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The computer object associated with the cluster network name resource '%1' could not be updated in domain '%2'. The error code was '%3'. The cluster identity '%4' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`FailureString`	—
`ClusterIdentity`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1206 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`FailureString`	—
`ClusterIdentity`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1207 — The computer object associated with the cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The computer object associated with the cluster network name resource '%1' could not be updated in domain '%2' during the 
%3 operation.

The text for the associated error code is: %4
 
The cluster identity '%5' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`FailureString`	—
`Status`	—
`ClusterIdentity`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1207 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`FailureString`	—
`Status`	—
`ClusterIdentity`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1208 — Cluster disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster disk resource '%1' contains an invalid mount point. Both the source and target disks associated with the mount point must be clustered disks, and must be members of the same group. 
Mount point '%2' for volume '%3' references an invalid target disk. Please ensure that the target disk is also a clustered disk and in the same group as the source disk (hosting the mount point).

Fields

Name	Description
`ResourceName`	—
`MountPoint`	—
`VolumeID`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1208 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`MountPoint`	—
`VolumeID`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1209 — Cluster service is requesting a bus reset for device '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster service is requesting a bus reset for device '%1'.

Fields

Name	Description
`Parameter1`	—

Event ID 1211 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' cannot be brought online. Attempt to locate a writeable domain controller (in domain %2) in order to create or update a computer object associated with the resource failed. The error code was '%3'. Ensure that a writeable domain controller is accessible to this node within the configured domain. Also ensure that the DNS server is running in order to resolve the name of the domain controller.

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`Status`	—

Event ID 1211 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`Status`	—

Event ID 1212 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' cannot be brought online. Attempt to locate a writeable domain controller (in domain %2) in order to create or update a computer object associated with the resource failed for the following reason:
%3.

 The error code was '%4'. Ensure that a writeable domain controller is accessible to this node within the configured domain. Also ensure that the DNS server is running in order to resolve the name of the domain controller.

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`FailureString`	—
`Status`	—

Event ID 1212 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainName`	—
`FailureString`	—
`Status`	—

Event ID 1213 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' could not completely rename the associated computer object on domain controller '%2'. Attempting to rename the computer object from new name '%3' back to its original name '%4' has also failed. The error code was '%5'. This may affect client connectivity until the network name and its associated computer object name are consistent. Contact your domain administrator to manually rename the computer object.

Fields

Name	Description
`ResourceName`	—
`DomainControllerName`	—
`NewName`	—
`OldName`	—
`Status`	—

Event ID 1213 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainControllerName`	—
`NewName`	—
`OldName`	—
`Status`	—

Event ID 1214 — Cluster Network Name resource cannot be registered with Netbios.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Network Name resource cannot be registered with Netbios. 

Network Name: '%3' 
Reason for failure: %2 
Resource name:'%1' 

 Run nbtstat for the network name to ensure that the name is not already registered with Netbios.

Fields

Name	Description
`ResourceName`	—
`FailureString`	—
`Name`	—

Event ID 1214 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`FailureString`	—
`Name`	—

Event ID 1215 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed a health check. Network name '%2' is no longer registered on this node.  The error code was '%3'. Check for hardware or software errors related to the network adapter. Also, you can run the Validate a Configuration wizard to check your network configuration.

Fields

Name	Description
`ResourceName`	—
`Name`	—
`Status`	—

Event ID 1215 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Name`	—
`Status`	—

Event ID 1216 — A name change operation on the cluster core netname resource has failed.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

A name change operation on the cluster core netname resource has failed. Attempting to revert the name change operation back to the original name has also failed. The error code was '%1'. You may not be able to remotely manage the cluster using the cluster name until this situation has been manually corrected.

Fields

Name	Description
`Status`	—

Event ID 1216 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 1217 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network name resource '%1' successfully changed the name property from '%2' to '%3'.

Fields

Name	Description
`ResourceName`	—
`OriginalName`	—
`Name`	—

Event ID 1218 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to perform a name change operation (attempting to change original name '%3' to name '%4').  The computer object could not be found on the domain controller '%2' (where it was created). An attempt will be made to recreate the computer object the next time the resource is brought online. Additionally, please work with your domain administrator to ensure that the computer object exists in the domain.

Fields

Name	Description
`ResourceName`	—
`DomainController`	—
`OriginalName`	—
`Name`	—

Event ID 1218 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainController`	—
`OriginalName`	—
`Name`	—

Event ID 1219 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to perform a name change operation.  The domain controller '%2' where computer object '%3' was being renamed, could not be contacted. The error code was '%4'. Ensure a writeable domain controller is accessible and check for any connectivity issue.

Fields

Name	Description
`ResourceName`	—
`ComputerAccount`	—
`DomainController`	—
`Status`	—

Event ID 1219 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ComputerAccount`	—
`DomainController`	—
`Status`	—

Event ID 1220 — The computer account for resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The computer account for resource '%1' failed to be renamed from %2 to %3 using Domain Controller %4. The associated error code is stored in the data section.
 
The computer account for this resource was in the process of being renamed and did not complete. This was detected during the online process for this resource. In order to recover, the computer account must be renamed to the current value of the Name property, i.e., the name presented on the network.
 
The Domain Controller where the renamed was attempted might not be available; if this is the case, wait for the Domain Controller to be available again. The Domain Controller could be denying access to the account; after resolving access, try to bring the name online again.
 
If this is not possible, disable and re-enable Kerberos Authentication and an attempt will be made to find the computer account on a different DC. You eed to change the Name property to %2 in order to use the existing CComputer account.

Fields

Name	Description
`ResourceName`	—
`OriginalName`	—
`Name`	—
`DomainController`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1220 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`OriginalName`	—
`Name`	—
`DomainController`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1221 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' has a name '%2' which does not match the corresponding computer object name '%3'.  It is likely that a previous name change of the computer object has not replicated to all domain controllers in the domain. You will be unable to rename the network name resource until the names become consistent. If the computer object has not been recently changed, please contact your domain administrator to rename the computer object and thereby make it consistent. Also, ensure that replication across domain controllers has been successfully completed.

Fields

Name	Description
`ResourceName`	—
`Name`	—
`ComputerAccount`	—

Event ID 1221 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Name`	—
`ComputerAccount`	—

Event ID 1222 — The computer object associated with cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The computer object associated with cluster network name resource '%1' could not be updated.

The text for the associated error code is: %2
 
The cluster identity '%3' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.

Fields

Name	Description
`ResourceName`	—
`FailureString`	—
`ClusterIdentity`	—

Event ID 1222 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`FailureString`	—
`ClusterIdentity`	—

Event ID 1223 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' cannot be brought online because the cluster network '%2' is not configured to allow client access. Please use the Failover Cluster Manager snap-in to check the configured properties of the cluster network.

Fields

Name	Description
`ResourceName`	—
`NetworkName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1223 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`NetworkName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1224 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster IP address resource '%1' has been moved to cluster network '%2' because its IP address and subnet mask match. To reverse this assignment, take resource '%1' offline, restore the '%1' Network property to its former value, set the '%1' OverrideAddressMatch property to 1, and bring resource '%1' back online.

Fields

Name	Description
`ResourceName`	—
`NetworkName`	—

Event ID 1226 — Network Name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Network Name resource '%1' (with associated network name '%2') has Kerberos Authentication support enabled. Failed to add required credentials to the LSA - the associated error code '%3' indicates insufficient privileges normally required for this operation. The required privilege is 'Trusted Computing Base' and must be locally enabled on each node comprising the cluster.

Fields

Name	Description
`ResourceName`	—
`NetBiosName`	—
`Status`	—

Event ID 1226 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`NetBiosName`	—
`Status`	—

Event ID 1227 — Network Name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Network Name resource '%1' (with associated network name '%2') has Kerberos Authentication support enabled. Failed to add required credentials to the LSA - the associated error code is '%3'.

Fields

Name	Description
`ResourceName`	—
`NetBiosName`	—
`Status`	—

Event ID 1227 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`NetBiosName`	—
`Status`	—

Event ID 1228 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' encountered an error enabling the network name on this node. The reason for the failure was: 
 '%2'.

 The error code was '%3'. 

 You may take the network name resource offline and online again to retry.

Fields

Name	Description
`ResourceName`	—
`Description`	—
`Status`	—

Event ID 1228 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Description`	—
`Status`	—

Event ID 1229 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' was unable to identify any IP addresses to register with a DNS server. Ensure that there is one or more networks that are enabled for cluster use with the 'Allow clients to connect through this network' setting, and that each node has a valid IP address configured for the networks.

Fields

Name	Description
`ResourceName`	—

Event ID 1229 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 1230 — A component on the server did not respond in a timely fashion.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

A component on the server did not respond in a timely fashion. This caused the cluster resource '%1' (resource type '%2', DLL '%3') to exceed its time-out threshold. As part of cluster health detection, recovery actions will be taken. The cluster will try to automatically recover by terminating and restarting the Resource Hosting Subsystem (RHS) process that is running this resource. Verify that the underlying infrastructure (such as storage, networking, or services) that are associated with the resource are functioning correctly.

Fields

Name	Description
`ResourceName`	—
`ResourceType`	—
`ResTypeDll`	—
`ResourceControl`	—

Event ID 1230 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ResourceType`	—
`ResTypeDll`	—
`ResourceControl`	—

Event ID 1231 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' encountered an error logging on to the domain. The reason for the failure was: 
 '%2'.

 The error code was '%3'. 

 Ensure that a domain controller is accessible to this node within the configured domain.

Fields

Name	Description
`ResourceName`	—
`Description`	—
`Status`	—

Event ID 1231 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Description`	—
`Status`	—

Event ID 1232 — Entry point '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Entry point '%2' in cluster generic script resource '%1' did not complete execution in a timely manner. This could be due to an infinite loop or other issues possibly resulting in an infinite wait. Alternatively, the specified pending timeout value may be too short for this resource. Please review the '%2' script entry point to ensure all possible infinite waits in the script code have been corrected. Then, consider increasing the pending timeout value if deemed necessary.

Fields

Name	Description
`ResourceName`	—
`Parameter2`	—

Event ID 1232 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Parameter2`	—

Event ID 1233 — Cluster generic script resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster generic script resource '%1': request to perform the '%2' operation will not be processed. This is due to a previously failed attempt to execute the '%3' entry point in a timely fashion. Please review the script code for this entry point to ensure there does not exist any infinite loop or other issues possibly resulting in an infinite wait. Then, consider increasing the resource pending timeout value if deemed necessary.

Fields

Name	Description
`ResourceName`	—
`Parameter2`	—
`Parameter3`	—

Event ID 1233 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Parameter2`	—
`Parameter3`	—

Event ID 1234 — The Cluster service has detected that its service account is missing one or more of the required privileges.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service has detected that its service account is missing one or more of the required privileges. The missing privilege list is: '%1' and is not currently granted to the service account. Use the 'sc.exe qprivs clussvc' to verify the privileges of the Cluster service (ClusSvc). Additionally check for any security policies or group policies in Active Directory Domain Services that may have altered the default privileges. Type the following command to grant the Cluster service the necessary privileges to function correctly: 

sc.exe privs clussvc SeBackupPrivilege/SeRestorePrivilege/SeIncreaseQuotaPrivilege/SeIncreaseBasePriorityPrivilege/SeTcbPrivilege/SeDebugPrivilege/SeSecurityPrivilege/SeAuditPrivilege/SeImpersonatePrivilege/SeChangeNotifyPrivilege/SeIncreaseWorkingSetPrivilege/SeManageVolumePrivilege/SeCreateSymbolicLinkPrivilege/SeLoadDriverPrivilege

Fields

Name	Description
`MissingPrivilegeList`	—
`NodeName`	—

Event ID 1234 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`MissingPrivilegeList`	—
`NodeName`	—

Event ID 1237 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' entered maintenance mode. The associated status is '%2'.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1238 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' exited maintenance mode. The associated status is '%2'.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1239 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster IP address resource '%1' obtained a leased IP address '%2'.

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1240 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' failed to obtain a leased IP address.

Fields

Name	Description
`ResourceName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1240 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1241 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster IP address resource '%1' released lease of IP address '%2'.

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1242 — Lease of IP address '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Lease of IP address '%2' associated with cluster IP address resource '%1' has expired or is about to expire, and currently cannot be renewed. Ensure that the associated DHCP server is accessible and properly configured to renew the lease on this IP address.

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1242 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1243 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' failed to release the lease for IP address '%2'.

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1243 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1244 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster IP address resource '%1' renewed the lease for IP address '%2'.

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—

Event ID 1245 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' failed to renew the lease for IP address '%2'. Ensure that the DHCP server is accessible and properly configured to renew the lease on this IP address.

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1245 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1246 — Settings have changed for cluster network '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Settings have changed for cluster network '%2' which affect cluster IP address resource '%1'. Attempting to renew lease for the IP address resource.

Fields

Name	Description
`ResourceName`	—
`NetworkName`	—

Event ID 1247 — The Security Identifier (SID) type for the cluster service is configured as '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Security Identifier (SID) type for the cluster service is configured as '%1' but the expected SID type is 'Unrestricted'. The cluster service is automatically modifying its SID type configuration with the Service Control Manager (SCM) and will restart in order for this change to take effect.

Fields

Name	Description
`ServiceSIDType`	—
`NodeName`	—

Event ID 1247 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ServiceSIDType`	—
`NodeName`	—

Event ID 1248 — The Security Identifier (SID) '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Security Identifier (SID) '%1' associated with the cluster service is not present in the process token. The cluster service will automatically correct this problem and restart.

Fields

Name	Description
`ServiceSID`	—
`NodeName`	—

Event ID 1248 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ServiceSID`	—
`NodeName`	—

Event ID 1249 — Cluster IPv6 tunnel address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster IPv6 tunnel address resource '%1' has been updated to match the tunnel type supported by the cluster node. The tunnel type has changed from '%2' to '%3' and the address has been set to '%4'. If this change is unexpected, please check the IP address resource on which the IPv6 tunnel address resource '%1' depends, as well as the IPv6 configuration of your network and all cluster nodes.

Fields

Name	Description
`ResourceName`	—
`Parameter2`	—
`Parameter3`	—
`Parameter4`	—

Event ID 1250 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster resource '%1' in clustered role  '%2' has received a critical state notification.  For a virtual machine this indicates that an application or service inside the virtual machine is in an unhealthy state. Verify the functionality of the service or application being monitored within the virtual machine.

Fields

Name	Description
`ResourceName`	—
`ResourceGroup`	—

Event ID 1250 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ResourceGroup`	—

Event ID 1251 — Clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Clustered role '%2' was taken offline. This role was preempted by the higher priority clustered role '%1'. The cluster service will attempt to bring clustered role '%2' online later when system resources are available.

Fields

Name	Description
`Preemptor`	—
`Preemptee`	—

Event ID 1251 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Preemptor`	—
`Preemptee`	—

Event ID 1252 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' in clustered role '%2' rejected a move request to node '%3'. The error code was '%4'.  Cluster resource '%1' may be busy or in a state where it cannot be moved.  The cluster service may automatically retry the move.

Fields

Name	Description
`ResourceName`	—
`GroupName`	—
`NodeName`	—
`ApplicationErrorCode`	—

Event ID 1253 — Resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Resource '%1' of the clustered role '%2' vetoed the untargeted move with application specific error code '%3'.

Fields

Name	Description
`ResourceName`	—
`GroupName`	—
`ApplicationErrorCode`	—

Event ID 1254 — Clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Clustered role '%1' has exceeded its failover threshold.  It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state.  No additional attempts will be made to bring the role online or fail it over to another node in the cluster.  Please check the events associated with the failure.  After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

Fields

Name	Description
`ResourceGroup`	—

Event ID 1254 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceGroup`	—

Event ID 1255 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster resource '%1' in clustered role  '%2' has received a critical state notification.  For a virtual machine this indicates that a critical network of the virtual machine is in an unhealthy state. Verify the network connectivity of the virtual machine and the virtual networks that the virtual machine is configured to use.

Fields

Name	Description
`ResourceName`	—
`ResourceGroup`	—

Event ID 1255 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ResourceGroup`	—

Event ID 1256 — Cluster network name resource failed registration of one or more associated DNS names(s) because the corresponding DNS Zone does not accept dynamic...

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource failed registration of one or more associated DNS names(s) because the corresponding DNS Zone does not accept dynamic updates.

Cluster Network name: '%1'
DNS Zone: '%2'

Guidance:
Ensure that the DNS is configured as a Dynamic DNS zone. If the DNS server does not accept dynamic updates uncheck the   'Register this connection's' addresses in DNS' in the properties of the network adapter.

Fields

Name	Description
`ResourceName`	—
`DNSZone`	—

Event ID 1256 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DNSZone`	—

Event ID 1257 — Cluster network name resource failed registration of one or more associated DNS names(s) because the access to update the secure DNS Zone was denied.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource failed registration of one or more associated DNS names(s) because the access to update the secure DNS Zone was denied.

Cluster Network name: '%1'
DNS Zone: '%2'

Ensure that cluster name object (CNO) is granted permissions to the Secure DNS Zone.

Fields

Name	Description
`ResourceName`	—
`DNSZone`	—

Event ID 1257 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DNSZone`	—

Event ID 1258 — Cluster network name resource failed registration of one or more associated DNS name(s) because the a DNS server could not be reached.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource failed registration of one or more associated DNS name(s) because the a DNS server could not be reached.

Cluster Network name: '%1'
DNS Zone: '%2'
DNS Server: '%3'

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.

Fields

Name	Description
`ResourceName`	—
`DNSZone`	—
`DNSServers`	—

Event ID 1258 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DNSZone`	—
`DNSServers`	—

Event ID 1259 — Cluster network name resource failed registration of one or more associated DNS name(s) because the cluster service failed clean up the existing re...

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource failed registration of one or more associated DNS name(s) because the cluster service failed clean up the existing records corresponding to the network name.

Cluster Network name: '%1'
DNS Zone: '%2'

Ensure that cluster name object (CNO) is granted permissions to the Secure DNS Zone.

Fields

Name	Description
`ResourceName`	—
`DNSZone`	—

Event ID 1259 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DNSZone`	—

Event ID 1260 — Cluster network name resource failed to modify the DNS registration.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource failed to modify the DNS registration.

Cluster Network name: '%1'
Error code: '%2'

Guidance:
Ensure that the network adapters associated with dependent IP address resources are configured with access to at least one DNS server.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1260 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1261 — Cluster network name resource failed to modify the DNS registration.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource failed to modify the DNS registration.

Cluster Network name: '%1'
Reason: '%2'

Guidance:
Ensure that the network adapters associated with dependent IP address resources are configured with access to at least one DNS server.

Fields

Name	Description
`ResourceName`	—
`StatusString`	—

Event ID 1261 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`StatusString`	—

Event ID 1263 — Cluster network name resource failed to publish the PTR record in the DNS reverse lookup zone.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource failed to publish the PTR record in the DNS reverse lookup zone.

Cluster Network name: '%1'
Error Code: '%2'

Guidance:

Ensure that the network adapters associated with dependent IP address resources are configured with access to at least one DNS server and that the DNS reverse lookup zone exists.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1263 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1264 — Cluster network name resource failed to publish the PTR record in the DNS reverse lookup zone.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource failed to publish the PTR record in the DNS reverse lookup zone.

Cluster Network name: '%1'
Reason: '%2'

Guidance:

Ensure that the network adapters associated with dependent IP address resources are configured with access to at least one DNS server and that the DNS reverse lookup zone exists.

Fields

Name	Description
`ResourceName`	—
`StatusString`	—

Event ID 1264 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`StatusString`	—

Event ID 1265 — Cluster resource type '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster resource type '%1' timed out while processing the control code %2. The cluster will try to automatically recover by terminating and restarting the Resource Hosting Subsystem (RHS) process that was processing the call.

Fields

Name	Description
`ResourceTypeName`	—
`ControlCode`	—

Event ID 1265 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceTypeName`	—
`ControlCode`	—

Event ID 1280 — Sponsor tried to Create Security Context using Package='.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Sponsor tried to Create Security Context using Package='%1' with Context Requirement ='%2' and Timeout ='%3'

Fields

Name	Description
`PackageName`	—
`ContextRequirement`	—
`Timeout`	—

Event ID 1281 — Joiner tried to Create Security Context using Package='.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Joiner tried to Create Security Context using Package='%1' with Context Requirement ='%2' and Timeout ='%3' for the target = '%4'

Fields

Name	Description
`PackageName`	—
`ContextRequirement`	—
`Timeout`	—
`Target`	—

Event ID 1282 — Security Handshake between local and remote endpoints '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Security Handshake between local and remote endpoints '%2' did not complete in '%1' seconds, node terminating the connection

Fields

Name	Description
`Timeout`	—
`ConnectionInfo`	—

Event ID 1282 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Timeout`	—
`ConnectionInfo`	—

Event ID 1289 — The Cluster Service was unable to access network adapter '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster Service was unable to access network adapter '%1'. Verify that other network adapters are functioning properly and check the device manager for errors associated with adapter '%1'. If the configuration for adapter '%1' has been changed, it may become necessary to reinstall the failover clustering feature on this computer.

Fields

Name	Description
`NetftDisplayName`	—
`NodeName`	—

Event ID 1289 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NetftDisplayName`	—
`NodeName`	—

Event ID 1360 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' failed to come online. Ensure the network property '%2' matches a cluster network name or the address property '%3' matches one of the subnets on a cluster network. If this is an IPv6 Address type, please verify that the cluster network matching this resource has at least one IPv6 prefix that is not link-local or tunnel.

Fields

Name	Description
`ResourceName`	—
`NetworkProperty`	—
`AddressProperty`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1360 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`NetworkProperty`	—
`AddressProperty`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1361 — IPv6 Tunnel address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

IPv6 Tunnel address resource '%1' failed to come online because it does not depend on an IP Address (IPv4) resource. Dependency on at least one IP Address (IPv4) resource is required.

Fields

Name	Description
`ResourceName`	—

Event ID 1361 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 1362 — Cluster IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster IP address resource '%1' failed to come online because the '%2' property could not be read. Please ensure that the resource is correctly configured.

Fields

Name	Description
`ResourceName`	—
`NetworkProperty`	—

Event ID 1362 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`NetworkProperty`	—

Event ID 1363 — IPv6 tunnel address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

IPv6 tunnel address resource '%1' failed to come online. Cluster network '%2' associated with dependent IP address (IPv4) resource '%3' does not support ISATAP tunneling. Please ensure that the cluster network supports ISATAP tunneling.

Fields

Name	Description
`ResourceName`	—
`NetworkName`	—
`DependantName`	—

Event ID 1363 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`NetworkName`	—
`DependantName`	—

Event ID 1537 — A backup operation of the cluster configuration data has been initiated.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

A backup operation of the cluster configuration data has been initiated.

Fields

Name	Description
`NodeName`	—

Event ID 1538 — The backup operation for the cluster configuration data completed successfully.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The backup operation for the cluster configuration data completed successfully. The snapshot ID is '%1'.

Fields

Name	Description
`SnapShotID`	—
`NodeName`	—

Event ID 1539 — A restore operation of the cluster configuration data has been initiated.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

A restore operation of the cluster configuration data has been initiated.

Fields

Name	Description
`NodeName`	—

Event ID 1540 — The restore operation for the cluster configuration data completed successfully.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The restore operation for the cluster configuration data completed successfully.

Fields

Name	Description
`NodeName`	—

Event ID 1541 — The backup operation for the cluster configuration data has been aborted because quorum for the cluster has not yet been achieved.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The backup operation for the cluster configuration data has been aborted because quorum for the cluster has not yet been achieved. Please retry this backup operation after the cluster achieves quorum.

Fields

Name	Description
`NodeName`	—

Event ID 1541 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1542 — The restore request for the cluster configuration data has failed.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The restore request for the cluster configuration data has failed. This restore failed during the 'pre-restore' stage usually indicating that some nodes comprising the cluster are not currently operational. Ensure that the cluster service is running successfully on all nodes comprising this cluster.

Fields

Name	Description
`NodeName`	—

Event ID 1542 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1543 — The restore operation of the cluster configuration data has failed.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The restore operation of the cluster configuration data has failed. This restore failed during the 'post-restore' stage usually indicating that some nodes comprising the cluster are not currently operational. It is recommended that you replace the current cluster configuration data file (ClusDB) with '%1'.

Fields

Name	Description
`SafeCopy`	—
`NodeName`	—

Event ID 1543 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`SafeCopy`	—
`NodeName`	—

Event ID 1544 — The backup operation for the cluster configuration data has been canceled.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The backup operation for the cluster configuration data has been canceled. The cluster Volume Shadow Copy Service (VSS) writer received an abort request.

Fields

Name	Description
`NodeName`	—

Event ID 1544 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1545 — The restore operation for the cluster configuration data has failed.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The restore operation for the cluster configuration data has failed. This was due to insufficient privileges associated with the user account performing the restore. Please ensure that the user account has local administrator privileges.

Fields

Name	Description
`NodeName`	—

Event ID 1545 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1546 — Node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Node '%1' failed to form a failover cluster. This was due to one or more nodes executing incompatible versions of the cluster service software. If node '%1' or a different node in the cluster has been recently upgraded, please re-verify that all nodes are executing compatible versions of the cluster service software.

Fields

Name	Description
`NodeName`	—

Event ID 1546 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1547 — Node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Node '%1' attempted to join a failover cluster but failed due to incompatibility between versions of the cluster service software. If node '%1' or a different node in the cluster has been recently upgraded, please verify that the changed cluster deployment with different versions of the cluster service software is supported.

Fields

Name	Description
`NodeName`	—

Event ID 1547 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1548 — Node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Node '%1' established communication with node '%2' and detected that it is running a different, but compatible, version of the operating system. We recommend that all nodes run the same version of the operating system. After all nodes have been upgraded, run the Update-ClusterFunctionalLevel Windows PowerShell cmdlet to complete upgrading the cluster.

Fields

Name	Description
`LocalNodeName`	—
`RemoteNodeName`	—

Event ID 1548 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LocalNodeName`	—
`RemoteNodeName`	—

Event ID 1549 — Node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node '%1' successfully became part of a failover cluster and detected that its cluster service software has been updated.

Fields

Name	Description
`NodeName`	—

Event ID 1550 — Node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Node '%1' established a communication session with node '%2' without performing a version compatibility check because version compatibility checking is disabled. Disabling version compatibility checking is not supported.

Fields

Name	Description
`LocalNodeName`	—
`RemoteNodeName`	—

Event ID 1550 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LocalNodeName`	—
`RemoteNodeName`	—

Event ID 1551 — Node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Node '%1' formed a failover cluster without performing a version compatibility check because version compatibility checking is disabled. Disabling version compatibility checking is not supported.

Fields

Name	Description
`NodeName`	—

Event ID 1551 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1552 — The cluster service detected that the witness disk designation has changed - usually indicating that the current node has stale cluster configurati...

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The cluster service detected that the witness disk designation has changed - usually indicating that the current node has stale cluster configuration data. This condition will be automatically reconciled when the current node connects to other nodes that have the latest configuration data. Please ensure that all cluster nodes are running.

Fields

Name	Description
`NodeName`	—

Event ID 1553 — This cluster node has no network connectivity.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

This cluster node has no network connectivity. It cannot participate in the cluster until connectivity is restored.  Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Fields

Name	Description
`ArbitrationDelay`	—
`NodeName`	—

Event ID 1553 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ArbitrationDelay`	—
`NodeName`	—

Event ID 1554 — This cluster node has lost all network connectivity.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

This cluster node has lost all network connectivity. It cannot participate in the cluster until connectivity is restored. The cluster service on this node will be terminated.

Fields

Name	Description
`NodeName`	—

Event ID 1554 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1555 — Attempting to use IPv4 for '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Attempting to use IPv4 for '%1' network adapter failed. This was due to a failure to disable IPv4 auto-configuration and DHCP. This may be expected if the DHCP Client service is already disabled.  IPv6 will be used if enabled, otherwise this node may not be able to participate in a failover cluster.

Fields

Name	Description
`NetftDisplayName`	—
`NodeName`	—

Event ID 1555 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NetftDisplayName`	—
`NodeName`	—

Event ID 1556 — The cluster service encountered an unexpected problem and will be shut down.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service encountered an unexpected problem and will be shut down. The error code was '%2'.

Fields

Name	Description
`NodeName`	—
`Status`	—

Event ID 1556 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`Status`	—

Event ID 1557 — Cluster service failed to update the cluster configuration data on the witness resource.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to update the cluster configuration data on the witness resource. Please ensure that the witness resource is online and accessible.

Fields

Name	Description
`NodeName`	—

Event ID 1557 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1558 — The cluster service detected a problem with the witness resource.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.

Fields

Name	Description
`NodeName`	—

Event ID 1558 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1559 — File share '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

File share '%1' associated with the file share witness resource is currently hosted by server '%2'. This server '%2' has just been added as a new node within the failover cluster. Hosting of the file share witness by any node comprising the same cluster is not recommended. Please choose a file share witness that is not hosted by any node within the same cluster and modify settings of the file share witness resource accordingly.

Fields

Name	Description
`ShareName`	—
`NodeName`	—

Event ID 1559 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ShareName`	—
`NodeName`	—

Event ID 1560 — Cluster file share resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster file share resource '%1' has detected shared folder conflicts. As a result, some of these shared folders may not be accessible. To rectify this situation, ensure multiple shared folders do not have the same share name.

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`ShareScopeName`	—
`Status`	—

Event ID 1560 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`ShareScopeName`	—
`Status`	—

Event ID 1561 — Cluster service failed to start because this node detected that it does not have the latest copy of cluster configuration data.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to start because this node detected that it does not have the latest copy of cluster configuration data. Changes to the cluster occurred while this node was not in membership and as a result was not able to receive configuration data updates.

Guidance:
Attempt to start the cluster service on all nodes in the cluster so that nodes with the latest copy of the cluster configuration data can first form the cluster. This node will then be able join the cluster and will automatically obtain the updated cluster configuration data. If there are no nodes available with the latest copy of the cluster configuration data, run the 'Start-ClusterNode -FQ' Windows PowerShell cmdlet. Using the ForceQuorum (FQ) parameter will start the cluster service and mark this node's copy of the cluster configuration data to be authoritative.  Forcing quorum on a node with an outdated copy of the cluster database may result in cluster configuration changes that occurred while the node was not participating in the cluster to be lost.

Fields

Name	Description
`NodeName`	—

Event ID 1561 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1562 — File share witness resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

File share witness resource '%1' failed a periodic health check on file share '%2'. Please ensure that file share '%2' exists and is accessible by the cluster.

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1562 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1563 — File share witness resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

File share witness resource '%1' failed to come online. Please ensure that file share '%2' exists and is accessible by the cluster.

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1563 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1564 — File share witness resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

File share witness resource '%1' failed to arbitrate for the file share '%2'. Please ensure that file share '%2' exists and is accessible by the cluster.

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1564 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1565 — This cluster node is running with a different message security level ('%1') than remote node '%3' ('%2').

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

This cluster node is running with a different message security level ('%1') than remote node '%3' ('%2'). These two nodes will attempt to negotiate a mutually compatible message security level for this connection. Please ensure that the '%4' cluster property is configured correctly and that the cluster service has been restarted on all nodes since it was last changed.

Fields

Name	Description
`LocalSecurityLevel`	—
`RemoteSecurityLevel`	—
`NodeName`	—
`PropertyName`	—

Event ID 1566 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' cannot be brought online.  The network name resource was terminated by the resource host subsystem because it did not complete an operation in an acceptable time.  The operation timed out while performing:
 '%2'

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1566 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1567 — Cluster service failed to change the trace log size.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to change the trace log size. Please verify the ClusterLogSize setting with the 'Get-Cluster | Format-List *' PowerShell cmdlet. Also, use the Performance Monitor snapin to verify the event trace session settings for FailoverClustering.

Fields

Name	Description
`NodeName`	—

Event ID 1567 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1568 — Cluster disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster disk resource '%1' found the disk identifier to be stale. This may be expected if a restore operation was just performed or if this cluster uses replicated storage. The DiskSignature or DiskUniqueIds property for the disk resource has been corrected.

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1568 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1569 — Network '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Network '%1' which has been disabled for failover cluster use, was found to be the only currently possible network that node '%2' can use to communicate with other nodes in the cluster. This may impact the node's ability to participate in the cluster. Please verify network connectivity of node '%2' and enable at least one network for cluster communication. Run the Validate a Configuration wizard to check your network configuration.

Fields

Name	Description
`NetworkName`	—
`NodeName`	—

Event ID 1569 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NetworkName`	—
`NodeName`	—

Event ID 1570 — Node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Node '%1' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.

Fields

Name	Description
`NodeName`	—

Event ID 1570 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1571 — Node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Node '%1' failed to establish a communication session while joining the cluster. This was due to an authorization failure. Please verify that the nodes are running compatible versions of the cluster service software.

Fields

Name	Description
`NodeName`	—

Event ID 1571 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1572 — Node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Node '%1' failed to join the cluster because it could not send and receive failure detection network messages with other cluster nodes. Please run the Validate a Configuration wizard to ensure network settings. Also verify the Windows Firewall 'Failover Clusters' rules.

Fields

Name	Description
`NodeName`	—

Event ID 1572 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1573 — Node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Node '%1' failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource is online and available.

Fields

Name	Description
`NodeName`	—

Event ID 1573 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1574 — The failover cluster database could not be unloaded.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The failover cluster database could not be unloaded. If restarting the cluster service does not fix the problem, please restart the machine.

Fields

Name	Description
`NodeName`	—

Event ID 1574 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1575 — An attempt to forcibly start the cluster service has failed because the cluster configuration data on this node is either missing or corrupt.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

An attempt to forcibly start the cluster service has failed because the cluster configuration data on this node is either missing or corrupt. Please first start the cluster service on another node that has an intact and valid copy of the cluster configuration data. Then, reattempt the start operation on this node (which will attempt to obtain updated valid configuration information automatically). If no other node is available, please use WBAdmin.msc to perform a System State Restore of this node in order to restore the configuration data.

Fields

Name	Description
`NodeName`	—

Event ID 1575 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1576 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to register the name '%2' over adapter '%4' in a secure DNS zone. This was due to an existing record with this name and the cluster identity does not have the sufficient privileges to update that record. The error code was '%3'. Please contact your DNS server administrator to verify the cluster identity has permissions on DNS record '%2'.

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1576 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1577 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to register the name '%2' over adapter '%4'. The DNS server could not be contacted. The error code was '%3.' Ensure that a DNS server is accessible from this cluster node. The DNS registration will be retried later.

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1577 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1578 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to register dynamic updates for name '%2' over adapter '%4'. The DNS server may not be configured to accept dynamic updates. The error code was '%3'. Please contact your DNS server administrator to verify that the DNS server is available and configured for dynamic updates.

Alternatively, you can disable dynamic DNS updates by unchecking the 'Register this connection's addresses in DNS' setting in the advanced TCP/IP settings for adapter '%4' under the DNS tab.

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1578 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1579 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to update the DNS record for name '%2' over adapter '%4'. The error code was '%3'. Ensure that a DNS server is accessible from this cluster node and contact your DNS server administrator to verify the cluster identity can update the DNS record '%2'.

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1579 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1580 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' failed to register the name '%2' over adapter '%4' in a secure DNS zone. This was due to an existing record with this name and the cluster identity does not have the sufficient privileges to update that record. The error code was '%3'. Please contact your DNS server administrator to verify the cluster identity has permissions on DNS record '%2'.

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1580 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`Status`	—
`AdapterName`	—
`BinaryParameterLength`	—
`BinaryData`	—

Event ID 1581 — The restore request for the cluster configuration data failed to make a copy of the existing cluster configuration data file (ClusDB).

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The restore request for the cluster configuration data failed to make a copy of the existing cluster configuration data file (ClusDB). While attempting to preserve the existing configuration, the restore operation was unable to create a copy at location '%1'. This might be expected if the existing configuration data file was corrupt. The restore operation has continued but attempts to revert to the existing cluster configuration may not be possible.

Fields

Name	Description
`OriginalFileName`	—
`NewFileName`	—

Event ID 1581 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`OriginalFileName`	—
`NewFileName`	—

Event ID 1582 — Cluster Service failed to move the restored cluster hive at '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Service failed to move the restored cluster hive at '%1' to '%2'.  This may prevent the restore operation from succeeding successfully.  If the cluster configuration was not properly restored, please retry the restore action.

Fields

Name	Description
`OriginalFileName`	—
`NewFileName`	—

Event ID 1582 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`OriginalFileName`	—
`NewFileName`	—

Event ID 1583 — Cluster service failed to disable Internet Protocol security (IPsec) on the Failover cluster virtual adapter '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to disable Internet Protocol security (IPsec) on the Failover cluster virtual adapter '%1'. This could have a negative impact on cluster communication performance. If this problem persists, please verify your local and domain connection security policies applying to IPSec and the Windows Firewall. Additionally, please check for events related to the Base Filtering Engine service.

Fields

Name	Description
`NetftDisplayName`	—
`NodeName`	—

Event ID 1583 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NetftDisplayName`	—
`NodeName`	—

Event ID 1584 — A backup application initiated a VSS snapshot on Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

A backup application initiated a VSS snapshot on Cluster Shared Volume '%1' ('%3') without properly preparing the volume for snapshot. This snapshot may be invalid and the backup may not be usable for restore operations. Please contact your backup application vendor to verify compatibility with Cluster Shared Volumes.

Fields

Name	Description
`VolumeName`	—
`VolumeGuidName`	—
`ResourceName`	—

Event ID 1584 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeName`	—
`VolumeGuidName`	—
`ResourceName`	—

Event ID 1585 — Cluster file server resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster file server resource '%1' failed a health check. This was due to the Server service not being started. Please use Server Manager to confirm the state of the Server service on this cluster node.

Fields

Name	Description
`ResourceName`	—

Event ID 1585 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 1586 — Cluster file server resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster file server resource '%1' failed a health check. This was because some of its shared folders were inaccessible. Verify that the folders are accessible from clients. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other events related to the Server service on this cluster node. It may be necessary to restart the network name resource '%2' in this clustered role.

Fields

Name	Description
`ResourceName`	—
`NetworkNameResourceName`	—
`NumberOfSharesChecked`	—

Event ID 1586 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`NetworkNameResourceName`	—
`NumberOfSharesChecked`	—

Event ID 1587 — Cluster file server resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster file server resource '%1' failed a health check. This was because some of its shared folders were inaccessible. Verify that the folders are accessible from clients. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other events related to the Server service on this cluster node.

Fields

Name	Description
`ResourceName`	—
`NumberOfSharesChecked`	—
`LastShareError`	—

Event ID 1587 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`NumberOfSharesChecked`	—
`LastShareError`	—

Event ID 1588 — Cluster file server resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster file server resource '%1' cannot be brought online. The resource failed to create file share '%2' associated with network name '%3'. The error code was '%4'. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource '%3' in this clustered role.

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`ShareScopeName`	—
`Status`	—

Event ID 1588 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ShareName`	—
`ShareScopeName`	—
`Status`	—

Event ID 1589 — Cluster network name resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource '%1' found one or more IP addresses associated with DNS name '%2' that are not dependent IP address resources. The additional addresses found were '%3'. This may affect client connectivity until the network name and its associated DNS records are consistent. Please contact your DNS server administrator to verify the records associated with name '%2'.

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`IPAddress`	—

Event ID 1589 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DnsName`	—
`IPAddress`	—

Event ID 1592 — Cluster node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster node '%1' lost communication with cluster node '%2'.  Network communication was reestablished. This could be due to communication temporarily being blocked by a firewall or connection security policy update. If the problem persists and network communication are not reestablished, the cluster service on one or more nodes will stop.  If that happens, run the Validate a Configuration wizard to check your network configuration. Additionally, check for hardware or software errors related to the network adapters on this node, and check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Fields

Name	Description
`LocalNodeName`	—
`RemoteNodeName`	—

Event ID 1592 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LocalNodeName`	—
`RemoteNodeName`	—

Event ID 1593 — The failover cluster database could not be unloaded and any potentially incorrect changes in memory could not be discarded.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The failover cluster database could not be unloaded and any potentially incorrect changes in memory could not be discarded.  The cluster service will attempt to repair the database by retrieving it from another cluster node.  If the cluster service does not come online, restart the cluster service on this node.  If restarting the cluster service does not fix the problem, please restart the machine.  If the cluster service fails to come online after a reboot, please restore the cluster database from the last backup.  The current database was copied to '%1'.  If no backups are available, please copy '%1' to '%2' and attempt to start the cluster service.  If the cluster service then comes online on this node, some cluster configuration changes may be lost and the cluster may not function properly.  Run the Validate a Configuration wizard to check your cluster configuration and verify that the hosted Services and Applications are online and functioning correctly.

Fields

Name	Description
`BadDatabaseFilePath`	—
`DatabaseFilePath`	—

Event ID 1593 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`BadDatabaseFilePath`	—
`DatabaseFilePath`	—

Event ID 1594 — Cluster service successfully upgraded the cluster functional level.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service successfully upgraded the cluster functional level.  \n\n Functional Level: %1 \n Upgrade Version: %2

Fields

Name	Description
`FunctionalLevel`	—
`UpgradeLevel`	—

Event ID 1594 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`FunctionalLevel`	—
`UpgradeLevel`	—

Event ID 1600 — Cluster service failed to set the permissions on the cluster computer object '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to set the permissions on the cluster computer object '%1'. Please contact your network administrator to check the cluster security descriptor of the computer object in Active Directory, verify that the DACL is not too big, and remove any unnecessary extra ACE(s) on the object if necessary.

Fields

Name	Description
`ComputerObject`	—

Event ID 1600 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ComputerObject`	—

Event ID 1601 — The Cluster service successfully brought the Scale-out file server clone online.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service successfully brought the Scale-out file server clone online.

Fields

Name	Description
`ResourceName`	—

Event ID 1602 — The Cluster service successfully brought the Scale-out file server clone offline.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service successfully brought the Scale-out file server clone offline.

Fields

Name	Description
`ResourceName`	—

Event ID 1603 — Cluster service failed to create a clone of the Scale Out File Server resource.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to create a clone of the Scale Out File Server resource. This node will not be able to accept SMB connections to the Scale Out File Server. The error code was '0x%2'. Ensure that the Server service is running and functional on this node. Moving the Scale Out File Server resource to another node will attempt to recreate the clone.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1603 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1604 — Cluster disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster disk resource '%1' detected corruption for volume '%2'. Spotfix Chkdsk is required to repair problems.

Fields

Name	Description
`ResourceName`	—
`VolumeID`	—

Event ID 1604 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`VolumeID`	—

Event ID 1605 — Cluster disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster disk resource '%1' completed running ChkDsk.exe /spotfix on volume '%2'. The return code was '%4'. Output from the ChkDsk has been logged to file '%3'.
 Check the application event log for additional information from ChkDsk.

Fields

Name	Description
`ResourceName`	—
`VolumeID`	—
`Status`	—
`SpotfixLogFile`	—

Event ID 1605 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`VolumeID`	—
`Status`	—
`SpotfixLogFile`	—

Event ID 1606 — Cluster disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster disk resource '%1' contains a BitLocker-protected volume, '%2', but for this volume, the Active Directory cluster name account (also called the cluster name object or CNO) is not a BitLocker protector for the volume. This is required for BitLocker-protected volumes. To correct this, first remove the disk from the cluster. Next, use the Manage-bde.exe command-line tool to add the cluster name as an ADAccountOrGroup protector, using the format domain\ClusterName$ for the cluster name. Then add the disk back to the cluster. For more information, see the documentation for Manage-bde.exe;

Fields

Name	Description
`ResourceName`	—
`VolumeID`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1606 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`VolumeID`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1607 — Cluster disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster disk resource '%1' was unable to unlock the BitLocker-protected volume '%2'. The cluster name object (CNO) is not set to be a valid BitLocker protector for this volume. To correct this, remove the disk from the cluster. Then use the Manage-bde.exe command-line tool to add the cluster name as an ADAccountOrGroup protector, using the format domain\ClusterName$, and add the disk back to the cluster. For more information, see the documentation for Manage-bde.exe.

Fields

Name	Description
`ResourceName`	—
`VolumeID`	—
`Status`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1607 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`VolumeID`	—
`Status`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1608 — File Server could not start because expected dependency on 'Network Name' resource was not found or it was not configured properly.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

File Server could not start because expected dependency on 'Network Name' resource was not found or it was not configured properly. Error=0x%2.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1608 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1609 — Scale Out File Server could not start because expected dependency on 'Distributed Network Name' resource was not found or it was not configured pro...

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Scale Out File Server could not start because expected dependency on 'Distributed Network Name' resource was not found or it was not configured properly. Error=0x%2.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1609 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1632 — The creation of the cluster failed.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The creation of the cluster failed.  Unable to create the cluster name object '%1' in active directory organizational unit '%2'. The object already exists in organizational unit '%3'.  Verify that the specified distinguished name path and the cluster name object are correct.  If the distinguished name path is not specified, the existing computer object '%1' will be used.

Fields

Name	Description
`ComputerObject`	—
`OU1`	—
`OU2`	—

Event ID 1632 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ComputerObject`	—
`OU1`	—
`OU2`	—

Event ID 1633 — The Cluster service failed to bring clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service failed to bring clustered role '%1' completely online or offline. One or more resources may be in a failed or an offline state. This may impact the availability of the clustered role.

Fields

Name	Description
`ResourceGroup`	—

Event ID 1634 — Clustered service or application '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Clustered service or application '%1' has exceeded its failover threshold.  It has exhausted the configured number of failover attempts within the failover period of time alotted to it and will be left in a failed state.  No additional attempts will be made to bring the service or application online or fail it over to another node in the cluster.  Please check the events associated with the failure.  After the issues causing the failure are resolved the service or application can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

Fields

Name	Description
`ResourceGroup`	—

Event ID 1635 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' in clustered role '%2' failed.

Fields

Name	Description
`ResourceName`	—
`ResourceGroup`	—
`ResTypeDll`	—

Event ID 1636 — The Cluster service has changed the password of account '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster service has changed the password of account '%1' on node '%2'.

Fields

Name	Description
`AccountName`	—
`NodeName`	—

Event ID 1637 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' in clustered role '%2' has transitioned from state %3 to state %4.

Fields

Name	Description
`ResourceName`	—
`GroupName`	—
`FromState`	—
`ToState`	—
`BlockingResources`	—
`FromStateValue`	—
`ToStateValue`	—
`TimeInLastState`	—

Event ID 1638 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' in clustered role '%2' has exceeded the maximum number of consecutive failures. It has exhausted the number of restart attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the resource online. Check the events associated with the failure. After the issues causing the failure are resolved the resource can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

Fields

Name	Description
`ResourceName`	—
`GroupName`	—

Event ID 1639 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' in clustered role '%2' cannot come online due to an antiaffinity conflict.

Fields

Name	Description
`ResourceName`	—
`GroupName`	—

Event ID 1640 — Clustered roles with priority less than '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Clustered roles with priority less than '%1' are currently waiting on higher-priority roles to start.

Fields

Name	Description
`BlockingPriority`	—

Event ID 1641 — Clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Clustered role '%1' is moving to cluster node '%2'.

Fields

Name	Description
`GroupName`	—
`PreviousNodeName`	—
`DestinationNodeName`	—
`MoveReason`	—
`SequenceNumber`	—

Event ID 1648 — Clustered role '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Clustered role '%1' is currently waiting for the quorum witness resource to come online before starting.

Fields

Name	Description
`GroupName`	—

Event ID 1649 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' in clustered role '%2' has taken more than one minute to respond to a control code. The control code was '%3'.

Fields

Name	Description
`ResourceName`	—
`GroupName`	—
`ResourceControlCode`	—

Event ID 1650 — Cluster has established a UDP connection from local endpoint %1 connected to remote endpoint %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster has established a UDP connection from local endpoint %1 connected to remote endpoint %2.

Fields

Name	Description
`LocalEndpoint`	—
`RemoteEndpoint`	—

Event ID 1651 — Cluster has received notification that Adapter %1 is now in a connected state.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster has received notification that Adapter %1 is now in a connected state.

Fields

Name	Description
`AdapterName`	—

Event ID 1652 — Cluster node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster node '%1' failed to join the cluster. A TCP connection could not be established to node(s) '%2'. Verify network connectivity and configuration of any network firewalls.

Fields

Name	Description
`NodeName`	—
`RemoteNodeNames`	—

Event ID 1652 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`RemoteNodeNames`	—

Event ID 1653 — Cluster node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster node '%1' failed to join the cluster because it could not communicate over the network with any other node in the cluster. Verify network connectivity and configuration of any network firewalls.

Fields

Name	Description
`NodeName`	—

Event ID 1653 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1654 — Cluster Disjoint IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Disjoint IP address resource '%1' failed to come online. Configuration data for the network adapter corresponding to network adapter '%2' could not be determined (error code was '%3'). Check that the IP address resource is configured with the correct address and network properties.

Fields

Name	Description
`ResourceName`	—
`AdapterName`	—
`Status`	—

Event ID 1654 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`AdapterName`	—
`Status`	—

Event ID 1655 — Cluster Disjoint IP address resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Disjoint IP address resource '%1' failed to come online. Configuration data for the network adapter corresponding to Virtual Subnet Id '%2' and Routing Domain Id '%3' could not be determined (error code was '%4'). Check that the IP address resource is configured with the correct address and network properties.

Fields

Name	Description
`ResourceName`	—
`VSID`	—
`RDID`	—
`Status`	—

Event ID 1655 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`VSID`	—
`RDID`	—
`Status`	—

Event ID 1656 — Failed to add the IP Address '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Failed to add the IP Address '%2' for Disjoint IP address resource '%1' (error code was '%3'). Check for hardware or software errors related to the physical or virtual network adapters.

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`Status`	—

Event ID 1656 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`Status`	—

Event ID 1657 — Health check for IP interface '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Health check for IP interface '%1'(address '%2') failed (status is '%3'). Check for hardware or software errors related to the physical or virtual network adapters.

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`Status`	—

Event ID 1657 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`IPAddress`	—
`Status`	—

Event ID 1658 — Cloud witness resource could not reach Microsoft Azure storage services.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cloud witness resource could not reach Microsoft Azure storage services.\n\nCluster resource: %1 \nCluster node: %2 \n\nGuidance:\nThis could be due to network communication between the cluster node and the Microsoft Azure service being blocked. Verify the node's internet connectivity to Microsoft Azure. Connect to the Microsoft Azure portal and verify that the storage account exists.

Fields

Name	Description
`ResourceName`	—
`NodeName`	—

Event ID 1658 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`NodeName`	—

Event ID 1659 — Cloud witness resource failed to authenticate with Microsoft Azure storage services.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cloud witness resource failed to authenticate with Microsoft Azure storage services. An access denied error was returned while attempting to contact the Microsoft Azure storage account. \n\nCluster resource: %1 \n\nGuidance:\n The storage account's access key may no longer be valid. Use the Configure Cluster Quorum Wizard in the Failover Cluster Manager or the Set-ClusterQuorum Windows PowerShell cmdlet, to configure the Cloud witness resource with the updated storage account access key.

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1659 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—

Event ID 1664 — Upgrading the functional level of the cluster failed.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Upgrading the functional level of the cluster failed. Check that all nodes of the cluster are currently running and are the same version of Windows Server, then run the Update-ClusterFunctionalLevel Windows PowerShell cmdlet again.

Event ID 1664 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 1665 — Online operation for the Physical Disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Online operation for the Physical Disk resource '%1' is started.

Fields

Name	Description
`ResourceName`	—

Event ID 1666 — Online operation for the Physical Disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Online operation for the Physical Disk resource '%1' is completed with status '%2'.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1667 — Offline operation for the Physical Disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Offline operation for the Physical Disk resource '%1' is started.

Fields

Name	Description
`ResourceName`	—

Event ID 1668 — Offline operation for the Physical Disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Offline operation for the Physical Disk resource '%1' is completed with status '%2'.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 1669 — Cluster physical disk resource took longer than expected to reach an online state.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster physical disk resource took longer than expected to reach an online state.

Physical Disk resource name: %1

Guidance:
During the Online Pending phase the Physical Disk resource will wait for dependent components to be ready for the volumes to be mounted. Delays can occur when using replicated volumes if there is a large amount of data that needs to be replicated before the volume is ready to be mounted. The Cluster Service will wait for Storage Replication to respond that it is ready. Review the Storage Replication events for additional information on what operations are taking additional time to complete.

Fields

Name	Description
`ResourceName`	—

Event ID 1670 — Cluster physical disk resource successfully brought the resource online.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster physical disk resource successfully brought the resource online.

Physical Disk resource name: %1
Time Elapsed (seconds): %3

Fields

Name	Description
`ResourceName`	—
`ErrorCode`	—
`TimeElapsedSeconds`	—

Event ID 1671 — Cluster physical disk resource cannot be brought online.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster physical disk resource cannot be brought online.

Physical Disk resource name: %1
Error Code: %2
Time Elapsed (seconds): %3

Guidance:
Run the Validate a Configuration wizard to check your storage configuration. If the error code was ERROR_CLUSTER_SHUTDOWN then the Online Pending state was cancelled by an administrator. If this is a replicated volume then this could be the result of a failure to set the disk attributes.  Review the Storage Replication events for additional information.

Fields

Name	Description
`ResourceName`	—
`ErrorCode`	—
`TimeElapsedSeconds`	—

Event ID 1671 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`ErrorCode`	—
`TimeElapsedSeconds`	—

Event ID 1672 — Cluster node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster node '%1' has been quarantined.  The node experienced '%2' consecutive failures within a short amount of time and has been removed from the cluster to avoid further disruptions. The node will be quarantined until '%3' and then the node will automatically attempt to re-join the cluster.

Refer to the System and Application event logs to determine the issues on this node.  When the issue is resolved, quarantine can be manually cleared to allow the node to rejoin with the 'Start-ClusterNode ?ClearQuarantine' Windows PowerShell cmdlet.

Node Name : %1
Number of consecutive cluster membership loses: %2
Time quarantine will be automatically cleared: %3

Fields

Name	Description
`NodeName`	—
`UngracefulShutdownThreshold`	—
`QuarantineExpiryTime`	—

Event ID 1672 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`UngracefulShutdownThreshold`	—
`QuarantineExpiryTime`	—

Event ID 1673 — Cluster node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster node '%1' has entered the isolated state.

Fields

Name	Description
`ResourceName`	—
`PreviousGroup`	—
`PreviousGroupOwnerNode`	—
`NewGroup`	—
`NewGroupOwnerNode`	—

Event ID 1673 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`PreviousGroup`	—
`PreviousGroupOwnerNode`	—
`NewGroup`	—
`NewGroupOwnerNode`	—

Event ID 1674 — Group '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Group '%1' has transitioned from state '%2' to state '%3'.

Fields

Name	Description
`GroupName`	—
`FromState`	—
`ToState`	—

Event ID 1675 — Cluster node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster node '%1' has been quarantined by '%2' and cannot join the cluster. The node will be quarantined until '%3' and then the node will automatically attempt to re-join the cluster. 

Refer to the System and Application event logs to determine the issues on this node.  When the issue is resolved, quarantine can be manually cleared to allow the node to rejoin with the 'Start-ClusterNode ?ClearQuarantine' Windows PowerShell cmdlet.

Node Name : %1
QuarantineType : Quarantine by %2
Time quarantine will be automatically cleared: %3

Fields

Name	Description
`NodeName`	—
`QuarantineType`	—
`QuarantineExpiryTime`	—

Event ID 1675 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`QuarantineType`	—
`QuarantineExpiryTime`	—

Event ID 1676 — Local cluster node has been quarantined by '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Local cluster node has been quarantined by '%1'. The node will be quarantined until '%2' and then the node will automatically attempt to re-join the cluster. 

Refer to the System and Application event logs to determine the issues on this node.  When the issue is resolved, quarantine can be manually cleared to allow the node to rejoin with the 'Start-ClusterNode ?ClearQuarantine' Windows PowerShell cmdlet.

QuarantineType : Quarantined by %1
Time quarantine will be automatically cleared: %2

Fields

Name	Description
`QuarantineType`	—
`QuarantineExpiryTime`	—

Event ID 1676 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`QuarantineType`	—
`QuarantineExpiryTime`	—

Event ID 1677 — Node drain failed on Cluster node %1.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Node drain failed on Cluster node %1. 

Reference the node's System and Application event logs and cluster logs to investigate the cause of the drain failure.  When the problem is resolved, you can retry the drain operation.

Fields

Name	Description
`NodeName`	—

Event ID 1677 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1680 — Cluster node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster node '%1' has exited the isolated state.

Fields

Name	Description
`NodeName`	—

Event ID 1680 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1681 — Virtual machines on node '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Virtual machines on node '%1' have entered an unmonitored state. The virtual machines health will be monitored again once the node returns from an isolated state or may failover if the node does not return. The virtual machine no longer being monitored are: %2.

Fields

Name	Description
`NodeName`	—
`GroupList`	—

Event ID 1681 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`GroupList`	—

Event ID 1682 — Virtual machine '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Virtual machine '%2' which was unmonitored on the isolated node '%1' has been failed over to another node. The health of the virtual machine is once again being monitored.

Fields

Name	Description
`NodeName`	—
`GroupList`	—

Event ID 1682 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`GroupList`	—

Event ID 1683 — The cluster service was unable to reach any available domain controller on the domain.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service was unable to reach any available domain controller on the domain. This may impact functionality that is dependent on Cluster network name authentication.

DC Server: %1 

Guidance:
 Verify that domain controllers are accessible on the network to the cluster nodes.

Fields

Name	Description
`ResourceName`	—
`DomainController`	—

Event ID 1683 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DomainController`	—

Event ID 1684 — Cluster network name resource failed to find the associated computer object in Active Directory.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource failed to find the associated computer object in Active Directory. This may impact functionality that is dependent on Cluster network name authentication.

Network Name: %1
Organizational Unit: %2

Guidance:

Restore the computer object for the network name from the Active Directory recycle bin. Alternately, offline the cluster network name resource and run the Repair action to recreate the computer object in Active Directory.

Fields

Name	Description
`ResourceName`	—
`OrganizationalUnit`	—

Event ID 1684 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`OrganizationalUnit`	—

Event ID 1685 — Cluster network name resource failed to find the associated computer object in Active Directory.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource failed to find the associated computer object in Active Directory. This may impact functionality that is dependent on Cluster network name authentication.

Network Name: %1
Organizational Unit: %2

Guidance:

Restore the computer object for the network name from the Active Directory recycle bin.

Fields

Name	Description
`ResourceName`	—
`OrganizationalUnit`	—

Event ID 1685 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`OrganizationalUnit`	—

Event ID 1686 — Cluster network name resource found the associated computer object in Active Directory to be disabled.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource found the associated computer object in Active Directory to be disabled. This may impact functionality that is dependent on Cluster network name authentication.

Network Name: %1
Organizational Unit: %2

Guidance:

Enable the computer object for the network name in Active Directory.

Fields

Name	Description
`ResourceName`	—
`OrganizationalUnit`	—

Event ID 1686 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`OrganizationalUnit`	—

Event ID 1687 — Cluster network name resource found the associated computer object in Active Directory to be disabled.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource found the associated computer object in Active Directory to be disabled. This may impact functionality that is dependent on Cluster network name authentication.

Network Name: %1
Organizational Unit: %2

Guidance:

Enable the computer object for the network name in Active Directory. Alternately, offline the cluster network name resource and run the Repair action to enable the computer object in Active Directory.

Fields

Name	Description
`ResourceName`	—
`OrganizationalUnit`	—

Event ID 1687 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`OrganizationalUnit`	—

Event ID 1688 — Cluster network name resource detected that the associated computer object in Active Directory was disabled and failed in its attempt to enable it.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster network name resource detected that the associated computer object in Active Directory was disabled and failed in its attempt to enable it. This may impact functionality that is dependent on Cluster network name authentication.

Network Name: %1
Organizational Unit: %2

Guidance:

Enable the computer object for the network name in Active Directory.

Fields

Name	Description
`ResourceName`	—
`OrganizationalUnit`	—
`Status`	—

Event ID 1688 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`OrganizationalUnit`	—
`Status`	—

Event ID 1689 — The cluster service detected a service which is not compatible with Failover Clustering.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service detected a service which is not compatible with Failover Clustering. The service has been disabled to avoid possible problems with the Failover Cluster.

Service name: '%1'

Fields

Name	Description
`ServiceName`	—

Event ID 1689 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ServiceName`	—

Event ID 1690 — The cluster role was not brought online automatically because IgnorePersistentStateOnStartup is enabled.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster role was not brought online automatically because IgnorePersistentStateOnStartup is enabled. This parameter is used for troubleshooting Cluster Service startup issues and prevents cluster roles from coming online automatically. 

 Role: %1 

 Guidance:
Once the troubleshooting is complete, this parameter can be disabled to allow roles to online automatically by using the following Windows PowerShell cmdlet: (Get-Cluster).IgnorePersistentStateOnStartup = 0

Fields

Name	Description
`GroupName`	—

Event ID 1690 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`GroupName`	—

Event ID 1691 — The cluster service started with the IgnorePersistentStateOnStartup parameter enabled.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service started with the IgnorePersistentStateOnStartup parameter enabled. This parameter is used for troubleshooting Cluster Service startup issues and prevents cluster roles from coming online automatically. 

Guidance:
Once the troubleshooting is complete, this parameter can be disabled to allow roles to online automatically by using the following Windows PowerShell cmdlet: (Get-Cluster).IgnorePersistentStateOnStartup = 0

Event ID 1691 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 1792 — Cluster physical disk resource failed periodic health check.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster physical disk resource failed periodic health check. 

 Physical Disk resource name: %1 
 Device Number: %2 
 Device Guid: %3 
  Error Code: %4 
 Reason: %5

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—
`ErrorCode`	—
`ReasonMessage`	—

Event ID 1792 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—
`ErrorCode`	—
`ReasonMessage`	—

Event ID 1793 — Cluster physical disk resource failed to come online.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster physical disk resource failed to come online.

Resource Name: %1
Device Number: %2
Device Guid: %3
Error Code: %4
Reason: %5

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—
`ErrorCode`	—
`ReasonMessage`	—

Event ID 1793 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—
`ErrorCode`	—
`ReasonMessage`	—

Event ID 1794 — Cluster physical disk resource failed to go offline.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster physical disk resource failed to go offline.

Physical Disk Resource Name: %1
Device Number: %2
Device Guid: %3
Error Code: %4
Additional reason: %5

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—
`ErrorCode`	—
`ReasonMessage`	—

Event ID 1794 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—
`ErrorCode`	—
`ReasonMessage`	—

Event ID 1795 — Cluster physical disk resource encountered an error while attempting to terminate.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster physical disk resource encountered an error while attempting to terminate.

Phsyical Disk Resource Name: %1
Device Number: %2
Device Guid: %3
Error Code: %4
Reason: %5

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—
`ErrorCode`	—
`ReasonMessage`	—

Event ID 1795 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`DeviceNumber`	—
`DeviceGuid`	—
`ErrorCode`	—
`ReasonMessage`	—

Event ID 1808 — The cluster load balancer has identified the current node is exceeding the CPU or memory usage threshold.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The cluster load balancer has identified the current node is exceeding the CPU or memory usage threshold.  Virtual Machines will be moved to a new node to balance the cluster. 

 Current Node: %1 
 Virtual Machines: %2 
 New Node: %3

Fields

Name	Description
`FromNodeName`	—
`GroupName`	—
`ToNodeName`	—

Event ID 1809 — This node has been joined to a cluster that has Storage Spaces Direct enabled, which is not validated on the current build.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

This node has been joined to a cluster that has Storage Spaces Direct enabled, which is not validated on the current build. The node will be quarantined.

Microsoft recommends deploying SDDC on WSSD [https://www.microsoft.com/en-us/cloud-platform/software-defined-datacenter] certified hardware offerings for production environments. The WSSD offerings will be pre-validated on Windows Server 2019 in the coming months. In the meantime, we are making the SDDC bits available early to Windows Server 2019 Insiders to allow for testing and evaluation in preparation for WSSD certified hardware becoming available.

Customers interested in upgrading existing WSSD environments to Windows Server 2019 should contact Microsoft for recommendations on how to proceed. Please call Microsoft support [https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers].

Fields

Name	Description
`NodeName`	—

Event ID 1809 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—

Event ID 1810 — Cluster Physical Disk Resource added a protector to a BitLocker encrypted volume.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Physical Disk Resource added a protector to a BitLocker encrypted volume. 

ResourceName: %1
Volume: %2
ProtectorType: %3
ProtectorId: %4
TimeInMilliseconds: %5

Fields

Name	Description
`ResourceName`	—
`Volume`	—
`ProtectorType`	—
`ProtectorId`	—
`TimeInMilliseconds`	—

Event ID 1811 — Cluster Physical Disk Resource failed to add a protector to a BitLocker encrypted volume.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Physical Disk Resource failed to add a protector to a BitLocker encrypted volume. 

ResourceName: %1
Volume: %2
ProtectorType: %3
TimeInMilliseconds: %4
Status: %5

Fields

Name	Description
`ResourceName`	—
`Volume`	—
`ProtectorType`	—
`TimeInMilliseconds`	—
`Status`	—

Event ID 1812 — Cluster Physical Disk Resource completed a storage operation.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Physical Disk Resource completed a storage operation. 

ResourceName: %1
Device: %2
Operation: %3
TimeInMilliseconds: %4
Status: %5
AdditionalInformation: %6

Fields

Name	Description
`ResourceName`	—
`Device`	—
`Operation`	—
`TimeInMilliseconds`	—
`Status`	—
`AdditionalInformation`	—

Event ID 1813 — Cluster Physical Disk Resource completed resource online.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Physical Disk Resource completed resource online.

ResourceName: %1
OperationTimes: %2
TotalTimeInMilliseconds: %3
Status: %4

Fields

Name	Description
`ResourceName`	—
`OperationTimes`	—
`TotalTimeInMilliseconds`	—
`Status`	—

Event ID 1814 — Cluster Physical Disk Resource completed resource offline.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Physical Disk Resource completed resource offline.

ResourceName: %1
OperationTimes: %2
TotalTimeInMilliseconds: %3
Status: %4

Fields

Name	Description
`ResourceName`	—
`OperationTimes`	—
`TotalTimeInMilliseconds`	—
`Status`	—

Event ID 1815 — Cluster Physical Disk Resource completed resource terminate.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Physical Disk Resource completed resource terminate.

ResourceName: %1
OperationTimes: %2
TotalTimeInMilliseconds: %3
Status: %4

Fields

Name	Description
`ResourceName`	—
`OperationTimes`	—
`TotalTimeInMilliseconds`	—
`Status`	—

Event ID 1816 — Cluster Physical Disk Resource could not find expected number of usable data volumes during online.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Physical Disk Resource could not find expected number of usable data volumes during online.

ResourceName: %1
Device: %2
VolumesExpected: %3
VolumesFound: %4

Fields

Name	Description
`ResourceName`	—
`Device`	—
`VolumesExpected`	—
`VolumesFound`	—

Event ID 1817 — Cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster resource '%1' in clustered role '%2' has transitioned to an online state after failure. %3 millisecond(s) have elapsed since the resource failed.

Fields

Name	Description
`ResourceName`	—
`GroupName`	—
`TimeSinceFailure`	—

Event ID 1824 — Cluster Physical Disk Resource contains a BitLocker protected volume, but the system volume is not BitLocker protected.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Physical Disk Resource contains a BitLocker protected volume, but the system volume is not BitLocker protected. For data protection, it is recommended that the system volume be BitLocker protected as well.

ResourceName: %1

Fields

Name	Description
`ResourceName`	—

Event ID 1825 — Cluster Physical Disk Resource saved a protector to a BitLocker encrypted volume.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Physical Disk Resource saved a protector to a BitLocker encrypted volume. 

ResourceName: %1
Volume: %2
ProtectorType: %3
ProtectorId: %4

Fields

Name	Description
`ResourceName`	—
`Volume`	—
`ProtectorType`	—
`ProtectorId`	—

Event ID 1826 — Node drain failed on Cluster node %1.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node drain failed on Cluster node %1. 

Reference the node's System and Application event logs and cluster logs to investigate the cause of the drain failure.  When the problem is resolved, you can retry the drain operation.

Fields

Name	Description
`NodeName`	—
`Reason`	—

Event ID 1827 — Node drain succeeded on Cluster node %1.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node drain succeeded on Cluster node %1.

Fields

Name	Description
`NodeName`	—

Event ID 1828 — Node drain started on Cluster node %1.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node drain started on Cluster node %1.

Fields

Name	Description
`NodeName`	—

Event ID 1829 — Node drain started second attempt on Cluster node %1.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node drain started second attempt on Cluster node %1.

Fields

Name	Description
`NodeName`	—

Event ID 1830 — Node failback failed on Cluster node %1.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node failback failed on Cluster node %1. Groups: %2. 

Reference the node's System and Application event logs and cluster logs to investigate the cause of the drain failure.  When the problem is resolved, you can retry the drain operation.

Fields

Name	Description
`NodeName`	—
`ExtraInfo`	—

Event ID 1831 — Node failback succeeded on Cluster node %1 after being called from %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node failback succeeded on Cluster node %1 after being called from %2

Fields

Name	Description
`NodeName`	—
`Origin`	—

Event ID 1832 — Node Resume started on Cluster node %1.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node Resume started on Cluster node %1.

Fields

Name	Description
`NodeName`	—
`Origin`	—

Event ID 1833 — Node failback started on Cluster node %1 due to being called from %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node failback started on Cluster node %1 due to being called from %2

Fields

Name	Description
`NodeName`	—
`Origin`	—

Event ID 1840 — Node Failback did not run on Cluster node %1 after being called from %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node Failback did not run on Cluster node %1 after being called from %2. Reason: %3

Fields

Name	Description
`NodeName`	—
`Origin`	—
`Reason`	—

Event ID 1841 — Node resume succeeded on Cluster node %1 after being called from %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Node resume succeeded on Cluster node %1 after being called from %2

Fields

Name	Description
`NodeName`	—
`Origin`	—

Event ID 2049 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 2049 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 2050 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 2050 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 2051 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 2051 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 2052 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 2052 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 4096 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`Address`	—
`State`	—
`LogTime`	—

Event ID 4096 — [NETFTAPI] received %1 for %2 (%3).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] received %1 for %2 (%3)

Fields

Name	Description
`Notification`	—
`Address`	—
`State`	—
`LogTime`	—

Event ID 4097 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`Address`	—
`State`	—
`LogTime`	—

Event ID 4097 — [NETFTAPI] received %1 for %2 (%3).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] received %1 for %2 (%3)

Fields

Name	Description
`Notification`	—
`Address`	—
`State`	—
`LogTime`	—

Event ID 4098 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`Address`	—
`LogTime`	—

Event ID 4098 — [NETFTAPI] received %1 for %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] received %1 for %2

Fields

Name	Description
`Notification`	—
`Address`	—
`LogTime`	—

Event ID 4099 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`Address`	—
`LogTime`	—

Event ID 4099 — [NETFTAPI] received %1 for %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] received %1 for %2

Fields

Name	Description
`Notification`	—
`Address`	—
`LogTime`	—

Event ID 4100 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`LogTime`	—

Event ID 4100 — [NETFTAPI] received %1.

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] received %1

Fields

Name	Description
`Notification`	—
`LogTime`	—

Event ID 4101 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`Address`	—
`LogTime`	—

Event ID 4101 — [NETFTAPI] Signaled %1 event for %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Signaled %1 event for %2

Fields

Name	Description
`Notification`	—
`Address`	—
`LogTime`	—

Event ID 4102 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`Address`	—
`LogTime`	—

Event ID 4102 — [NETFTAPI] Signaled %1 event for %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Signaled %1 event for %2

Fields

Name	Description
`Notification`	—
`Address`	—
`LogTime`	—

Event ID 4103 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`LocalAddress`	—
`LocalPort`	—
`RemoteAddress`	—
`RemotePort`	—
`LogTime`	—

Event ID 4103 — [NETFTAPI] Signaled %1 event, local address %2:%3 remote address %4:%5.

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Signaled %1 event, local address %2:%3 remote address %4:%5

Fields

Name	Description
`Notification`	—
`LocalAddress`	—
`LocalPort`	—
`RemoteAddress`	—
`RemotePort`	—
`LogTime`	—

Event ID 4104 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`LocalAddress`	—
`LocalPort`	—
`RemoteAddress`	—
`RemotePort`	—
`LogTime`	—

Event ID 4104 — [NETFTAPI] Signaled %1 event, local address [%2]:%3 remote address [%4]:%5.

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Signaled %1 event, local address [%2]:%3 remote address [%4]:%5

Fields

Name	Description
`Notification`	—
`LocalAddress`	—
`LocalPort`	—
`RemoteAddress`	—
`RemotePort`	—
`LogTime`	—

Event ID 4105 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`Alias`	—
`LogTime`	—

Event ID 4105 — [NETFTAPI] Signaled %1 event, alias %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Signaled %1 event, alias %2

Fields

Name	Description
`Notification`	—
`Alias`	—
`LogTime`	—

Event ID 4106 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4106 — [NETFTAPI] Failed to allocate %1 network address entry (status %2).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Failed to allocate %1 network address entry (status %2)

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4107 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4107 — [NETFTAPI] Failed to allocate %1 network address entry (status %2).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Failed to allocate %1 network address entry (status %2)

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4108 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4108 — [NETFTAPI] Failed to query initialization parameters for %1 (status %2).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Failed to query initialization parameters for %1 (status %2)

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4109 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4109 — [NETFTAPI] Failed to query initialization parameters for %1 (status %2).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Failed to query initialization parameters for %1 (status %2)

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4110 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4110 — [NETFTAPI] Failed to query parameters for %1 (status %2).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Failed to query parameters for %1 (status %2)

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4111 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4111 — [NETFTAPI] Failed to query parameters for %1 (status %2).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Failed to query parameters for %1 (status %2)

Fields

Name	Description
`Address`	—
`Status`	—
`LogTime`	—

Event ID 4112 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—
`LogTime`	—

Event ID 4112 — [NETFTAPI] Subscriber thrown exception %1 processing NETFT notification.

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Subscriber thrown exception %1 processing NETFT notification

Fields

Name	Description
`Status`	—
`LogTime`	—

Event ID 4113 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Interface`	—
`Status`	—
`LogTime`	—

Event ID 4113 — [NETFTAPI] Failed to allocate %1 network interface entry (status %2).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Failed to allocate %1 network interface entry (status %2)

Fields

Name	Description
`Interface`	—
`Status`	—
`LogTime`	—

Event ID 4114 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 4114 — [NETFTAPI] The IPv4/802 provider is not present

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] The IPv4/802 provider is not present

Event ID 4115 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 4115 — [NETFTAPI] The IPv6/802 provider is not present

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] The IPv6/802 provider is not present

Event ID 4116 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—
`LogTime`	—

Event ID 4116 — [NETFTAPI] Event processing thread failed to register for NETFT event (status %1).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Event processing thread failed to register for NETFT event (status %1)

Fields

Name	Description
`Status`	—
`LogTime`	—

Event ID 4117 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—
`LogTime`	—

Event ID 4117 — [NETFTAPI] Event processing thread completed processing loop (status %1).

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] Event processing thread completed processing loop (status %1)

Fields

Name	Description
`Status`	—
`LogTime`	—

Event ID 4118 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Notification`	—
`LogTime`	—

Event ID 4118 — [NETFTAPI] The watchdog miniport is halting.

Provider: Microsoft-Windows-FailoverClustering
Channel: Diagnostic

Message

[NETFTAPI] The watchdog miniport is halting.

Fields

Name	Description
`Notification`	—
`LogTime`	—

Event ID 4608 — The list of clustered disks has been retrieved during cluster node cleanup.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The list of clustered disks has been retrieved during cluster node cleanup.

Event ID 4609 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 4609 — Cluster service failed to retrieve the list of clustered disks while destroying the cluster.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to retrieve the list of clustered disks while destroying the cluster. The error code was '%1'. If these disks are not accessible, execute the 'Clear-ClusterDiskReservation' PowerShell cmdlet.

Fields

Name	Description
`Status`	—

Event ID 4610 — Clustered disks have been released by the Partition Manager while destroying the cluster.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Clustered disks have been released by the Partition Manager while destroying the cluster. These disks will be left in an offline state. For these released disks to be accessible, please bring them online on a single machine only, using the Disk Management utility.

Event ID 4611 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—
`DiskId`	—

Event ID 4611 — Clustered disk with ID '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Clustered disk with ID '%2' was not released by the Partition Manager while destroying the cluster. The error code was '%1'. Restarting the machine will ensure the disk is released by the Partition Manager.

Fields

Name	Description
`Status`	—
`DiskId`	—

Event ID 4612 — The clustered disks database has been cleared as part of cluster node cleanup.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The clustered disks database has been cleared as part of cluster node cleanup.

Event ID 4613 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—
`DiskId`	—

Event ID 4613 — The cluster service failed to properly cleanup a clustered disk with ID '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service failed to properly cleanup a clustered disk with ID '%2' while destroying the cluster. The error code was '%1'. You may unable to access this disk until cleanup has been successfully completed. For manual cleanup, delete the 'AttachedDisks' value of the 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusDisk\Parameters' key in the Windows registry.

Fields

Name	Description
`Status`	—
`DiskId`	—

Event ID 4614 — The cluster service has been stopped and set as disabled as part of cluster node cleanup.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The cluster service has been stopped and set as disabled as part of cluster node cleanup.

Event ID 4615 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 4615 — Disabling the cluster service during cluster node cleanup, has failed.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Disabling the cluster service during cluster node cleanup, has failed. The error code was '%1'. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine.

Fields

Name	Description
`Status`	—

Event ID 4616 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 4616 — Termination of the cluster service during cluster node cleanup has not completed within the expected time period.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Termination of the cluster service during cluster node cleanup has not completed within the expected time period. Please restart this machine to ensure the cluster service is no longer running.

Event ID 4617 — The cluster service registry entries on this machine have been reset as part of cluster node cleanup.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The cluster service registry entries on this machine have been reset as part of cluster node cleanup.

Event ID 4618 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 4618 — Resetting cluster service registry entries during cluster node cleanup failed.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Resetting cluster service registry entries during cluster node cleanup failed. The error code was '%1'. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine.

Fields

Name	Description
`Status`	—

Event ID 4619 — The cluster Windows registry hive has been unloaded.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The cluster Windows registry hive has been unloaded.

Event ID 4620 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 4620 — Unloading the cluster service registry hive during cluster node cleanup failed.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Unloading the cluster service registry hive during cluster node cleanup failed. The error code was '%1'. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine.

Fields

Name	Description
`Status`	—

Event ID 4621 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 4621 — This node was sucessfully removed from the cluster.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

This node was sucessfully removed from the cluster.

Event ID 4622 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 4622 — The Cluster service encountered an error during node cleanup.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service encountered an error during node cleanup. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. Use the 'Clear-ClusterNode' PowerShell cmdlet on this node.

Event ID 4623 — The IPSec security association timeout has been reset on this machine as part of cluster node cleanup.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The IPSec security association timeout has been reset on this machine as part of cluster node cleanup. This restores the IPSec security association timeout to the default policy for non-clustered machines.

Event ID 4624 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—
`RegValue1`	—
`RegValue2`	—

Event ID 4624 — Resetting the IPSec security association timeout registry value failed during cluster node cleanup.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Resetting the IPSec security association timeout registry value failed during cluster node cleanup. The error code was '%1'. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine. Alternatively, you may reset the IPSec security association timeout by deleting the '%2' value and the '%3' value from HKEY_LOCAL_MACHINE in the Windows registry.

Fields

Name	Description
`Status`	—
`RegValue1`	—
`RegValue2`	—

Event ID 4625 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`RegValue1`	—
`RegValue2`	—

Event ID 4625 — Resetting the IPSec security association timeout registry value failed during cluster node cleanup.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Resetting the IPSec security association timeout registry value failed during cluster node cleanup. This is because the IPSec security association timeout was modified after this machine was configured to be a member of a cluster. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine. Alternatively, you may reset the IPSec security association timeout by deleting the '%1' value and the '%2' value from HKEY_LOCAL_MACHINE in the Windows registry.

Fields

Name	Description
`RegValue1`	—
`RegValue2`	—

Event ID 4626 — All clustered tasks on this node have been deleted as part of node cleanup.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

All clustered tasks on this node have been deleted as part of node cleanup.

Event ID 4627 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 4627 — Deletion of clustered tasks during node cleanup failed.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Deletion of clustered tasks during node cleanup failed. The error code was '%1'. Use Windows Task Scheduler to delete any remaining clustered tasks.

Fields

Name	Description
`Status`	—

Event ID 4628 — During node cleanup, the local user account that is managed by the cluster was deleted.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

During node cleanup, the local user account that is managed by the cluster was deleted.

Event ID 4629 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 4629 — During node cleanup, the local user account that is managed by the cluster was not deleted.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

During node cleanup, the local user account that is managed by the cluster was not deleted.  The error code was '%1'. Open Local Users and Groups (lusrmgr.msc) to delete the account.

Fields

Name	Description
`Status`	—

Event ID 4864 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 4864 — Volume shadow copy service task resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Volume shadow copy service task resource '%1' creation failed. The error code was '%2'.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 4865 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 4865 — Volume shadow copy service task resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Volume shadow copy service task resource '%1' failed. The error code was '%2'. This is because the associated task could not be stopped as part of an offline operation. You may need to stop it manually using the Task Scheduler snapin.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 4866 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 4866 — Volume shadow copy service task resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Volume shadow copy service task resource '%1' failed. The error code was '%2'. This is because the associated task could not be deleted as part of an offline operation. You may need to delete it manually using the Task Scheduler snapin.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 4867 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 4867 — Volume shadow copy service task resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Volume shadow copy service task resource '%1' failed. The error code was '%2'. This is because the associated task could not be added as part of an online operation. Please use the Task Scheduler snapin to ensure your tasks are properly configured.

Fields

Name	Description
`ResourceName`	—
`Status`	—

Event ID 4868 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`SessionName`	—
`Status`	—

Event ID 4868 — Cluster service failed to start the cluster log trace session.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to start the cluster log trace session. The error code was '%2'. The cluster will function properly, but supplemental logging information will be missing. Use the Performance Monitor snapin to verify the event channel settings for '%1'.

Fields

Name	Description
`SessionName`	—
`Status`	—

Event ID 4869 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ProcessName`	—
`ProcessId`	—
`Period`	—

Event ID 4869 — User mode health monitoring has detected that the system is not being responsive.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

User mode health monitoring has detected that the system is not being responsive. The Failover cluster virtual adapter has lost contact with the '%1' process with a process ID '%2', for '%3' seconds. Please use Performance Monitor to evaluate the health of the system and determine which process may be negatively impacting the system.

Fields

Name	Description
`ProcessName`	—
`ProcessId`	—
`Period`	—

Event ID 4870 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ProcessName`	—
`ProcessId`	—
`Period`	—

Event ID 4870 — User mode health monitoring has detected that the system is not being responsive.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

User mode health monitoring has detected that the system is not being responsive. The Failover cluster virtual adapter has lost contact with the '%1' process with a process ID '%2', for '%3' seconds. Recovery action will be taken.

Fields

Name	Description
`ProcessName`	—
`ProcessId`	—
`Period`	—

Event ID 4871 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 4871 — The cluster service failed to start.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service failed to start. This was because the failover cluster virtual adapter failed to initialize the miniport adapter. The error code was '%1'. Verify that other network adapters are functioning properly and check the device manager for errors. If the configuration was changed, it may be necessary to reinstall the failover clustering feature on this computer.

Fields

Name	Description
`Status`	—

Event ID 4872 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 4872 — The failover cluster virtual adapter failed to generate a unique MAC address.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The failover cluster virtual adapter failed to generate a unique MAC address. Either it was unable to find a physical Ethernet adapter from which to generate a unique address or the generated address conflicts with another adapter on this machine. Please run the Validate a Configuration wizard to check your network configuration.

Fields

Name	Description
`Status`	—

Event ID 4873 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 4873 — The cluster service has detected that the failover cluster virtual adapter has stopped.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster service has detected that the failover cluster virtual adapter has stopped. This is expected when hot replace CPU is performed on this node. Cluster service will stop and should automatically restart after the operation is complete. Please check for additional events associated with the service and ensure that the cluster service has been restarted on this node.

Event ID 4874 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ProcessName`	—
`ProcessId`	—
`Period`	—

Event ID 4874 — User mode health monitoring has detected that the system is not being responsive.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

User mode health monitoring has detected that the system is not being responsive. The Failover Cluster virtual adapter has lost contact with a process. Recovery action will be taken.  

 Process: %1 
 Process ID: %2 
 Seconds: %3

Fields

Name	Description
`ProcessName`	—
`ProcessId`	—
`Period`	—

Event ID 5120 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`ErrorCode`	—
`DiskDeviceNumber`	—
`DiskDeviceGuid`	—

Event ID 5120 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Shared Volume '%1' ('%2') has entered a paused state because of '%3'. All I/O will temporarily be queued until a path to the volume is reestablished.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`ErrorCode`	—
`DiskDeviceNumber`	—
`DiskDeviceGuid`	—

Event ID 5121 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—

Event ID 5121 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Shared Volume '%1' ('%2') is no longer directly accessible from this cluster node. I/O access will be redirected to the storage device over the network to the node that owns the volume. If this results in degraded performance, please troubleshoot this node's connectivity to the storage device and I/O will resume to a healthy state once connectivity to the storage device is reestablished.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—

Event ID 5122 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume '%1' ('%2') has now resumed normal operation.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—

Event ID 5123 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ErrorMessage`	—
`RootName`	—
`Status`	—

Event ID 5123 — Cluster service failed to create the Cluster Shared Volumes root directory '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to create the Cluster Shared Volumes root directory '%2'. The error message was '%1'.

Fields

Name	Description
`ErrorMessage`	—
`RootName`	—
`Status`	—

Event ID 5124 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`RootName`	—
`RenamedDirectoryName`	—

Event ID 5124 — Cluster Shared Volumes root directory '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Shared Volumes root directory '%1' already exists. The directory '%1' was renamed to '%2'. Please verify that applications accessing data in this location have been updated as necessary.

Fields

Name	Description
`RootName`	—
`RenamedDirectoryName`	—

Event ID 5125 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeName`	—
`DriverNames`	—
`ResourceName`	—

Event ID 5125 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Shared Volume '%1' ('%3') has identified one or more active filter drivers on this device stack that could interfere with CSV operations. I/O access will be redirected to the storage device over the network through another Cluster node. This may result in degraded performance. Please contact the filter driver vendor to verify interoperability with Cluster Shared Volumes. 

Active filter drivers found:
%2

Fields

Name	Description
`VolumeName`	—
`DriverNames`	—
`ResourceName`	—

Event ID 5126 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeName`	—
`DriverName`	—
`ResourceName`	—

Event ID 5126 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Shared Volume '%1' ('%3') has identified one or more active volume drivers on this device stack that could interfere with CSV operations. I/O access will be redirected to the storage device over the network through another Cluster node. This may result in degraded performance. Please contact the volume driver vendor to verify interoperability with Cluster Shared Volumes. 

Active volume drivers found:
%2

Fields

Name	Description
`VolumeName`	—
`DriverName`	—
`ResourceName`	—

Event ID 5128 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 5128 — Physical disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Physical disk resource '%1' does not allow disabling short name generation. This may cause application compatibility issues. Please use 'fsutil 8dot3name set 2' to allow disabling short name generation and then offline/online the resource.

Fields

Name	Description
`ResourceName`	—

Event ID 5129 — Cluster Shared Volumes has been enabled on this cluster by user '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volumes has been enabled on this cluster by user '%1'.

Fields

Name	Description
`UserName`	—

Event ID 5130 — Cluster Shared Volumes has been disabled on this cluster by user '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volumes has been disabled on this cluster by user '%1'.

Fields

Name	Description
`UserName`	—

Event ID 5131 — Cluster Disk '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Disk '%1' has been added to Cluster Shared Volumes.

Fields

Name	Description
`ResourceName`	—

Event ID 5132 — Cluster Disk '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Disk '%1' has been removed from Cluster Shared Volumes. The disk resource '%1' is now part of the 'Available Storage' cluster group.

Fields

Name	Description
`ResourceName`	—

Event ID 5133 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 5133 — Cluster Disk '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Disk '%1' has been removed and placed back in the 'Available Storage' cluster group. During this process an attempt to restore the original drive letter(s) has taken longer than expected, possibly due to those drive letters being already in use.

Fields

Name	Description
`ResourceName`	—

Event ID 5134 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`RootName`	—
`ErrorMessage`	—
`Status`	—

Event ID 5134 — Cluster service failed to set the permissions (ACL) on the Cluster Shared Volumes root directory '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to set the permissions (ACL) on the Cluster Shared Volumes root directory '%1'. The error was '%2'.

Fields

Name	Description
`RootName`	—
`ErrorMessage`	—
`Status`	—

Event ID 5135 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`FolderName`	—
`ResourceName`	—
`ErrorMessage`	—
`Status`	—

Event ID 5135 — Cluster service failed to set the permissions on the Cluster Shared Volume directory '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to set the permissions on the Cluster Shared Volume directory '%1' ('%2'). The error was '%3'.

Fields

Name	Description
`FolderName`	—
`ResourceName`	—
`ErrorMessage`	—
`Status`	—

Event ID 5136 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—

Event ID 5136 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Shared Volume '%1' ('%2') redirected access was turned on. Access to the storage device will be redirected over the network from all cluster nodes that are accessing this volume. This may result in degraded performance. Turn off redirected access for this volume to resume normal operations.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—

Event ID 5137 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume '%1' ('%2') redirected access was turned off. The volume has now resumed normal operation.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—

Event ID 5138 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume '%1' ('%2') maintenance was turned on. This volume will not be accessible by the highly available service or application until maintenance is complete and the volume maintenance is turned off.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—

Event ID 5139 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume '%1' ('%2') maintenance was turned off.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—

Event ID 5140 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume '%1' ('%2') backup was turned on. Once the backup application completes the backup process, the Cluster Shared Volume backup mode will be turned off. If the backup application has not initiated a snapshot using the Volume Shadow Copy Service within %3 minutes, Cluster Shared Volume backup will be turned off.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`MaximumTimeMinutes`	—

Event ID 5141 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume '%1' ('%2') backup was turned off.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—

Event ID 5142 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`ErrorCode`	—
`ReasonCode`	—
`DiskDeviceNumber`	—
`DiskDeviceGuid`	—

Event ID 5142 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Shared Volume '%1' ('%2') is no longer accessible from this cluster node because of error '%3'. Please troubleshoot this node's connectivity to the storage device and network connectivity.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`ErrorCode`	—
`ReasonCode`	—
`DiskDeviceNumber`	—
`DiskDeviceGuid`	—

Event ID 5143 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`NodeName`	—
`ResourceName`	—
`CcDirtyPageThreshold`	—
`CcTotalDirtyPages`	—
`ErrorCode`	—

Event ID 5143 — Move of the disk ('%2') is vetoed based on the current state of the Cache Manager on the node '%1' to prevent a potential deadlock.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Move of the disk ('%2') is vetoed based on the current state of the Cache Manager on the node '%1' to prevent a potential deadlock. 'Cache Manager Dirty Pages Theshold' is %3, and 'Cache Manager Dirty Pages' is %4. Move is allowed if 'Cache Manager Dirty Pages' is less than 70% of 'Cache Manager Dirty Pages Theshold' or if 'Cache Manager Dirty Pages Theshold' minus 'Cache Manager Dirty Pages' is greater than 128000 pages (about 500MB if a page size is 4096 bytes). Cluster vetoed resource move to prevent potential deadlock due to Cache Manager throttling buffered writes while Cluster Shared Volumes on this disk are being paused.

Fields

Name	Description
`NodeName`	—
`ResourceName`	—
`CcDirtyPageThreshold`	—
`CcTotalDirtyPages`	—
`ErrorCode`	—

Event ID 5144 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`VolumeName`	—
`SnapshotVolume`	—

Event ID 5144 — While adding the disk ('%1') to Cluster Shared Volumes, setting explicit snapshot diff area association for volume ('%2') failed with error '%3'.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

While adding the disk ('%1') to Cluster Shared Volumes, setting explicit snapshot diff area association for volume ('%2') failed with error '%3'. The only supported software snapshot diff area association for Cluster Shared Volumes is to self.

Fields

Name	Description
`ResourceName`	—
`VolumeName`	—
`SnapshotVolume`	—

Event ID 5145 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`VolumeName`	—
`DiffVolume`	—

Event ID 5145 — Cluster disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster disk resource '%1' failed to delete a software snapshot.  The diff area on volume '%3' could not be dissociated from volume '%2'. This may be caused by active snapshots. Cluster Shared Volumes requires that the software snapshot be located on the same disk.

Fields

Name	Description
`ResourceName`	—
`VolumeName`	—
`DiffVolume`	—

Event ID 5146 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 5146 — Move of the Cluster Shared Volume resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Move of the Cluster Shared Volume resource '%1' is vetoed because one of the volumes belonging to the resource is in dismounted state. Please retry the action after the dismount operation is completed.

Fields

Name	Description
`ResourceName`	—

Event ID 5147 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 5147 — Move of the Cluster Shared Volume resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Move of the Cluster Shared Volume resource '%1' is vetoed because a snapshot is being created on one of the volumes belonging to the resource. Please retry the action after the snapshot creation is completed.

Fields

Name	Description
`ResourceName`	—

Event ID 5148 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 5148 — Move of the Cluster Shared Volume resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Move of the Cluster Shared Volume resource '%1' is vetoed because an IO mode change operation (Direct IO to Redirected IO or vice versa) is in progress on one of the volumes belonging to the resource. Please retry the action after the operation is completed.

Fields

Name	Description
`ResourceName`	—

Event ID 5149 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`CacheSizeInMb`	—

Event ID 5149 — Cache size resized to '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cache size resized to '%1' based on populated memory, user setsize is too high.

Fields

Name	Description
`CacheSizeInMb`	—

Event ID 5150 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`FailureReason`	—

Event ID 5150 — Cluster physical disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster physical disk resource '%1' failed.  The Cluster Shared Volume was put in failed state with the following error: '%2'

Fields

Name	Description
`ResourceName`	—
`FailureReason`	—

Event ID 5151 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume '%1' (resource '%2') transitioned to state '%3' as part of processing '%4' initiated by node '%5' with sequence number '%6'.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`VolumeState`	—
`Action`	—
`OriginatingNode`	—
`SequenceNumber`	—

Event ID 5152 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume '%1' (resource '%2') was unable to complete a  state transition. This was likely caused as part of processing '%4' with sequence number '%5' on nodes ('%3'). Cluster will attempt to create live dumps on the nodes.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`NodeNames`	—
`Action`	—
`SequenceNumber`	—

Event ID 5153 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume '%1' (resource '%2') received event '%3' with sequence number '%4' which originated in node '%5'.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`Event`	—
`SequenceNumber`	—
`OriginatingNode`	—

Event ID 5154 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume '%1' (resource '%2') completed processing event '%3' with sequence number '%4' which originated in node '%5'.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`Event`	—
`SequenceNumber`	—
`OriginatingNode`	—

Event ID 5155 — Cluster Shared Volume resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Shared Volume resource '%1' completed processing request '%2' with sequence number '%3'. The slowest node was '%4', which took %5 seconds.

Fields

Name	Description
`ResourceName`	—
`Action`	—
`SequenceNumber`	—
`Node`	—
`TimeTaken`	—

Event ID 5156 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`ErrorCode`	—

Event ID 5156 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Shared Volume '%1' ('%2') has entered a paused state because of '%3'. This error is encountered when the volsnap snapshots underlying the CSV volume are deleted outside of a user request. Possible causes of the snapshots getting deleted are lack of space in the volume for the snapshots to grow, or IO failure while trying to update the snapshot data. All I/O will temporarily be queued until the snapshot state is synchronized with volsnap.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`ErrorCode`	—

Event ID 5157 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`ErrorCode`	—

Event ID 5157 — Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Shared Volume '%1' ('%2') has entered a paused state because of '%3'. All I/O will temporarily be queued until a path to the volume is reestablished. This error is usually caused by an infrastructure failure. For example, losing connectivity to storage or the node owning the Cluster Shared Volume being removed from active cluster membership.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`ErrorCode`	—

Event ID 5158 — SMB client connection to server '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

SMB client connection to server '%1' (node '%2') on instance '%3' was explicitly disconnected because %4. This will result in all outstanding IO to that server to fail immediately. This is a fast-fail mechanism to recover from IOs that are stuck in a connection which is no longer responsive.

Fields

Name	Description
`ServerName`	—
`Node`	—
`SMBInstance`	—
`Reason`	—

Event ID 5159 — SMB client connection from source address '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

SMB client connection from source address '%1' to destination address '%2' for server '%3' (node '%4') on instance '%5' was explicitly disconnected because %6. This will result in all outstanding IO on that connection to fail immediately. This is a fast-fail mechanism to recover from IOs that are stuck in a connection which is no longer responsive.

Fields

Name	Description
`SourceAddress`	—
`DestAddress`	—
`ServerName`	—
`Node`	—
`SMBInstance`	—
`Reason`	—

Event ID 5160 — SMB client disconnect state for connection to server '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

SMB client disconnect state for connection to server '%1' (node '%2') on instance '%3' was cleared. This will restore the connection to a healthy state, and SMB client will no longer fail IO on that connection.

Fields

Name	Description
`ServerName`	—
`Node`	—
`SMBInstance`	—

Event ID 5161 — The volume name '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The volume name '%1' was removed because the underlying disk partition for resource '%2' no longer contains a recognizable file system. This volume name may be re-used by cluster in the future.

Fields

Name	Description
`VolumeName`	—
`Resource`	—

Event ID 5162 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 5162 — Move of the Cluster Shared Volume resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Move of the Cluster Shared Volume resource '%1' is vetoed because there is a Data Integrity Scan is in progress on one of the volumes belonging to the resource. Please retry the action after the operation is completed.

Fields

Name	Description
`ResourceName`	—

Event ID 5163 — Cluster service disabled RDMA on the SMB instance for %1 IO on this node.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster service disabled RDMA on the SMB instance for %1 IO on this node. All IO for this instance will now go over TCP connections only.

Fields

Name	Description
`SMBInstanceName`	—

Event ID 5164 — Cluster service enabled RDMA on the SMB instance for %1 IO on this node.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster service enabled RDMA on the SMB instance for %1 IO on this node.

Fields

Name	Description
`SMBInstanceName`	—

Event ID 5200 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 5200 — Cluster service failed to create a cluster identity token for Cluster Shared Volumes.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to create a cluster identity token for Cluster Shared Volumes. The error code was '%1'. Ensure the domain controller is accessible and check for connectivity issues. Until connection to the domain controller is recovered, some operations on this node against the Cluster Shared Volumes might fail.

Fields

Name	Description
`Status`	—

Event ID 5216 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`ErrorCode`	—

Event ID 5216 — Software snapshot creation on Cluster Shared Volume '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Software snapshot creation on Cluster Shared Volume '%1' ('%2') failed with error %3. The resource must be online to support snapshot creation. Please check the state of the resource.

Fields

Name	Description
`VolumeName`	—
`ResourceName`	—
`ErrorCode`	—

Event ID 5217 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeNames`	—
`SnapshotSet`	—
`ErrorCode`	—

Event ID 5217 — Software snapshot creation on Cluster Shared Volume(s) ('%1') with snapshot set id '%2' failed with error '%3'.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Software snapshot creation on Cluster Shared Volume(s) ('%1') with snapshot set id '%2' failed with error '%3'. Please check the state of the CSV resources and the system events of the resource owner nodes.

Fields

Name	Description
`VolumeNames`	—
`SnapshotSet`	—
`ErrorCode`	—

Event ID 5218 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`VolumeName`	—
`SnapshotAgeLimit`	—
`SnapshotId`	—
`SnapshotOriginNode`	—
`SnapshotDateTime`	—

Event ID 5218 — Cluster physical disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster physical disk resource '%1' deleted a software snapshot. The software snapshot on Cluster Shared Volume '%2' was deleted because it was older than '%3' day(s). The snapshot ID was '%4' and it was created from node '%5' at '%6'. It is expected that snapshots are deleted by a backup application after a backup job is completed.  This snapshot exceeded the time that is expected for a snapshot to exist. Verify with the backup application that backup jobs are completing successfully.

Fields

Name	Description
`ResourceName`	—
`VolumeName`	—
`SnapshotAgeLimit`	—
`SnapshotId`	—
`SnapshotOriginNode`	—
`SnapshotDateTime`	—

Event ID 5219 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ErrorCode`	—

Event ID 5219 — Cluster service failed to register the Cluster Shared Volumes snapshot provider with the Volume Shadow Service (VSS).

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster service failed to register the Cluster Shared Volumes snapshot provider with the Volume Shadow Service (VSS). This may be due to the VSS service shutting down or may be a problem with the VSS service having a problem that causes it to not accept incoming requests. 

Error: %1

Fields

Name	Description
`ErrorCode`	—

Event ID 5220 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResiliencyName`	—

Event ID 5220 — Cluster Service detected the fault domain settings may not be configured optimally.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster Service detected the fault domain settings may not be configured optimally. The current settings could result in reduced storage resiliency. 

Current Resiliency Level: %1

Fields

Name	Description
`ResiliencyName`	—

Event ID 5235 — Task '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Task '%1' is successfully registered.

Fields

Name	Description
`TaskName`	—

Event ID 5237 — Task '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Task '%1' is successfully changed.

Fields

Name	Description
`TaskName`	—

Event ID 5245 — Task '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Task '%1' is successfully deleted.

Fields

Name	Description
`TaskName`	—

Event ID 5264 — Physical Disk resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Physical Disk resource '%1' has been disconnected from this node.

Fields

Name	Description
`DeviceName`	—

Event ID 5265 — Cluster network '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network '%1' is down because the network interfaces connected to it are not operational. Cluster network '%1' is configured such that cluster communication is not allowed; however, if this failure is unexpected, run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Fields

Name	Description
`NetworkName`	—

Event ID 5266 — Cluster network interface '.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster network interface '%1' for cluster node '%2' on network '%3' is not operational. Network '%3' is configured such that cluster communication is not allowed; however, if this failure is unexpected, run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Fields

Name	Description
`InterfaceName`	—
`NodeName`	—
`NetworkName`	—

Event ID 5267 — ClusterMrr API request timed out because some nodes did not reply to the request within the specified time.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

ClusterMrr API request timed out because some nodes did not reply to the request within the specified time.

Component: %1
TimeoutInSeconds: %2
StragglerNodes: %3

Fields

Name	Description
`ComponentName`	—
`TimeoutInSeconds`	—
`NodeName`	—

Event ID 5268 — Too many ClusterMrr API requests are outstanding on this node.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Too many ClusterMrr API requests are outstanding on this node. If the number of requests is very high, then the applications that are generating such requests should be investigated. If the rate of requests being processed is low, the component listed below should be investigated.

Component: %1
RequestsBeingProcessed: %2
RequestsWaitingToBeProcessed: %3
RequestsReceivedInLastInterval: %4
RequestsProcessesedInLastInterval: %5
LastIntervalTimeInSeconds: %6
AverageRequestsProcessedPerSecond: %7

Fields

Name	Description
`ComponentName`	—
`RequestsBeingProcessed`	—
`RequestsWaitingToBeProcessed`	—
`ReceivedRequests`	—
`ProcessedRequests`	—
`RequestInterval`	—
`ProcessingRate`	—

Event ID 5269 — ClusterMrr API request handler timed out on this node.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

ClusterMrr API request handler timed out on this node. 

MessageDescription: %1
MessageAction: %2
Component: %3
TimeoutInSeconds: %4

Fields

Name	Description
`MessageDescription`	—
`MessageAction`	—
`ComponentName`	—
`TimeoutInSeconds`	—

Event ID 5377 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`OperationName`	—
`ThresholdTimeInSec`	—

Event ID 5377 — An internal Cluster service operation exceeded the defined threshold of '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

An internal Cluster service operation exceeded the defined threshold of '%2' seconds. The Cluster service has been terminated to recover. Service Control Manager will restart the Cluster service and the node will rejoin the cluster.

Fields

Name	Description
`OperationName`	—
`ThresholdTimeInSec`	—

Event ID 5393 — The Cluster detected that this node is slower than others and degrade Cluster performance.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

The Cluster detected that this node is slower than others and degrade Cluster performance. If the condition persists, check for hardware or software errors related to this node. To avoid repeated events it is supress for 24 hours unless the Cluster service is restarted.

Fields

Name	Description
`SlowOperations`	—
`TotalOperations`	—
`TimeFrameInSec`	—

Event ID 5394 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 5394 — The Cluster service encountered some storage errors while trying to bring storage pool online.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service encountered some storage errors while trying to bring storage pool online. Run cluster storage validation to troubleshoot the issue.

Fields

Name	Description
`ResourceName`	—

Event ID 5395 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`GroupName`	—
`NodeName`	—

Event ID 5395 — Cluster is moving the group for storage pool '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster is moving the group for storage pool '%1' because current node '%3' does not have optimal connectivity to the storage pool physical disks.

Fields

Name	Description
`ResourceName`	—
`GroupName`	—
`NodeName`	—

Event ID 5396 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 5396 — The Cluster service on this node is shutting down because it has detected that there are other cluster nodes that have quorum.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The Cluster service on this node is shutting down because it has detected that there are other cluster nodes that have quorum. This occurs when the Cluster service detects another node that was started with the Force Quorum switch (/fq).  The node which was started with the Force Quorum Switch will remain running.  Use Failover Cluster Manager to verify that this node automatically joined the cluster when the cluster service restarted.

Event ID 5397 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—
`AccountName`	—

Event ID 5397 — The cluster resource '.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster resource '%1' could not create or modify the replicated local user account '%2' on this node. Check the cluster logs for more information.

Fields

Name	Description
`ResourceName`	—
`AccountName`	—

Event ID 5398 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`RequiredVotes`	—
`RunningVotes`	—
`NodesWithWeight`	—

Event ID 5398 — Cluster failed to start.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Cluster failed to start. The latest copy of cluster configuration data was not available within the set of nodes attempting to start the cluster. Changes to the cluster occurred while the set of nodes were not in membership and as a result were not able to receive configuration data updates. .

Votes required to start cluster: %1
Votes available: %2
Nodes with votes: %3

Guidance:
Attempt to start the cluster service on all nodes in the cluster so that nodes with the latest copy of the cluster configuration data can first form the cluster. The cluster will be able to start and the nodes will automatically obtain the updated cluster configuration data. If there are no nodes available with the latest copy of the cluster configuration data, run the 'Start-ClusterNode -FQ' Windows PowerShell cmdlet. Using the ForceQuorum (FQ) parameter will start the cluster service and mark this node's copy of the cluster configuration data to be authoritative.  Forcing quorum on a node with an outdated copy of the cluster database may result in cluster configuration changes that occurred while the node was not participating in the cluster to be lost.

Fields

Name	Description
`RequiredVotes`	—
`RunningVotes`	—
`NodesWithWeight`	—

Event ID 5399 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 5399 —

Provider: Microsoft-Windows-FailoverClustering
Channel: DiagnosticVerbose

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 5400 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 5400 —

Provider: Microsoft-Windows-FailoverClustering
Channel: DiagnosticVerbose

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 5401 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 5401 —

Provider: Microsoft-Windows-FailoverClustering
Channel: DiagnosticVerbose

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 5408 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 5408 —

Provider: Microsoft-Windows-FailoverClustering
Channel: DiagnosticVerbose

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 5409 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 5409 —

Provider: Microsoft-Windows-FailoverClustering
Channel: ClusterSetDiagnostic

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 5410 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 5410 —

Provider: Microsoft-Windows-FailoverClustering
Channel: ClusterSetDiagnostic

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 5411 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 5411 —

Provider: Microsoft-Windows-FailoverClustering
Channel: ClusterSetDiagnostic

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 5412 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`LogString`	—

Event ID 5412 —

Provider: Microsoft-Windows-FailoverClustering
Channel: ClusterSetDiagnostic

Message

%1

Fields

Name	Description
`LogString`	—

Event ID 5413 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Event ID 5413 — The cluster has cold started.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

The cluster has cold started.

Event ID 5414 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`ResourceName`	—

Event ID 5414 — Failed to create the clustered role ".

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Failed to create the clustered role "%1" because Azure Stack HCI is out of policy. Azure Stack HCI requires an Azure subscription and needs to regularly connect to the cloud. Register now or troubleshoot your connection. See aka.ms/register-hci for more information.

Fields

Name	Description
`ResourceName`	—

Event ID 5415 — Group is about to move to new owner.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Group is about to move to new owner. GroupName:%1, GroupId:%2, CurrentOwner:%3, NewOwner:%4, Reason:%5

Fields

Name	Description
`GroupName`	—
`GroupId`	—
`CurrentOwner`	—
`NewOwner`	—
`Reason`	—

Event ID 5416 — Property change has occured.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Property change has occured. ObjectName:%1, ObjectId: %2, Reason:%3, Changes:%4

Fields

Name	Description
`ObjectName`	—
`ObjectId`	—
`Reason`	—
`Changes`	—

Event ID 5417 — Cluster Service has terminated due to a fatal error.

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Message

Cluster Service has terminated due to a fatal error. Error Message: %1, Error Code: %2

Fields

Name	Description
`ErrorMessage`	—
`ErrorCode`	—

Event ID 5424 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`HandleType`	—
`RpcError`	—
`ClusterError`	—

Event ID 5424 — Clusapi handle of type %1 has been marked as dead.

Provider: Microsoft-Windows-FailoverClustering
Channel: System

Message

Clusapi handle of type %1 has been marked as dead. RPC Error %2, Cluster Error %3.

Fields

Name	Description
`HandleType`	—
`RpcError`	—
`ClusterError`	—

Event ID 43968 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeId`	—
`VolumeNumber`	—
`MappedPath`	—
`TargetPath`	—

Event ID 43968 — Volume %1 activating.

Provider: Microsoft-Windows-FailoverClustering
Channel: Performance-CSV

Message

Volume %1 activating

Fields

Name	Description
`VolumeId`	—
`VolumeNumber`	—
`MappedPath`	—
`TargetPath`	—

Event ID 43969 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`VolumeId`	—

Event ID 43969 — Volume %1 deactivating.

Provider: Microsoft-Windows-FailoverClustering
Channel: Performance-CSV

Message

Volume %1 deactivating

Fields

Name	Description
`VolumeId`	—

Event ID 43970 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`IoId`	—
`IrpMajorFunction`	—
`FileContext`	—
`Size`	—
`IrpMinorFunction`	—
`FileObject`	—
`ShadowFileObject`	—

Event ID 43970 — IO %1 is of type %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Performance-CSV

Message

IO %1 is of type %2

Fields

Name	Description
`IoId`	—
`IrpMajorFunction`	—
`FileContext`	—
`Size`	—
`IrpMinorFunction`	—
`FileObject`	—
`ShadowFileObject`	—

Event ID 43971 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`IoId`	—
`State`	—

Event ID 43971 — IO %1 now in state %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Performance-CSV

Message

IO %1 now in state %2

Fields

Name	Description
`IoId`	—
`State`	—

Event ID 43972 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`FileId`	—
`VolumeId`	—
`Name`	—

Event ID 43972 — fsContext %1 opened for file %3.

Provider: Microsoft-Windows-FailoverClustering
Channel: Performance-CSV

Message

fsContext %1 opened for file %3

Fields

Name	Description
`FileId`	—
`VolumeId`	—
`Name`	—

Event ID 43973 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`FileId`	—

Event ID 43973 — fsContext %1 closed.

Provider: Microsoft-Windows-FailoverClustering
Channel: Performance-CSV

Message

fsContext %1 closed

Fields

Name	Description
`FileId`	—

Event ID 43974 —

Provider: Microsoft-Windows-FailoverClustering
Channel: Operational

Fields

Name	Description
`FileId`	—
`State`	—

Event ID 43974 — fsContext %1 is in state %2.

Provider: Microsoft-Windows-FailoverClustering
Channel: Performance-CSV

Message

fsContext %1 is in state %2

Fields

Name	Description
`FileId`	—
`State`	—