Microsoft-Windows-FailoverClustering-NetFt

354 events across 2 channels

Event IDTitleChannel
0Operational
0[AdpCreateAdapter] Invalid Adapter TypeVerbose
1Operational
1[AdpCreateAdapter] Invalid Adapter Object sizeVerbose
2Operational
2[AdpCreateAdapter] AdpInsertAdapterTable failedVerbose
3Operational
3[AdpCreateAdapter] AdapterInitialize failedVerbose
4Operational
4[AdpCreateAdapter] NetftAcquireIoRemoveLock failedVerbose
5Operational
5[AdpCreateAdapter] Failed to allocate memoryVerbose
6Operational
6Created Adapter of type %1 adapter %2.Verbose
7Operational
7Deleted Adapter of type %1 adapter %2.Verbose
8Operational
8Monitor %1 (%3 - %5) being marked for special HB.Verbose
9Operational
9Device %1 is processing Irp %2 (%3).Verbose
10Operational
10Device %1 is failed Irp %2 (%3) with %4.Verbose
11Operational
11Created device object %1 (handle %2) with %3.Verbose
12Operational
12Deleted device object %1 (handle %2).Verbose
13Operational
13Event \KernelObjects\Cluster.Verbose
14Operational
14Failed to create \KernelObjects\Cluster.Verbose
15Operational
15[ProcessNotifyRoutine] : Cluster service PID %1 is terminating.Verbose
16Operational
16Failed to open a tunnel adapter bound to address %2 with error %3.Verbose
17Operational
17Failed to allocate memory while creating a tunnel record.Verbose
18Operational
18[NetftDispatchAddRoute] Route already existsVerbose
19Operational
19[NetftDispatchAddRoute] ExtensionSize calculation returned status %1.Verbose
20Operational
20[RegisterClusterService] : Cluster service is already registered.Verbose
21Operational
21[RegisterClusterService] : Cluster service PID is %1.Verbose
22Operational
22[NetftSweepRdbWorkerRoutine] : Routes associated with context %1 will be deleted …Verbose
23Operational
23[NetftSweepRdbWorkerRoutine] : Route cleanup timer firedVerbose
24Operational
24[NetftSweepRdbWorkerRoutine] : Route cleanup event signaledVerbose
25Operational
25[ClusterServicePreTerminate] : Cluster service PID is %p is about to go down.Verbose
26Operational
26[ClusterServicePreTerminate]: Deleting routes associated with calling context.Verbose
27Operational
27[ClusterServicePreTerminate]: Couldn't schedule route cleanup.Verbose
28Operational
28[WerCaptureLiveKernelDumpAddSecondaryData] : Adding resource type to secondary …Verbose
29Operational
29[WerCaptureLiveKernelDumpAddSecondaryData] : Secondary data %1; Size 0x%2; …Verbose
30Operational
30[WerCaptureLiveKernelDump] : Live dump collection is disabled.Verbose
31Operational
31[WerCaptureLiveKernelDump] : Live dump collection is throttled.Verbose
32Operational
32[WerCaptureLiveKernelDump] Threshold time is not met.Verbose
33Operational
33[NetftDispatchSetLiveDumpPolicy] : Live dump policy = %1.Verbose
34Operational
34[NetftDispatchSetOperationalVersion] : Operational Version = %1.Verbose
35Operational
35[NetftIssueEvent] Failed to allocate entry for %1 event.Verbose
36Operational
36[NetftIssueEvent] Invalid event type specified (%1 event).Verbose
37Operational
37Starvation threshold reached.Verbose
38Operational
38Pending event IRP %1 is being cancelled.Verbose
39Operational
39-----------------------------+ LOG BEGIN +-----------------------------Verbose
40Operational
40Driver %p is loading, registry path %S.Verbose
41Operational
41Driver %p failed to register with ETW (status %x).Verbose
42Operational
42Driver %p failed initialization with %xVerbose
43Operational
43Miniport adapter %1 failed to query permanent data link address.Verbose
44Operational
44MaInitializeAdapter: Creating MiniportCounterSet instance '.Verbose
45Operational
45[DROP] MaSendPackets - Tcb creation failed, adapter %1.Verbose
46Operational
46[DROP] MaSendPackets - Adapter %1 is not active.Verbose
47Operational
47NetBufferList %1 with %2 NetBuffers completed send with error %3.Verbose
48Operational
48MaStatus: Miniport adapter %1 signals connect.Verbose
49Operational
49MaStatus: Miniport adapter %1 signals disconnect.Verbose
50Operational
50[DROP] MaReceivePacket - Adapter %p is not activeVerbose
51Operational
51Received a split packet of size %1, split at byte %2.Verbose
52Operational
52Generated data link address %1.Verbose
53Operational
53Searching for registered data link address at interface index %1, type %2, oper …Verbose
54Operational
54Using registered data link address %1.Verbose
55Operational
55Found data link address collision with physical address on interface index %1, …Verbose
56Operational
56Found data link address collision with permanentphysical address on interface …Verbose
57Operational
57Successfully generated data link address %1.Verbose
58Operational
58[DROP] MaBuildTcbChain - Send from %2 to %4 failed RdbLookupActiveRoute.Verbose
59Operational
59[DROP] MaBuildTcbChain - Send from %2 to %4 failed NetftParsePacket failed with …Verbose
60Operational
60Initializing NDIS miniport %1.Verbose
61Operational
61Initialized NDIS miniport %1.Verbose
62Operational
62Initialize NDIS miniport %1 failed with %2.Verbose
63Operational
63Miniport adapter %1 halted.Verbose
64Operational
64NDIS attempted to cancel send operation.Verbose
65Operational
65Driver %1 unloaded.Verbose
66Operational
66Interface %1 was inserted into the system.Verbose
67Operational
67Interface %1 was removed from the system.Verbose
68Operational
68nconsistent route count.Verbose
69Operational
69[RmInitializeAdapter] no valid configuration.Verbose
70Operational
70[RmInitializeAdapter] Heartbeat parameters are not valid.Verbose
71Operational
71[RmInitializeAdapter] RmCreateSecurityContext failed.Verbose
72Operational
72[RmInitializeAdapter] TotalMessage Size is too large %1.Verbose
73Operational
73[RmInitializeAdapter] NdisAllocateMemoryWithTag failed with %1.Verbose
74Operational
74[RmInitializeAdapter] NdisAllocateNetBufferListPool failed with %1.Verbose
75Operational
75[RmInitializeAdapter] AdpOpenTunnelAdapter returned %1.Verbose
76Operational
76Monitor %1 started HB from %3 to %5 with delay %6 and threshold %7.Verbose
77Operational
77RmCreateCounterSet: Creating RouteMonitorCounterSet instance '.Verbose
78Operational
78Monitor %1 forced the endpoint %3 to be unreachable.Verbose
79Operational
79Monitor %1 stopped HB to %3.Verbose
80Operational
80Monitor %1 (%3 - %5) missed two-fifth consecutive HB response.Verbose
81Operational
81Monitor %1 (%3 - %5) reached HB threshold, remote endpoint %5 is unreachable.Verbose
82Operational
82Monitor %1 (%3 - %5) missed HB response, gap=%6.Verbose
83Operational
83Monitor %1 routine RmHeartbeatTimerDpc took too long to complete.Verbose
84Operational
84Monitor %1 (%3 - %5) sending RCP stop adapter request %6 (sequence %7).Verbose
85Operational
85[DROP] RmSendPackets - Tcb Creation Failed for RmAdapter %1.Verbose
86Operational
86[DROP] RmSendPackets - Could not find TunnelAdapter for RmAdapter %1.Verbose
87Operational
87Monitor %1 routine RmSendPackets took too long to complete.Verbose
88Operational
88Switched tunnel for this RMA from %2 to %4.Verbose
89Operational
89Monitor %1 routine RmSendComplete took too long to complete.Verbose
90Operational
90[DROP] Monitor %1 (%3 - %5) Ignoring incomming heartbeat.Verbose
91Operational
91Monitor %1 (%3 - %5) received RCP request special %6 (sequence %7).Verbose
92Operational
92Monitor %1 (%3 - %5) received RCP request adapter stopping %6 (sequence %7).Verbose
93Operational
93[DROP] Monitor %1 (%3 - %5) received unsupported RCP message %6 (type %7).Verbose
94Operational
94[DROP] Monitor %1 (%3 - %5) RmParseRcpPacket failed message %6\n).Verbose
95Operational
95Monitor %1 routine RmReceivePacket took too long to complete.Verbose
96Operational
96Monitor adapter %1 signals media connect.Verbose
97Operational
97Monitor adapter %1 signals media disconnect.Verbose
98Operational
98Monitor %1 was disconnected, remote endpoint %3 is unreachable.Verbose
99Operational
99Monitor adapter %1 signals status change %2.Verbose
100Operational
100Monitor %1 (%3 - %5) failed to sign RCP message with %6.Verbose
101Operational
101Monitor %1 detected that remote endpoint %3 is reachable.Verbose
102Operational
102Monitor %1 routine RmProcessRcpRequest took too long to complete.Verbose
103Operational
103Failed to invalidate ARP cache.Verbose
104Operational
104Failed to invalidate neighbor cache.Verbose
105Operational
105Failed to invalidate neighbor cache fault-tolerant adapter not found.Verbose
106Operational
106Monitor %1 routine RmpUpdateNeighborEntries took too long to complete.Verbose
107Operational
107[RmStoreHeartbeatRecord] Monitor %1 (%3 - %5) MissedHBCount is already 0.Verbose
108Operational
108[RmStoreHeartbeatRecord] Monitor %1 (%3 - %5) MissedHBCount = %6, Error = %7.Verbose
109Operational
109[RmHandleHeartbeatResponse] Monitor %1 (%3 - %5) MissedHBCount is already 0.Verbose
110Operational
110Failed to allocate neighbor update work itemVerbose
111Operational
111Validation of RCP packet failed - Packet too small (%1 bytes).Verbose
112Operational
112Validation of RCP packet failed - Bad message type.Verbose
113Operational
113Validation of RCP packet failed - Bad version.Verbose
114Operational
114Validation of RCP packet failed - Invalid reserved value.Verbose
115Operational
115Validation of RCP packet failed - Invalid extension header order.Verbose
116Operational
116Validation of RCP packet failed - Invalid IPv4 address pair.Verbose
117Operational
117Validation of RCP packet failed - Invalid IPv6 address pair.Verbose
118Operational
118Validation of RCP packet failed - Invalid address pair extension header.Verbose
119Operational
119Validation of RCP packet failed - Invalid signature buffer.Verbose
120Operational
120Validation of RCP packet failed - Invalid signature extension header.Verbose
121Operational
121Validation of RCP packet failed - Monitor %1 failed to verify signature (%2).Verbose
122Operational
122Validation of RCP packet failed - Missing signature extension header.Verbose
123Operational
123Validation of RCP packet failed - Route monitor (%2 - %4) FT IPs (%6 - %8) not …Verbose
124Operational
124Validation of RCP packet failed - Invalid RCP header.Verbose
125Operational
125Error in RmParseRcpPacketForLRR, could not retrieve packet in contiguous buffer …Verbose
126Operational
126Reference process object (ID 0x%1, handle 0x%2) by handle failed with %3.Verbose
127Operational
127Open client process (ID 0x%1) failed with %2.Verbose
128Operational
128Close client process (handle 0x%1) failed with %2.Verbose
129Operational
129TaInitializeAdapter: Creating TunnelCounterSet instance '.Verbose
130Operational
130TaDeInitializeAdapter: Releasing Endpoint TunnelCounterSet instance '.Verbose
131Operational
131[DROP] TaSendTcb - Adapter %1 not ready to send to %3.Verbose
132Operational
132[DROP] TaReceivePacket - Receive from %2 to %4 failed TaFilterPacket.Verbose
133Operational
133Tunnel adapter %1 signals media connect.Verbose
134Operational
134Tunnel adapter %1 signals media disconnect.Verbose
135Operational
135Tunnel adapter %1 signals status change %2.Verbose
136Operational
136[DROP] Dropping received RCP messages from %2.Verbose
137Operational
137[DROP] Dropping received RCP messages from %2 invalid port number.Verbose
138Operational
138[DROP] TaFilterPacket Invalid Ethernet HeaderVerbose
139Operational
139[DROP] TaFilterPacket NetftInitializeDataBuffer failedVerbose
140Operational
140The client process (ID 0x%1) was terminated.Verbose
141Operational
141Watchdog timer timed out for the client process (ID 0x%1).Verbose
142Operational
142Watchdog timer timed out for the client process (ID 0x%1).Verbose
143Operational
143Tunnel adapter %1 bound to %3.Verbose
144Operational
144Tunnel adapter %1 failed to create socket %3 (status %4).Verbose
145Operational
145NetftEndpointCreateCounterSet: Creating WskCounterSet instance '.Verbose
146Operational
146[DROP] NetftSendDatagram - IoAllocateIrp failed when trying to send to %2.Verbose
147Operational
147[DROP] NetftSendDatagram - NdisAllocateFromNPagedLookasideList failed when …Verbose
148Operational
148[DROP] NetftReceiveDatagramHandler - AdpReferenceAdapterSafe failed (tunnel …Verbose
149Operational
149[DROP] NetftReceiveDatagramHandler - Tunnel adapter %1 is stopping.Verbose
150Operational
150[DROP] NetftReceiveDatagramHandler - Tunnel adapter %1 is not active.Verbose
151Operational
151[DROP] Underlying socket terminated by WSK provider (tunnel adapter %1).Verbose
152Operational
152[DROP] Tunnel adapter %1 failed to build datagram descriptor list.Verbose
153Operational
153Tunnel adapter %1 unbound from %3 with %4.Verbose
154Operational
154Tunnel adapter failed to allocate NBL.Verbose
155Operational
155[NetftQueryIfIndexByDataLinkddress] : NetftEnumerateInterfaces returned status …Verbose
156Operational
156[NetftIsFaultTolerantIpAddress] : AdpOpenMiniportAdapter returned status %1.Verbose
157Operational
157[NetftIsFaultTolerantIpAddress] : NetftQueryIfIndexByIpAddress returned status …Verbose
158Operational
158Insert %2 into interface %3 completed with %4.Verbose
159Operational
159Insert %2 into interface %3 completed with %4.Verbose
160Operational
160Remove %2 from interface %3 completed with %4.Verbose
161Operational
161Remove %2 from interface %3 completed with %4.Verbose
162Operational
162Failed to register address change handler with IPv4/802 providerVerbose
163Operational
163Failed to register address change handler with IPv6/802 providerVerbose
164Operational
164Failed to register media sense handler with NDIS providerVerbose
165Operational
165PnP signals %1 address change (%2).Verbose
166Operational
166Interface %1 signals address %3 IP DAD State change to %4.Verbose
167Operational
167Interface %1 signals address %3 IP DAD State change to %4.Verbose
168Operational
168PnP signals interface operational status changeVerbose
169Operational
169Interface %1 signals operational status %2.Verbose
4096Driver loaded.Operational
8192Watchdog Started.Operational
12288Watchdog Stopped.Operational
16384Watchdog Heartbeat Missed.Operational
20480Watchdog Fired.Operational
24576Watchdog Updated.Operational
28672Watchdog Orphaned.Operational
32768Watchdog Orphaned.Operational
36864Route added from %4 to %5 for context %1, ContextRouteCount: %6.Operational
40960Route from %4 to %5 deleted for context %1, ContextRouteCount: %6.Operational
45056Route cleanup scheduled for context %1, ContextRouteCount: %2, Source: %3.Operational
49152Livedump started.Operational
53248Livedump Completed.Operational
57344DPC Skew detected for Monitor %1.Operational

Event ID 0 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 0 — [AdpCreateAdapter] Invalid Adapter Type

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[AdpCreateAdapter] Invalid Adapter Type

Event ID 1 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 1 — [AdpCreateAdapter] Invalid Adapter Object size

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[AdpCreateAdapter] Invalid Adapter Object size

Event ID 2 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 2 — [AdpCreateAdapter] AdpInsertAdapterTable failed

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[AdpCreateAdapter] AdpInsertAdapterTable failed

Event ID 3 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 3 — [AdpCreateAdapter] AdapterInitialize failed

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[AdpCreateAdapter] AdapterInitialize failed

Event ID 4 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 4 — [AdpCreateAdapter] NetftAcquireIoRemoveLock failed

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[AdpCreateAdapter] NetftAcquireIoRemoveLock failed

Event ID 5 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 5 — [AdpCreateAdapter] Failed to allocate memory

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[AdpCreateAdapter] Failed to allocate memory

Event ID 6 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Type
Context

Event ID 6 — Created Adapter of type %1 adapter %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Created Adapter of type %1 adapter %2

Fields

NameDescription
Type
Context

Event ID 7 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Type
Context

Event ID 7 — Deleted Adapter of type %1 adapter %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Deleted Adapter of type %1 adapter %2

Fields

NameDescription
Type
Context

Event ID 8 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Context
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 8 — Monitor %1 (%3 - %5) being marked for special HB.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 (%3 - %5) being marked for special HB

Fields

NameDescription
Context
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 9 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
DeviceContext
IrpContext
MajorFunctionCode

Event ID 9 — Device %1 is processing Irp %2 (%3).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Device %1 is processing Irp %2 (%3)

Fields

NameDescription
DeviceContext
IrpContext
MajorFunctionCode

Event ID 10 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
DeviceContext
IrpContext
MajorFunctionCode
ErrorCode

Event ID 10 — Device %1 is failed Irp %2 (%3) with %4.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Device %1 is failed Irp %2 (%3) with %4

Fields

NameDescription
DeviceContext
IrpContext
MajorFunctionCode
ErrorCode

Event ID 11 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
DeviceContext
Handle
Status

Event ID 11 — Created device object %1 (handle %2) with %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Created device object %1 (handle %2) with %3

Fields

NameDescription
DeviceContext
Handle
Status

Event ID 12 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
DeviceContext
Handle

Event ID 12 — Deleted device object %1 (handle %2).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Deleted device object %1 (handle %2)

Fields

NameDescription
DeviceContext
Handle

Event ID 13 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 13 — Event \KernelObjects\Cluster.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Event \KernelObjects\Cluster.Service.Running.Event still exists. Trying to open existing event

Event ID 14 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 14 — Failed to create \KernelObjects\Cluster.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Failed to create \KernelObjects\Cluster.Service.Running.Event. %1

Fields

NameDescription
Status

Event ID 15 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
ProcessId

Event ID 15 — [ProcessNotifyRoutine] : Cluster service PID %1 is terminating.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[ProcessNotifyRoutine] : Cluster service PID %1 is terminating. Setting event

Fields

NameDescription
ProcessId

Event ID 16 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
LocalAddressIPLength
LocalAddress
Status

Event ID 16 — Failed to open a tunnel adapter bound to address %2 with error %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Failed to open a tunnel adapter bound to address %2 with error %3

Fields

NameDescription
LocalAddressIPLength
LocalAddress
Status

Event ID 17 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 17 — Failed to allocate memory while creating a tunnel record.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Failed to allocate memory while creating a tunnel record. Error = %1

Fields

NameDescription
Status

Event ID 18 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 18 — [NetftDispatchAddRoute] Route already exists

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftDispatchAddRoute] Route already exists

Event ID 19 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 19 — [NetftDispatchAddRoute] ExtensionSize calculation returned status %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftDispatchAddRoute] ExtensionSize calculation returned status %1

Fields

NameDescription
Status

Event ID 20 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
NewProcessId
CurProcessId
Status

Event ID 20 — [RegisterClusterService] : Cluster service is already registered.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RegisterClusterService] : Cluster service is already registered. Cluster service PID %1. Current process PID %2. %3

Fields

NameDescription
NewProcessId
CurProcessId
Status

Event ID 21 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
ProcessId

Event ID 21 — [RegisterClusterService] : Cluster service PID is %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RegisterClusterService] : Cluster service PID is %1. Resetting event

Fields

NameDescription
ProcessId

Event ID 22 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Context

Event ID 22 — [NetftSweepRdbWorkerRoutine] : Routes associated with context %1 will be deleted when the wait completes.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftSweepRdbWorkerRoutine] : Routes associated with context %1 will be deleted when the wait completes

Fields

NameDescription
Context

Event ID 23 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 23 — [NetftSweepRdbWorkerRoutine] : Route cleanup timer fired

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftSweepRdbWorkerRoutine] : Route cleanup timer fired

Event ID 24 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 24 — [NetftSweepRdbWorkerRoutine] : Route cleanup event signaled

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftSweepRdbWorkerRoutine] : Route cleanup event signaled

Event ID 25 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
ProcessId

Event ID 25 — [ClusterServicePreTerminate] : Cluster service PID is %p is about to go down.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[ClusterServicePreTerminate] : Cluster service PID is %p is about to go down.

Fields

NameDescription
ProcessId

Event ID 26 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 26 — [ClusterServicePreTerminate]: Deleting routes associated with calling context.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[ClusterServicePreTerminate]: Deleting routes associated with calling context.

Event ID 27 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 27 — [ClusterServicePreTerminate]: Couldn't schedule route cleanup.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[ClusterServicePreTerminate]: Couldn't schedule route cleanup. Deleting routes

Event ID 28 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
GUID
ReportType
Status

Event ID 28 — [WerCaptureLiveKernelDumpAddSecondaryData] : Adding resource type to secondary data %1 %2; Status %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[WerCaptureLiveKernelDumpAddSecondaryData] : Adding resource type to secondary data %1 %2; Status %3

Fields

NameDescription
GUID
ReportType
Status

Event ID 29 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
GUID
Size
Status

Event ID 29 — [WerCaptureLiveKernelDumpAddSecondaryData] : Secondary data %1; Size 0x%2; Status %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[WerCaptureLiveKernelDumpAddSecondaryData] : Secondary data %1; Size 0x%2; Status %3

Fields

NameDescription
GUID
Size
Status

Event ID 30 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
LiveDumpPolicy

Event ID 30 — [WerCaptureLiveKernelDump] : Live dump collection is disabled.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[WerCaptureLiveKernelDump] : Live dump collection is disabled. Current policy %1

Fields

NameDescription
LiveDumpPolicy

Event ID 31 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 31 — [WerCaptureLiveKernelDump] : Live dump collection is throttled.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[WerCaptureLiveKernelDump] : Live dump collection is throttled.

Event ID 32 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
ThresholdTime
Threshold
CurrentTime
TimeDeltaRemaining

Event ID 32 — [WerCaptureLiveKernelDump] Threshold time is not met.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[WerCaptureLiveKernelDump] Threshold time is not met. Threshold value %1, Threshold time %2, Current time %3, Remaining %4 x 100ns

Fields

NameDescription
ThresholdTime
Threshold
CurrentTime
TimeDeltaRemaining

Event ID 33 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
LiveDumpPolicy

Event ID 33 — [NetftDispatchSetLiveDumpPolicy] : Live dump policy = %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftDispatchSetLiveDumpPolicy] : Live dump policy = %1

Fields

NameDescription
LiveDumpPolicy

Event ID 34 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Version

Event ID 34 — [NetftDispatchSetOperationalVersion] : Operational Version = %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftDispatchSetOperationalVersion] : Operational Version =  %1

Fields

NameDescription
Version

Event ID 35 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EventType

Event ID 35 — [NetftIssueEvent] Failed to allocate entry for %1 event.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftIssueEvent] Failed to allocate entry for %1 event

Fields

NameDescription
EventType

Event ID 36 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EventType

Event ID 36 — [NetftIssueEvent] Invalid event type specified (%1 event).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftIssueEvent] Invalid event type specified (%1 event)

Fields

NameDescription
EventType

Event ID 37 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 37 — Starvation threshold reached.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Starvation threshold reached. Wait for event delivery terminated.

Event ID 38 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
IrpContext

Event ID 38 — Pending event IRP %1 is being cancelled.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Pending event IRP %1 is being cancelled.

Fields

NameDescription
IrpContext

Event ID 39 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 39 — -----------------------------+ LOG BEGIN +-----------------------------

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

-----------------------------+ LOG BEGIN +-----------------------------

Event ID 40 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Context
RegPath

Event ID 40 — Driver %p is loading, registry path %S.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Driver %p is loading, registry path %S.

Fields

NameDescription
Context
RegPath

Event ID 41 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Context
Status

Event ID 41 — Driver %p failed to register with ETW (status %x).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Driver %p failed to register with ETW (status %x).

Fields

NameDescription
Context
Status

Event ID 42 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Context
Status

Event ID 42 — Driver %p failed initialization with %x

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Driver %p failed initialization with %x

Fields

NameDescription
Context
Status

Event ID 43 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
AdapterContext

Event ID 43 — Miniport adapter %1 failed to query permanent data link address.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Miniport adapter %1 failed to query permanent data link address.

Fields

NameDescription
AdapterContext

Event ID 44 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Instance
Status

Event ID 44 — MaInitializeAdapter: Creating MiniportCounterSet instance '.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

MaInitializeAdapter: Creating MiniportCounterSet instance '%1' result %2

Fields

NameDescription
Instance
Status

Event ID 45 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
AdapterContext

Event ID 45 — [DROP] MaSendPackets - Tcb creation failed, adapter %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] MaSendPackets - Tcb creation failed, adapter %1.

Fields

NameDescription
AdapterContext

Event ID 46 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
AdapterContext

Event ID 46 — [DROP] MaSendPackets - Adapter %1 is not active.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] MaSendPackets - Adapter %1 is not active.

Fields

NameDescription
AdapterContext

Event ID 47 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
NBLContext
NLBCount
Status

Event ID 47 — NetBufferList %1 with %2 NetBuffers completed send with error %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

NetBufferList %1 with %2 NetBuffers completed send with error %3.

Fields

NameDescription
NBLContext
NLBCount
Status

Event ID 48 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
AdapterContext

Event ID 48 — MaStatus: Miniport adapter %1 signals connect.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

MaStatus: Miniport adapter %1 signals connect.

Fields

NameDescription
AdapterContext

Event ID 49 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
AdapterContext

Event ID 49 — MaStatus: Miniport adapter %1 signals disconnect.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

MaStatus: Miniport adapter %1 signals disconnect.

Fields

NameDescription
AdapterContext

Event ID 50 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
AdapterContext

Event ID 50 — [DROP] MaReceivePacket - Adapter %p is not active

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] MaReceivePacket - Adapter %p is not active

Fields

NameDescription
AdapterContext

Event ID 51 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Size
Offset

Event ID 51 — Received a split packet of size %1, split at byte %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Received a split packet of size %1, split at byte %2.

Fields

NameDescription
Size
Offset

Event ID 52 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Layer2Address

Event ID 52 — Generated data link address %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Generated data link address %1.

Fields

NameDescription
Layer2Address

Event ID 53 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
InterfaceIndex
InterfaceType
InterfaceStatus
Layer2Address

Event ID 53 — Searching for registered data link address at interface index %1, type %2, oper status %3, address %4.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Searching for registered data link address at interface index %1, type %2, oper status %3, address %4.

Fields

NameDescription
InterfaceIndex
InterfaceType
InterfaceStatus
Layer2Address

Event ID 54 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Instance

Event ID 54 — Using registered data link address %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Using registered data link address %1.

Fields

NameDescription
Instance

Event ID 55 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
InterfaceIndex
Layer2Address

Event ID 55 — Found data link address collision with physical address on interface index %1, address %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Found data link address collision with physical address on interface index %1, address %2.

Fields

NameDescription
InterfaceIndex
Layer2Address

Event ID 56 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
InterfaceIndex
Layer2Address

Event ID 56 — Found data link address collision with permanentphysical address on interface index %1, address %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Found data link address collision with permanentphysical address on interface index %1, address %2.

Fields

NameDescription
InterfaceIndex
Layer2Address

Event ID 57 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Layer2Address

Event ID 57 — Successfully generated data link address %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Successfully generated data link address %1.

Fields

NameDescription
Layer2Address

Event ID 58 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 58 — [DROP] MaBuildTcbChain - Send from %2 to %4 failed RdbLookupActiveRoute.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] MaBuildTcbChain - Send from %2 to %4 failed RdbLookupActiveRoute

Fields

NameDescription
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 59 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
Status

Event ID 59 — [DROP] MaBuildTcbChain - Send from %2 to %4 failed NetftParsePacket failed with %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] MaBuildTcbChain - Send from %2 to %4 failed NetftParsePacket failed with %3

Fields

NameDescription
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
Status

Event ID 60 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
AdapterHandle

Event ID 60 — Initializing NDIS miniport %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Initializing NDIS miniport %1

Fields

NameDescription
AdapterHandle

Event ID 61 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
AdapterHandle
AdapterContext

Event ID 61 — Initialized NDIS miniport %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Initialized NDIS miniport %1. (miniport adapter: %2)

Fields

NameDescription
AdapterHandle
AdapterContext

Event ID 62 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
AdapterHandle
Status

Event ID 62 — Initialize NDIS miniport %1 failed with %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Initialize NDIS miniport %1 failed with %2

Fields

NameDescription
AdapterHandle
Status

Event ID 63 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
AdapterContext

Event ID 63 — Miniport adapter %1 halted.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Miniport adapter %1 halted.

Fields

NameDescription
AdapterContext

Event ID 64 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 64 — NDIS attempted to cancel send operation.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

NDIS attempted to cancel send operation.

Event ID 65 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
DriverContext

Event ID 65 — Driver %1 unloaded.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Driver %1 unloaded.

Fields

NameDescription
DriverContext

Event ID 66 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
NetbiosName

Event ID 66 — Interface %1 was inserted into the system.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Interface %1 was inserted into the system.

Fields

NameDescription
NetbiosName

Event ID 67 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
NetbiosName

Event ID 67 — Interface %1 was removed from the system.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Interface %1 was removed from the system.

Fields

NameDescription
NetbiosName

Event ID 68 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
ExpectedCount
ActualCount

Event ID 68 — nconsistent route count.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

nconsistent route count. ContextRouteCount %1, Actual route count %2.

Fields

NameDescription
ExpectedCount
ActualCount

Event ID 69 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 69 — [RmInitializeAdapter] no valid configuration.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RmInitializeAdapter] no valid configuration. Status %1

Fields

NameDescription
Status

Event ID 70 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 70 — [RmInitializeAdapter] Heartbeat parameters are not valid.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RmInitializeAdapter] Heartbeat parameters are not valid. Status %1

Fields

NameDescription
Status

Event ID 71 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 71 — [RmInitializeAdapter] RmCreateSecurityContext failed.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RmInitializeAdapter] RmCreateSecurityContext failed. Status %1

Fields

NameDescription
Status

Event ID 72 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 72 — [RmInitializeAdapter] TotalMessage Size is too large %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RmInitializeAdapter] TotalMessage Size is too large %1

Fields

NameDescription
Status

Event ID 73 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 73 — [RmInitializeAdapter] NdisAllocateMemoryWithTag failed with %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RmInitializeAdapter] NdisAllocateMemoryWithTag failed with %1

Fields

NameDescription
Status

Event ID 74 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 74 — [RmInitializeAdapter] NdisAllocateNetBufferListPool failed with %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RmInitializeAdapter] NdisAllocateNetBufferListPool failed with %1

Fields

NameDescription
Status

Event ID 75 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 75 — [RmInitializeAdapter] AdpOpenTunnelAdapter returned %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RmInitializeAdapter] AdpOpenTunnelAdapter returned %1

Fields

NameDescription
Status

Event ID 76 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
Delay
Threshold
MinTicks
MaxTicks
Tickrate
CurrentCPU
TargetCPU

Event ID 76 — Monitor %1 started HB from %3 to %5 with delay %6 and threshold %7.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 started HB from %3 to %5 with delay %6 and threshold %7. [Min, Max] allowed delay = [%8, %9] ticks (@ %10 ticks per sec). CurrentProcessor=%11, DpcTargetProcessor=%12

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
Delay
Threshold
MinTicks
MaxTicks
Tickrate
CurrentCPU
TargetCPU

Event ID 77 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
Status

Event ID 77 — RmCreateCounterSet: Creating RouteMonitorCounterSet instance '.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

RmCreateCounterSet: Creating RouteMonitorCounterSet instance '%2 - %4' result %5

Fields

NameDescription
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
Status

Event ID 78 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
RemoteAddressIPLength
RemoteAddress

Event ID 78 — Monitor %1 forced the endpoint %3 to be unreachable.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 forced the endpoint %3 to be unreachable.

Fields

NameDescription
MonitorContext
RemoteAddressIPLength
RemoteAddress

Event ID 79 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
RemoteAddressIPLength
RemoteAddress

Event ID 79 — Monitor %1 stopped HB to %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 stopped HB to %3

Fields

NameDescription
MonitorContext
RemoteAddressIPLength
RemoteAddress

Event ID 80 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 80 — Monitor %1 (%3 - %5) missed two-fifth consecutive HB response.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 (%3 -  %5) missed two-fifth consecutive HB response

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 81 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
Counter
Threshold

Event ID 81 — Monitor %1 (%3 - %5) reached HB threshold, remote endpoint %5 is unreachable.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 (%3 -  %5) reached HB threshold, remote endpoint %5 is unreachable. Counter=%6, threshold=%7.

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
Counter
Threshold

Event ID 82 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
gap

Event ID 82 — Monitor %1 (%3 - %5) missed HB response, gap=%6.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 (%3 -  %5) missed HB response, gap=%6

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
gap

Event ID 83 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 83 — Monitor %1 routine RmHeartbeatTimerDpc took too long to complete.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 routine RmHeartbeatTimerDpc took too long to complete. Start=%2, end=%3, diff=%4

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 84 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
NBLContext
Sequence

Event ID 84 — Monitor %1 (%3 - %5) sending RCP stop adapter request %6 (sequence %7).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 (%3 -  %5) sending RCP stop adapter request %6 (sequence %7).

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
NBLContext
Sequence

Event ID 85 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext

Event ID 85 — [DROP] RmSendPackets - Tcb Creation Failed for RmAdapter %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] RmSendPackets - Tcb Creation Failed for RmAdapter %1

Fields

NameDescription
MonitorContext

Event ID 86 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext

Event ID 86 — [DROP] RmSendPackets - Could not find TunnelAdapter for RmAdapter %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] RmSendPackets - Could not find TunnelAdapter for RmAdapter %1

Fields

NameDescription
MonitorContext

Event ID 87 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 87 — Monitor %1 routine RmSendPackets took too long to complete.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 routine RmSendPackets took too long to complete. Start=%2, end=%3, diff=%4

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 88 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
OldTunnelAddressIPLength
OldTunnelAddress
NewTunnelAddressIPLength
NewTunnelAddress

Event ID 88 — Switched tunnel for this RMA from %2 to %4.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Switched tunnel for this RMA from %2 to %4

Fields

NameDescription
OldTunnelAddressIPLength
OldTunnelAddress
NewTunnelAddressIPLength
NewTunnelAddress

Event ID 89 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 89 — Monitor %1 routine RmSendComplete took too long to complete.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 routine RmSendComplete took too long to complete. Start=%2, end=%3, diff=%4

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 90 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
RouteBlocked
SpecialHBEnabled

Event ID 90 — [DROP] Monitor %1 (%3 - %5) Ignoring incomming heartbeat.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] Monitor %1 (%3 -  %5) Ignoring incomming heartbeat. Route blocked %6, SpecialHeartbeat %7.

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
RouteBlocked
SpecialHBEnabled

Event ID 91 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
NBLContext
Sequence

Event ID 91 — Monitor %1 (%3 - %5) received RCP request special %6 (sequence %7).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 (%3 -  %5) received RCP request special %6 (sequence %7)

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
NBLContext
Sequence

Event ID 92 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
NBLContext
Sequence

Event ID 92 — Monitor %1 (%3 - %5) received RCP request adapter stopping %6 (sequence %7).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 (%3 -  %5) received RCP request adapter stopping %6 (sequence %7)

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
NBLContext
Sequence

Event ID 93 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
NBLContext
MessageType

Event ID 93 — [DROP] Monitor %1 (%3 - %5) received unsupported RCP message %6 (type %7).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] Monitor %1 (%3 -  %5) received unsupported RCP message %6 (type %7)

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
NBLContext
MessageType

Event ID 94 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
NBLContext

Event ID 94 — [DROP] Monitor %1 (%3 - %5) RmParseRcpPacket failed message %6\n).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] Monitor %1 (%3 -  %5) RmParseRcpPacket failed message %6\n)

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
NBLContext

Event ID 95 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 95 — Monitor %1 routine RmReceivePacket took too long to complete.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 routine RmReceivePacket took too long to complete. Start=%2, end=%3, diff=%4

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 96 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext

Event ID 96 — Monitor adapter %1 signals media connect.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor adapter %1 signals media connect.

Fields

NameDescription
MonitorContext

Event ID 97 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext

Event ID 97 — Monitor adapter %1 signals media disconnect.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor adapter %1 signals media disconnect.

Fields

NameDescription
MonitorContext

Event ID 98 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
RemoteAddressIPLength
RemoteAddress

Event ID 98 — Monitor %1 was disconnected, remote endpoint %3 is unreachable.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 was disconnected, remote endpoint %3 is unreachable.

Fields

NameDescription
MonitorContext
RemoteAddressIPLength
RemoteAddress

Event ID 99 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
Status

Event ID 99 — Monitor adapter %1 signals status change %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor adapter %1 signals status change %2.

Fields

NameDescription
MonitorContext
Status

Event ID 100 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
Status

Event ID 100 — Monitor %1 (%3 - %5) failed to sign RCP message with %6.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 (%3 -  %5) failed to sign RCP message with %6

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
Status

Event ID 101 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
RemoteAddressIPLength
RemoteAddress

Event ID 101 — Monitor %1 detected that remote endpoint %3 is reachable.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 detected that remote endpoint %3 is reachable.

Fields

NameDescription
MonitorContext
RemoteAddressIPLength
RemoteAddress

Event ID 102 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 102 — Monitor %1 routine RmProcessRcpRequest took too long to complete.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 routine RmProcessRcpRequest took too long to complete. Start=%2, end=%3, diff=%4

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 103 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 103 — Failed to invalidate ARP cache.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Failed to invalidate ARP cache. Status %1

Fields

NameDescription
Status

Event ID 104 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 104 — Failed to invalidate neighbor cache.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Failed to invalidate neighbor cache. Status %1

Fields

NameDescription
Status

Event ID 105 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 105 — Failed to invalidate neighbor cache fault-tolerant adapter not found.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Failed to invalidate neighbor cache fault-tolerant adapter not found. Status %1

Fields

NameDescription
Status

Event ID 106 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 106 — Monitor %1 routine RmpUpdateNeighborEntries took too long to complete.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Monitor %1 routine RmpUpdateNeighborEntries took too long to complete. Start=%2, end=%3, diff=%4

Fields

NameDescription
MonitorContext
StartTicks
EndTicks
TickDelta

Event ID 107 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 107 — [RmStoreHeartbeatRecord] Monitor %1 (%3 - %5) MissedHBCount is already 0.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RmStoreHeartbeatRecord] Monitor %1 (%3 -  %5) MissedHBCount is already 0

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 108 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
MissedHBCount
Status

Event ID 108 — [RmStoreHeartbeatRecord] Monitor %1 (%3 - %5) MissedHBCount = %6, Error = %7.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RmStoreHeartbeatRecord] Monitor %1 (%3 -  %5) MissedHBCount = %6, Error = %7

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
MissedHBCount
Status

Event ID 109 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 109 — [RmHandleHeartbeatResponse] Monitor %1 (%3 - %5) MissedHBCount is already 0.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[RmHandleHeartbeatResponse] Monitor %1 (%3 -  %5) MissedHBCount is already 0

Fields

NameDescription
MonitorContext
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 110 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 110 — Failed to allocate neighbor update work item

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Failed to allocate neighbor update work item

Event ID 111 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
DataLength
RemoteAddressIPLength
RemoteAddress

Event ID 111 — Validation of RCP packet failed - Packet too small (%1 bytes).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Packet too small (%1 bytes). Sender: %3.

Fields

NameDescription
DataLength
RemoteAddressIPLength
RemoteAddress

Event ID 112 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Type
RemoteAddressIPLength
RemoteAddress

Event ID 112 — Validation of RCP packet failed - Bad message type.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Bad message type (%1). Sender: %3.

Fields

NameDescription
Type
RemoteAddressIPLength
RemoteAddress

Event ID 113 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Version
RemoteAddressIPLength
RemoteAddress

Event ID 113 — Validation of RCP packet failed - Bad version.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Bad version (%1). Sender: %3.

Fields

NameDescription
Version
RemoteAddressIPLength
RemoteAddress

Event ID 114 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Reserved
RemoteAddressIPLength
RemoteAddress

Event ID 114 — Validation of RCP packet failed - Invalid reserved value.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Invalid reserved value (%1). Sender: %3

Fields

NameDescription
Reserved
RemoteAddressIPLength
RemoteAddress

Event ID 115 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
NextHeader
RemoteAddressIPLength
RemoteAddress

Event ID 115 — Validation of RCP packet failed - Invalid extension header order.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Invalid extension header order (%1). Sender: %3

Fields

NameDescription
NextHeader
RemoteAddressIPLength
RemoteAddress

Event ID 116 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 116 — Validation of RCP packet failed - Invalid IPv4 address pair.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Invalid IPv4 address pair. Sender: %2

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 117 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 117 — Validation of RCP packet failed - Invalid IPv6 address pair.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Invalid IPv6 address pair. Sender: %2

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 118 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 118 — Validation of RCP packet failed - Invalid address pair extension header.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Invalid address pair extension header. Sender: %2

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 119 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 119 — Validation of RCP packet failed - Invalid signature buffer.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Invalid signature buffer. Sender: %2

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 120 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 120 — Validation of RCP packet failed - Invalid signature extension header.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Invalid signature extension header. Sender: %2

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 121 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
MonitorContext
Status
RemoteAddressIPLength
RemoteAddress

Event ID 121 — Validation of RCP packet failed - Monitor %1 failed to verify signature (%2).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Monitor %1 failed to verify signature (%2). Sender: %4

Fields

NameDescription
MonitorContext
Status
RemoteAddressIPLength
RemoteAddress

Event ID 122 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 122 — Validation of RCP packet failed - Missing signature extension header.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Missing signature extension header. Sender: %2

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 123 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
DestinationAddressIPLength
DestinationAddress
SourceAddressIPLength
SourceAddress

Event ID 123 — Validation of RCP packet failed - Route monitor (%2 - %4) FT IPs (%6 - %8) not found.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Route monitor (%2 -  %4) FT IPs (%6 -  %8) not found.

Fields

NameDescription
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress
DestinationAddressIPLength
DestinationAddress
SourceAddressIPLength
SourceAddress

Event ID 124 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 124 — Validation of RCP packet failed - Invalid RCP header.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Validation of RCP packet failed - Invalid RCP header. Sender: %2.

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 125 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
DataLength

Event ID 125 — Error in RmParseRcpPacketForLRR, could not retrieve packet in contiguous buffer %1 bytes.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Error in RmParseRcpPacketForLRR, could not retrieve packet in contiguous buffer %1 bytes.

Fields

NameDescription
DataLength

Event ID 126 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
ProcessID
Handle
Status

Event ID 126 — Reference process object (ID 0x%1, handle 0x%2) by handle failed with %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Reference process object (ID 0x%1, handle 0x%2) by handle failed with %3.

Fields

NameDescription
ProcessID
Handle
Status

Event ID 127 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
ProcessID
Status

Event ID 127 — Open client process (ID 0x%1) failed with %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Open client process (ID 0x%1) failed with %2.

Fields

NameDescription
ProcessID
Status

Event ID 128 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Handle
Status

Event ID 128 — Close client process (handle 0x%1) failed with %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Close client process (handle 0x%1) failed with %2.

Fields

NameDescription
Handle
Status

Event ID 129 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
Status

Event ID 129 — TaInitializeAdapter: Creating TunnelCounterSet instance '.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

TaInitializeAdapter: Creating TunnelCounterSet instance '%2' result %3

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
Status

Event ID 130 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress

Event ID 130 — TaDeInitializeAdapter: Releasing Endpoint TunnelCounterSet instance '.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

TaDeInitializeAdapter: Releasing Endpoint TunnelCounterSet instance '%2'

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress

Event ID 131 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Adapter
EndpointAddressIPLength
EndpointAddress

Event ID 131 — [DROP] TaSendTcb - Adapter %1 not ready to send to %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] TaSendTcb - Adapter %1 not ready to send to %3

Fields

NameDescription
Adapter
EndpointAddressIPLength
EndpointAddress

Event ID 132 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 132 — [DROP] TaReceivePacket - Receive from %2 to %4 failed TaFilterPacket.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] TaReceivePacket - Receive from %2 to %4 failed TaFilterPacket

Fields

NameDescription
LocalAddressIPLength
LocalAddress
RemoteAddressIPLength
RemoteAddress

Event ID 133 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Adapter

Event ID 133 — Tunnel adapter %1 signals media connect.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Tunnel adapter %1 signals media connect. \n

Fields

NameDescription
Adapter

Event ID 134 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Adapter

Event ID 134 — Tunnel adapter %1 signals media disconnect.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Tunnel adapter %1 signals media disconnect.\n

Fields

NameDescription
Adapter

Event ID 135 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Adapter
Status

Event ID 135 — Tunnel adapter %1 signals status change %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Tunnel adapter %1 signals status change %2.\n

Fields

NameDescription
Adapter
Status

Event ID 136 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 136 — [DROP] Dropping received RCP messages from %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] Dropping received RCP messages from %2.

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 137 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 137 — [DROP] Dropping received RCP messages from %2 invalid port number.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] Dropping received RCP messages from %2 invalid port number.

Fields

NameDescription
RemoteAddressIPLength
RemoteAddress

Event ID 138 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 138 — [DROP] TaFilterPacket Invalid Ethernet Header

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] TaFilterPacket Invalid Ethernet Header

Event ID 139 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 139 — [DROP] TaFilterPacket NetftInitializeDataBuffer failed

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] TaFilterPacket NetftInitializeDataBuffer failed

Event ID 140 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
ProcessId
WatchdogSource

Event ID 140 — The client process (ID 0x%1) was terminated.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

The client process (ID 0x%1) was terminated. Watchdog source %2.

Fields

NameDescription
ProcessId
WatchdogSource

Event ID 141 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
ProcessId
WatchdogSource

Event ID 141 — Watchdog timer timed out for the client process (ID 0x%1).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Watchdog timer timed out for the client process (ID 0x%1). The system will be halted. Watchdog source %2.

Fields

NameDescription
ProcessId
WatchdogSource

Event ID 142 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
ProcessId
WatchdogSource

Event ID 142 — Watchdog timer timed out for the client process (ID 0x%1).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Watchdog timer timed out for the client process (ID 0x%1). Looking for kd to allow debugging. Watchdog source %2.

Fields

NameDescription
ProcessId
WatchdogSource

Event ID 143 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointContext
EndpointAddressIPLength
EndpointAddress

Event ID 143 — Tunnel adapter %1 bound to %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Tunnel adapter %1 bound to %3

Fields

NameDescription
EndpointContext
EndpointAddressIPLength
EndpointAddress

Event ID 144 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointContext
EndpointAddressIPLength
EndpointAddress
Status

Event ID 144 — Tunnel adapter %1 failed to create socket %3 (status %4).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Tunnel adapter %1 failed to create socket %3 (status %4)

Fields

NameDescription
EndpointContext
EndpointAddressIPLength
EndpointAddress
Status

Event ID 145 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
Status

Event ID 145 — NetftEndpointCreateCounterSet: Creating WskCounterSet instance '.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

NetftEndpointCreateCounterSet: Creating WskCounterSet instance '%2' result %3

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
Status

Event ID 146 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress

Event ID 146 — [DROP] NetftSendDatagram - IoAllocateIrp failed when trying to send to %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] NetftSendDatagram - IoAllocateIrp failed when trying to send to %2

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress

Event ID 147 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress

Event ID 147 — [DROP] NetftSendDatagram - NdisAllocateFromNPagedLookasideList failed when trying to send to %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] NetftSendDatagram - NdisAllocateFromNPagedLookasideList failed when trying to send to %2

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress

Event ID 148 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointContext

Event ID 148 — [DROP] NetftReceiveDatagramHandler - AdpReferenceAdapterSafe failed (tunnel adapter %1).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] NetftReceiveDatagramHandler - AdpReferenceAdapterSafe failed (tunnel adapter %1).

Fields

NameDescription
EndpointContext

Event ID 149 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointContext

Event ID 149 — [DROP] NetftReceiveDatagramHandler - Tunnel adapter %1 is stopping.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] NetftReceiveDatagramHandler - Tunnel adapter %1 is stopping.

Fields

NameDescription
EndpointContext

Event ID 150 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointContext

Event ID 150 — [DROP] NetftReceiveDatagramHandler - Tunnel adapter %1 is not active.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] NetftReceiveDatagramHandler - Tunnel adapter %1 is not active.

Fields

NameDescription
EndpointContext

Event ID 151 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointContext

Event ID 151 — [DROP] Underlying socket terminated by WSK provider (tunnel adapter %1).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] Underlying socket terminated by WSK provider (tunnel adapter %1).

Fields

NameDescription
EndpointContext

Event ID 152 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointContext

Event ID 152 — [DROP] Tunnel adapter %1 failed to build datagram descriptor list.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[DROP] Tunnel adapter %1 failed to build datagram descriptor list.

Fields

NameDescription
EndpointContext

Event ID 153 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointContext
EndpointAddressIPLength
EndpointAddress
Status

Event ID 153 — Tunnel adapter %1 unbound from %3 with %4.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Tunnel adapter %1 unbound from %3 with %4.

Fields

NameDescription
EndpointContext
EndpointAddressIPLength
EndpointAddress
Status

Event ID 154 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Event ID 154 — Tunnel adapter failed to allocate NBL.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Tunnel adapter failed to allocate NBL.

Event ID 155 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 155 — [NetftQueryIfIndexByDataLinkddress] : NetftEnumerateInterfaces returned status %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftQueryIfIndexByDataLinkddress] : NetftEnumerateInterfaces returned status %1

Fields

NameDescription
Status

Event ID 156 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 156 — [NetftIsFaultTolerantIpAddress] : AdpOpenMiniportAdapter returned status %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftIsFaultTolerantIpAddress] : AdpOpenMiniportAdapter returned status %1

Fields

NameDescription
Status

Event ID 157 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 157 — [NetftIsFaultTolerantIpAddress] : NetftQueryIfIndexByIpAddress returned status %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

[NetftIsFaultTolerantIpAddress] : NetftQueryIfIndexByIpAddress returned status %1

Fields

NameDescription
Status

Event ID 158 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
InterfaceId
Status

Event ID 158 — Insert %2 into interface %3 completed with %4.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Insert %2 into interface %3 completed with %4

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
InterfaceId
Status

Event ID 159 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
InterfaceId
Status

Event ID 159 — Insert %2 into interface %3 completed with %4.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Insert %2 into interface %3 completed with %4

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
InterfaceId
Status

Event ID 160 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
InterfaceId
Status

Event ID 160 — Remove %2 from interface %3 completed with %4.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Remove %2 from interface %3 completed with %4

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
InterfaceId
Status

Event ID 161 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
InterfaceId
Status

Event ID 161 — Remove %2 from interface %3 completed with %4.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Remove %2 from interface %3 completed with %4

Fields

NameDescription
EndpointAddressIPLength
EndpointAddress
InterfaceId
Status

Event ID 162 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 162 — Failed to register address change handler with IPv4/802 provider

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Failed to register address change handler with IPv4/802 provider (%1)

Fields

NameDescription
Status

Event ID 163 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 163 — Failed to register address change handler with IPv6/802 provider

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Failed to register address change handler with IPv6/802 provider (%1)

Fields

NameDescription
Status

Event ID 164 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Status

Event ID 164 — Failed to register media sense handler with NDIS provider

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Failed to register media sense handler with NDIS provider (%1)

Fields

NameDescription
Status

Event ID 165 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
Context
NotificationType

Event ID 165 — PnP signals %1 address change (%2).

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

PnP signals %1 address change (%2)

Fields

NameDescription
Context
NotificationType

Event ID 166 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
InterfaceId
EndpointAddressIPLength
EndpointAddress
IpDadState

Event ID 166 — Interface %1 signals address %3 IP DAD State change to %4.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Interface %1 signals address %3 IP DAD State change to %4

Fields

NameDescription
InterfaceId
EndpointAddressIPLength
EndpointAddress
IpDadState

Event ID 167 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
InterfaceId
EndpointAddressIPLength
EndpointAddress
IpDadState

Event ID 167 — Interface %1 signals address %3 IP DAD State change to %4.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Interface %1 signals address %3 IP DAD State change to %4

Fields

NameDescription
InterfaceId
EndpointAddressIPLength
EndpointAddress
IpDadState

Event ID 168 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
NotificationType

Event ID 168 — PnP signals interface operational status change

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

PnP signals interface operational status change (%1)

Fields

NameDescription
NotificationType

Event ID 169 —

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Fields

NameDescription
InterfaceId
Status

Event ID 169 — Interface %1 signals operational status %2.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Verbose

Message

Interface %1 signals operational status %2

Fields

NameDescription
InterfaceId
Status

Event ID 4096 — Driver loaded.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Driver loaded.

Fields

NameDescription
Status

Event ID 8192 — Watchdog Started.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Watchdog Started. Instance: %1; Image Name: %4; PID: %2; Action: %5; Source: %6; Counter: %8; Missing Heartbeats Limit: %7;

Fields

NameDescription
Context
PID
ProcessImageNameLength
ProcessName
Action
Source
Period
Counter

Event ID 12288 — Watchdog Stopped.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Watchdog Stopped. Instance: %1; Image Name: %4; PID: %2; Action: %5; Source: %6; Counter: %8; Missing Heartbeats Limit: %7;

Fields

NameDescription
Context
PID
ProcessImageNameLength
ProcessName
Action
Source
Period
Counter

Event ID 16384 — Watchdog Heartbeat Missed.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Watchdog Heartbeat Missed. Instance: %1; Image Name: %4; PID: %2; Action: %5; Source: %6; Counter: %8; Missing Heartbeats Limit: %7;

Fields

NameDescription
Context
PID
ProcessImageNameLength
ProcessName
Action
Source
Period
Counter

Event ID 20480 — Watchdog Fired.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Watchdog Fired. Instance: %1; Image Name: %4; PID: %2; Action: %5; Source: %6; Counter: %8; Missing Heartbeats Limit: %7;

Fields

NameDescription
Context
PID
ProcessImageNameLength
ProcessName
Action
Source
Period
Counter

Event ID 24576 — Watchdog Updated.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Watchdog Updated. Instance: %1; Image Name: %4; PID: %2; Action: %5; Source: %6; Counter: %8; Missing Heartbeats Limit: %7;

Fields

NameDescription
Context
PID
ProcessImageNameLength
ProcessName
Action
Source
Period
Counter

Event ID 28672 — Watchdog Orphaned.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Watchdog Orphaned. Instance: %1; Image Name: %4; PID: %2; Action: %5; Source: %6; Counter: %8; Missing Heartbeats Limit: %7;

Fields

NameDescription
Context
PID
ProcessImageNameLength
ProcessName
Action
Source
Period
Counter

Event ID 32768 — Watchdog Orphaned.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Watchdog Orphaned. Process termination completed. Instance: %1; Image Name: %4; PID: %2; Action: %5; Source: %6; Counter: %8; Missing Heartbeats Limit: %7;

Fields

NameDescription
Context
PID
ProcessImageNameLength
ProcessName
Action
Source
Period
Counter

Event ID 36864 — Route added from %4 to %5 for context %1, ContextRouteCount: %6.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Route added from %4 to %5 for context %1, ContextRouteCount: %6. Source: %7

Fields

NameDescription
Context
SourceIPLength
DestinationIPLength
SourceIP
DestinationIP
ContextRouteCount
Source

Event ID 40960 — Route from %4 to %5 deleted for context %1, ContextRouteCount: %6.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Route from %4 to %5 deleted for context %1, ContextRouteCount: %6. Source: %7

Fields

NameDescription
Context
SourceIPLength
DestinationIPLength
SourceIP
DestinationIP
ContextRouteCount
Source

Event ID 45056 — Route cleanup scheduled for context %1, ContextRouteCount: %2, Source: %3.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Route cleanup scheduled for context %1, ContextRouteCount: %2, Source: %3

Fields

NameDescription
Context
ContextRouteCount
Source

Event ID 49152 — Livedump started.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Livedump started. : Report type: %2; Bugcheck code: %3; Parameter1: %4; Parameter2: %5; Parameter3: %6; Parameter4: %7; Flags: %8

Fields

NameDescription
Context
ReportType
BugcheckCode
Parameter1
Parameter2
Parameter3
Parameter4
Flags

Event ID 53248 — Livedump Completed.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

Livedump Completed. : Report type: %2; Bugcheck code: %3; Parameter1: %4; Parameter2: %5; Parameter3: %6; Parameter4: %7; Flags: %8 Status: %9

Fields

NameDescription
Context
ReportType
BugcheckCode
Parameter1
Parameter2
Parameter3
Parameter4
Flags
Status

Event ID 57344 — DPC Skew detected for Monitor %1.

Provider
Microsoft-Windows-FailoverClustering-NetFt
Channel
Operational

Message

DPC Skew detected for Monitor %1. DPC routine fired in %2 ticks (@ %3 ticks per sec), but was scheduled scheduled for %4 msecs, with tolerance range [min, max] = [%5, %6] ticks, current tick count %7.

Fields

NameDescription
Context
DelayTicks
TickRate
ScheduledTimeMilliseconds
MinimumToleranceTicks
MaximumToleranceTicks
CurrentTickCount