Microsoft-Windows-WebIO

156 events across 2 channels

Event ID	Title	Channel
1	%1: WebInitialize completed successfully (ApiVersion %3) (Flags %4) -> (API …	Diagnostic
2	WebInitialize failed with an error = %5 (ApiVersion %3) (Flags %4).	Diagnostic
3	%1 WebTerminate completed successfully.	Diagnostic
4	%1 WebTerminate failed with an error = %4.	Diagnostic
5	%3: WebCreateSession completed successfully.	Diagnostic
6	%1: WebCreateSession failed with an error = %6.	Diagnostic
7	%1: WebCloseSession called (Handle %2) (Flags %3).	Diagnostic
8	%1: WebCloseSession failed with an error = %4.	Diagnostic
9	%2(%1) API called.	Diagnostic
10	%2(%1) API returned successfully.	Diagnostic
11	%2(%1) API failed with an error = %3.	Diagnostic
12	%2(%1) API pending completion.	Diagnostic
13	%2(%1) API completed.	Diagnostic
14	%2(%1) API completed with an error = %3.	Diagnostic
15	%1: Set Request Option %3 (Handle %2) (Error %6) (Length %4) (Value %5).	Diagnostic
17	%1: WebCreateHttpRequest completed successfully.	Diagnostic
18	%3: WebCreateHttpRequest failed with error: %9.	Diagnostic
19	%1: WebCloseHttpRequest called (Handle %2) (Flags %3).	Diagnostic
20	%1 WebCloseHttpRequest failed with an error = %4.	Diagnostic
21	Synchronous API Event Handle Signall (Event %2) (Error %3) (Information %4).	Diagnostic
22	Synchronous API Event Handle Wait Completed (Handle %1) (Event %2) (Error %3) …	Diagnostic
23	%1: WebSetHttpRequestInformationRoutine completed successfully.	Diagnostic
24	%1: WebSetHttpRequestInformationRoutine failed with an error = %6.	Diagnostic
25	%1: WebRemoveHttpRequestInformationRoutine completed successfully.	Diagnostic
26	%1: WebRemoveHttpRequestInformationRoutine failed with an error = %6.	Diagnostic
27	%1: Indicating informational callback to request.	Diagnostic
28	%1: Informational callback to request complete.	Diagnostic
29	%1: WebCloseSession completed successfully.	Diagnostic
30	%1: WebCloseHttpRequest completed sucessfully error = %4.	Diagnostic
100	%1: Sending Headers: %3.	Diagnostic
101	%1: Received Headers: %3.	Diagnostic
102	%1: Starting Proxy Resolution.	Diagnostic
103	%1: Completed Proxy Resolution.	Diagnostic
104	%1: Acquired a connection slot (ConnMgr: %2), (Connection: %3).	Diagnostic
105	%1: Request on Endpoint (Server Endpoint: %2) (Proxy Endpoint: %3) (Connection …	Diagnostic
106	%1: Request Message Generated (DataChunk %2[%3]).	Diagnostic
107	%1: WebSendHttpRequestEntity (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) …	Diagnostic
108	%1: WebSendHttpRequestEntity Inline Completion (Handle: %2) (Error: %7) (Flags: …	Diagnostic
109	%1: HTTP Queuing Entity for Sending (DataChunks %2) (ChunkLength %3) (IsEntity …	Diagnostic
110	%1: HTTP Sending Entity (Connection: %2) (DataChunks %3) (PendingSendCount %4).	Diagnostic
111	%1: HTTP Send Entity Details (Connection: %2) (DataChunks %3) (Index %4) (Buffer …	Diagnostic
112	%1: HTTP Sending Entity Complete (Error %6) (Connection: %2) (DataChunks %3) …	Diagnostic
113	%1: Completing WebSendHttpRequest(Entity) (DataChunks %2) (Error %3) …	Diagnostic
114	%1: Completing WebSendHttpRequest(Entity) Complete (DataChunks %2).	Diagnostic
115	%1: WebHttpReceiveEntityBody (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) …	Diagnostic
116	%1: WebHttpReceiveEntityBody Inline Completion (Handle: %2) (Error: %7) (Flags: …	Diagnostic
117	%1: Completing WebHttpReceiveEntityBody (DataChunks %2) (Error %3) …	Diagnostic
118	%1: Completing WebHttpReceiveEntityBody Complete (DataChunks %2).	Diagnostic
119	%1: HTTP Connection changing Buffer (OldBuffer %2 [%3]) (NewBuffer %5 [%6]) …	Diagnostic
120	%1: HTTP Connection Buffer Posting Receive (DataChunks %2) (Buffer: %3 …	Diagnostic
121	%1: HTTP Connection Buffer Completing Receive (DataChunks %2) (Buffer: %3 …	Diagnostic
122	%1: HTTP Connection Buffer Receive Details (DataChunks %2) (Length %3) Data: %4.	Diagnostic
123	%1: HTTP Parser (Connection %2) (Buffer: %3 [%4/%5/%6]) (ParserChunk %7 [%8]).	Diagnostic
124	%1: HTTP Parser Complete (Connection %2) (Error %9) (Buffer: %3 [%4/%5/%6]) …	Diagnostic
125	%1: HTTP Parser Reset (Buffer %2) (HttpResponseCode %3).	Diagnostic
126	%1: HTTP Receive From Parser (DataChunk %2) (ParserChunk %3 [%4]) (Error %5) …	Diagnostic
127	%1: HTTP Receive (DataChunk %2) (BytesToRecv %3).	Diagnostic
128	%1: HTTP Receive Complete (DataChunk %2) (BytesToRecv %3) (Error %4) (Context …	Diagnostic
129	%1: HTTP Receive Entity Details (DataChunk %2) (Index %3) (Length %4) Data %5.	Diagnostic
130	%1: WebSendHttpRequest (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) …	Diagnostic
131	%1: WebSendHttpRequest Inline Completion (Handle: %2) (Error: %7) (Flags: %3) …	Diagnostic
132	%1: WebHttpReceiveResponse (Handle: %2) (Flags %3) (ResponseFlags %4) …	Diagnostic
133	%1: WebHttpReceiveEntityBody Inline Completion (Handle: %2) (Error: %6) (Flags: …	Diagnostic
134	%1: Completing WebHttpReceiveEntityBody (Error %3) (ResponseFlags %2) …	Diagnostic
135	%1: Completing WebHttpReceiveEntityBody Complete.	Diagnostic
136	%1: WebCancelHttpRequest (Handle: %2) (Flags %3).	Diagnostic
137	%1: WebCancelHttpRequest Complete (Error: %4) (Handle: %2) (Flags %3).	Diagnostic
200	%1: Connecting (Socket %2) (Context %5) (RemaingAddress %6) Address: %4.	Diagnostic
201	%1: Connection established (Socket %2) (Context %5).	Diagnostic
202	%1: Connect failed with error %7 (Socket %2) (Context %5) (RemaingAddress %6).	Diagnostic
203	Socket %2 created on Endpoint %1.	Diagnostic
204	%1: Socket %2 Closed (Reason = %3, Status = %4).	Diagnostic
205	%1: Name Resolution Request (Name %2) (Timeout %3) (CompletionContext: %4).	Diagnostic
206	%1: Name Resolution Request Completed (FQDN %2) (Canonical %3) (AddressCount: …	Diagnostic
207	%1: Name Resolution Request Failed (Error %2).	Diagnostic
208	%1: Name Resolution Request queued to %2.	Diagnostic
209	%1: Name Resolution Request is cancelled.	Diagnostic
210	%1: Name Resolution Request Timed-out.	Diagnostic
211	%1: Resolving addresses (Host %2) (Flags: %3).	Diagnostic
212	%1: Address resolution completed (Error = %4) (Host %2) (Flags: %3).	Diagnostic
213	%1: Winsock Send Entity Start(DataChunks %2) (Socket %3) (Buffers %4) (Context …	Diagnostic
214	%1: Winsock Send Entity Complete (Error %6) (Information %7) (Socket %3) …	Diagnostic
215	%1: Winsock Recv Entity Start (DataChunks %2) (Socket %3) (Buffers %4) (Context …	Diagnostic
216	%1: Winsock Recv Entity Complete(Error %6) (Information %7) (Socket %3) (Buffers …	Diagnostic
217	%1: (H/3 Connection ID %2) Got Stream (Stream Connection %3) (H/3 Stream ID %4).	Diagnostic
218	%1: Read Stream Data Indicated (StreamId %2) (Size %3) (Headers %4).	Diagnostic
219	%1: Stream Created (StreamId %2).	Diagnostic
220	%1: Stream Aborted (StreamId %2) (HRESULT error %3) (Reset Code %4).	Diagnostic
221	%1: Processing Initial HTTP/2 Setting (Id %2) (Value %3).	Diagnostic
222	%1: Received WINDOW_UPDATE frame (StreamId %2) (WindowIncrement %3) (IsSession …	Diagnostic
223	%1: Received GOAWAY frame (LastStreamId %2) (Error %3).	Diagnostic
224	%1: HTTP/2 Connection Aborted (Error %2).	Diagnostic
225	%1: HTTP/2 send window reached flow-control limit (StreamId %2) (IsSession %3).	Diagnostic
700	%1: InitializeSecurityContext - Credential Handle(%2:%3) Context Handle (%4:%5) …	Diagnostic
703	%1: InitializeSecurityContext returned - (%14) Credential Handle(%2:%3) Context …	Diagnostic
704	%1: InitializeSecurityContext Details (Pre) - Credential Handle(%2:%3) (Buffer …	Diagnostic
705	%1: InitializeSecurityContext Details (Post) - Credential Handle(%2:%3) …	Diagnostic
706	%1: SSL Encryption (SSLIOContext %2) Context Handle(%3:%4) (DataChunks: %5) …	Diagnostic
707	%1: SSL Encryption Complete (SSLIOContext %2) (ErrorCode: %10) Context …	Diagnostic
708	%1: SSL Encryption Failed (SSLIOContext %2) (ErrorCode: %10) Context …	Diagnostic
709	%1: SSL Encryption Details (SSLIOContext %2) Context Handle(%3:%4) (DataChunks: …	Diagnostic
710	%1: SSL Queue Send Entity (SSLIOContext %2) (DataChunks: %3).	Diagnostic
711	%1: SSL Send Entity Complete (SSLIOContext: %2) (Error: %5) (DataChunks: %3).	Diagnostic
712	%1: SSL Cert Validation - (Error: %6) Context Handle(%2:%3) …	Diagnostic
713	%1: SSL Cert Validation Failure - %7 (Error: %6) Context Handle(%2:%3) …	Diagnostic
720	%1: SSL Queue Recv Entity Data Chunk (SSLIOContext %2) (DataChunks: %3).	Diagnostic
721	%1: SSL Filling Up Recv Entity Data Chunk (SSLIOContext: %2) (DataChunks: %3) …	Diagnostic
722	%1: SSL Decryption - Context Handle(%2:%3) (Buffer %4[%5/%6]) (PlainData …	Diagnostic
723	%1: SSL Decryption Complete (SecStatus %9) (Error %10) Context Handle(%2:%3) …	Diagnostic
724	%1: SSL Receive Buffer Posting Receive (DataChunk %2) (Buffer %3[%4/%5]).	Diagnostic
725	%1: SSL Receive Buffer Receive Complete (DataChunk %2) (Error %7) (Information …	Diagnostic
726	%1: SSL Receive Buffer Details: (Buffer %2[%3/%4]) Data: %5.	Diagnostic
727	%1: SSL Receive Buffer Posting Receive (Buffer %2) (NewBuffer: %3).	Diagnostic
728	%1: SSL AcquireCredentialsHandle - (EnabledProtocols %2) (ClientCert %3) …	Diagnostic
729	%1: SSL AcquireCredentialsHandle returned - (%7) Credential Handle(%5:%6) …	Diagnostic
730	%1: SSL AcquireCredentialsHandle failed - (%7) (EnabledProtocols %2) (ClientCert …	Diagnostic
731	Failed to create HTTP/3 API session due to TLS 1.	Operational
900	%1: WebCompleteProtocolUpgrade completed successfully.	Diagnostic
901	%1: WebCompleteProtocolUpgrade failed with error: %7.	Diagnostic
902	%1: WebProtocolCancelHandle (Handle: %2).	Diagnostic
903	%1: WebProtocolCancelHandle Complete (Error: %3) (Handle: %2).	Diagnostic
904	%1: WebCloseProtocolHandle called (Handle %2).	Diagnostic
905	%1: WebCloseProtocolHandle completed (Error %4) (Handle %2).	Diagnostic
906	%1: Set Protocol Option %3 (Handle %2) (Error %6) (Length %4) (Value %5).	Diagnostic
907	%1: WebProtocolSendData (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) …	Diagnostic
908	%1: WebProtocolSendData Inline Completion (Handle: %2) (Error: %7) (Flags: %3) …	Diagnostic
909	%1: Completing WebProtocolSendData (Handle: %2) (Error: %3) CompletionContext …	Diagnostic
910	%1: Completing WebProtocolSendData Complete (Handle: %2) (Error: %3) …	Diagnostic
911	%1: WebProtocolReceiveData (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) …	Diagnostic
912	%1: WebProtocolReceiveData Inline Completion (Handle: %2) (Error: %7) (Flags: …	Diagnostic
913	%1: Completing WebProtocolReceiveData (Handle: %2) (Error: %3) CompletionContext …	Diagnostic
914	%1: Completing WebProtocolReceiveData Complete (Handle: %2) (Error: %3) …	Diagnostic
2100	%1: =====Request Initialize===================.	Diagnostic
2101	%1: =====Query Endpoints======================.	Diagnostic
2102	%1: =====Waiting For Available Connection=====.	Diagnostic
2111	%1: =====Request Connect======================.	Diagnostic
2112	%1: =====Name Resolution======================.	Diagnostic
2113	%1: =====TCP Connect==========================.	Diagnostic
2114	%1: =====SSL Negotiation======================.	Diagnostic
2120	%1: =====Generate Headers=====================.	Diagnostic
2121	%1: =====Send Headers=========================.	Diagnostic
2122	%1: =====Send Entity==========================.	Diagnostic
2123	%1: =====Send Complete========================.	Diagnostic
2130	%1: =====Receive Headers======================.	Diagnostic
2131	%1: =====Receive Entity=======================.	Diagnostic
2132	%1: =====Receive Complete=====================.	Diagnostic
2140	%1: =====Request Restart======================.	Diagnostic
2141	%1: =====Request Done=========================.	Diagnostic
59992	Restore Thread Token %1 (Error: %2).	Diagnostic
59993	Set Thread Token %1 (OldToken %2) (Error: %3).	Diagnostic
59994	Get Thread Token %1 (Error: %3) (SID: %2).	Diagnostic
59995	Canceling %2 Thread Action (Context: %1).	Diagnostic
59996	Queue %2 Thread Action (Context: %1).	Diagnostic
59997	Stopping %2 Thread Action (Context: %1).	Diagnostic
59998	Starting %2 Thread Action (Context: %1).	Diagnostic
59999		Diagnostic

Event ID 1 — %1: WebInitialize completed successfully (ApiVersion %3) (Flags %4) -> (API Handle = %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebInitialize completed successfully (ApiVersion %3) (Flags %4) -> (API Handle = %2).

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`ApiVersion`	—
`Flags`	—
`Error`	—

Event ID 2 — WebInitialize failed with an error = %5 (ApiVersion %3) (Flags %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

WebInitialize failed with an error = %5 (ApiVersion %3) (Flags %4)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`ApiVersion`	—
`Flags`	—
`Error`	—

Event ID 3 — %1 WebTerminate completed successfully.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1 WebTerminate completed successfully. (Handle %2) (Flags %3)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Flags`	—
`Error`	—

Event ID 4 — %1 WebTerminate failed with an error = %4.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1 WebTerminate failed with an error = %4. (Handle %2) (Flags %3)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Flags`	—
`Error`	—

Event ID 5 — %3: WebCreateSession completed successfully.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%3: WebCreateSession completed successfully. (ApiHandle %1[%2]) (Flags: %5) -> (Session Handle: %4)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Session`	—
`SessionHandle`	—
`Flags`	—
`Error`	—

Event ID 6 — %1: WebCreateSession failed with an error = %6.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCreateSession failed with an error = %6. (ApiHandle %1[%2]) (Flags: %5)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Session`	—
`SessionHandle`	—
`Flags`	—
`Error`	—

Event ID 7 — %1: WebCloseSession called (Handle %2) (Flags %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCloseSession called (Handle %2) (Flags %3)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Flags`	—
`Error`	—

Event ID 8 — %1: WebCloseSession failed with an error = %4.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCloseSession failed with an error = %4. (Handle %2) (Flags %3)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Flags`	—
`Error`	—

Event ID 9 — %2(%1) API called.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%2(%1) API called.

Fields

Name	Description
`ApiHandle`	—
`Api`	—

Event ID 10 — %2(%1) API returned successfully.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%2(%1) API returned successfully.

Fields

Name	Description
`ApiHandle`	—
`Api`	—
`Result`	—

Event ID 11 — %2(%1) API failed with an error = %3.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%2(%1) API failed with an error = %3.

Fields

Name	Description
`ApiHandle`	—
`Api`	—
`Result`	—

Event ID 12 — %2(%1) API pending completion.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%2(%1) API pending completion.

Fields

Name	Description
`ApiHandle`	—
`Api`	—

Event ID 13 — %2(%1) API completed.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%2(%1) API completed.

Fields

Name	Description
`ApiHandle`	—
`Api`	—
`Result`	—

Event ID 14 — %2(%1) API completed with an error = %3.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%2(%1) API completed with an error = %3.

Fields

Name	Description
`ApiHandle`	—
`Api`	—
`Result`	—

Event ID 15 — %1: Set Request Option %3 (Handle %2) (Error %6) (Length %4) (Value %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Set Request Option %3 (Handle %2) (Error %6) (Length %4) (Value %5)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Option`	—
`Length`	—
`Value`	—
`Error`	—

Event ID 17 — %1: WebCreateHttpRequest completed successfully.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCreateHttpRequest completed successfully. (Session %3[%4]) (Method %5) (URI %6) (Version %7.%8) -> (Request Handle %2)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Session`	—
`SessionHandle`	—
`Method`	—
`URI`	—
`VersionMajor`	—
`VersionMinor`	—
`Error`	—

Event ID 18 — %3: WebCreateHttpRequest failed with error: %9.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%3: WebCreateHttpRequest failed with error: %9. (Session %3[%4]) (Method %5) (URI %6) (Version %7.%8)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Session`	—
`SessionHandle`	—
`Method`	—
`URI`	—
`VersionMajor`	—
`VersionMinor`	—
`Error`	—

Event ID 19 — %1: WebCloseHttpRequest called (Handle %2) (Flags %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCloseHttpRequest called (Handle %2) (Flags %3)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Flags`	—
`Error`	—

Event ID 20 — %1 WebCloseHttpRequest failed with an error = %4.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1 WebCloseHttpRequest failed with an error = %4. (Handle %2) (Flags %3)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Flags`	—
`Error`	—

Event ID 21 — Synchronous API Event Handle Signall (Event %2) (Error %3) (Information %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

Synchronous API Event Handle Signall (Event %2) (Error %3) (Information %4)

Fields

Name	Description
`Handle`	—
`Event`	—
`Error`	—
`Information`	—

Event ID 22 — Synchronous API Event Handle Wait Completed (Handle %1) (Event %2) (Error %3) (Information %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

Synchronous API Event Handle Wait Completed (Handle %1) (Event %2) (Error %3) (Information %4)

Fields

Name	Description
`Handle`	—
`Event`	—
`Error`	—
`Information`	—

Event ID 23 — %1: WebSetHttpRequestInformationRoutine completed successfully.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebSetHttpRequestInformationRoutine completed successfully. (Handle %2) (Flags %3) (InformationRoutine %4) (InformationContext %5)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`InformationRoutine`	—
`InformationContext`	—
`Error`	—

Event ID 24 — %1: WebSetHttpRequestInformationRoutine failed with an error = %6.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebSetHttpRequestInformationRoutine failed with an error = %6. (Handle %2) (Flags %3) (InformationRoutine %4) (InformationContext %5)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`InformationRoutine`	—
`InformationContext`	—
`Error`	—

Event ID 25 — %1: WebRemoveHttpRequestInformationRoutine completed successfully.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebRemoveHttpRequestInformationRoutine completed successfully. (Handle %2) (Flags %3)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`InformationRoutine`	—
`InformationContext`	—
`Error`	—

Event ID 26 — %1: WebRemoveHttpRequestInformationRoutine failed with an error = %6.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebRemoveHttpRequestInformationRoutine failed with an error = %6. (Handle %2) (Flags %3)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`InformationRoutine`	—
`InformationContext`	—
`Error`	—

Event ID 27 — %1: Indicating informational callback to request.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Indicating informational callback to request. (PendingCount %2) (InformationRoutine %3) (InformationContext %4) (Type %5) (Information %6) (InformationLength %7

Fields

Name	Description
`Request`	—
`PendingCount`	—
`InformationRoutine`	—
`InformationContext`	—
`Type`	—
`Information`	—
`InformationLength`	—

Event ID 28 — %1: Informational callback to request complete.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Informational callback to request complete. (PendingCount %2) (InformationRoutine %3) (InformationContext %4) (Type %5) (Information %6) (InformationLength %7

Fields

Name	Description
`Request`	—
`PendingCount`	—
`InformationRoutine`	—
`InformationContext`	—
`Type`	—
`Information`	—
`InformationLength`	—

Event ID 29 — %1: WebCloseSession completed successfully.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCloseSession completed successfully. (Handle %2) (Flags %3)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Flags`	—
`Error`	—

Event ID 30 — %1: WebCloseHttpRequest completed sucessfully error = %4.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCloseHttpRequest completed sucessfully error = %4. (Handle %2) (Flags %3)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Flags`	—
`Error`	—

Event ID 100 — %1: Sending Headers: %3.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Sending Headers: %3

Fields

Name	Description
`Request`	—
`Length`	—
`Headers`	—

Event ID 101 — %1: Received Headers: %3.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Received Headers: %3

Fields

Name	Description
`Request`	—
`Length`	—
`Headers`	—

Event ID 102 — %1: Starting Proxy Resolution.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Starting Proxy Resolution

Fields

Name	Description
`Context`	—

Event ID 103 — %1: Completed Proxy Resolution.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completed Proxy Resolution

Fields

Name	Description
`Context`	—

Event ID 104 — %1: Acquired a connection slot (ConnMgr: %2), (Connection: %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Acquired a connection slot (ConnMgr: %2), (Connection: %3)

Fields

Name	Description
`Request`	—
`ConnMgr`	—
`Connection`	—

Event ID 105 — %1: Request on Endpoint (Server Endpoint: %2) (Proxy Endpoint: %3) (Connection Manager: %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Request on Endpoint (Server Endpoint: %2) (Proxy Endpoint: %3) (Connection Manager: %4)

Fields

Name	Description
`Request`	—
`ServerEndpoint`	—
`ProxyEndpoint`	—
`ConnectionManager`	—

Event ID 106 — %1: Request Message Generated (DataChunk %2[%3]).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Request Message Generated (DataChunk %2[%3])

Fields

Name	Description
`Request`	—
`DataChunks`	—
`Length`	—

Event ID 107 — %1: WebSendHttpRequestEntity (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebSendHttpRequestEntity (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`DataChunks`	—
`DataChunkCount`	—
`CompletionContext`	—
`Error`	—

Event ID 108 — %1: WebSendHttpRequestEntity Inline Completion (Handle: %2) (Error: %7) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebSendHttpRequestEntity Inline Completion (Handle: %2) (Error: %7) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`DataChunks`	—
`DataChunkCount`	—
`CompletionContext`	—
`Error`	—

Event ID 109 — %1: HTTP Queuing Entity for Sending (DataChunks %2) (ChunkLength %3) (IsEntity %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Queuing Entity for Sending (DataChunks %2) (ChunkLength %3) (IsEntity %4) (All Entity Posted? %5)

Fields

Name	Description
`Request`	—
`DataChunks`	—
`TotalChunkLength`	—
`IsEntity`	—
`RequestEntityComplete`	—

Event ID 110 — %1: HTTP Sending Entity (Connection: %2) (DataChunks %3) (PendingSendCount %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Sending Entity (Connection: %2) (DataChunks %3) (PendingSendCount %4) (LastSend? %5)

Fields

Name	Description
`Request`	—
`Connection`	—
`DataChunks`	—
`PendingSendCount`	—
`LastSend`	—
`Error`	—

Event ID 111 — %1: HTTP Send Entity Details (Connection: %2) (DataChunks %3) (Index %4) (Buffer %5 [%6]) Data: %7.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Send Entity Details (Connection: %2) (DataChunks %3) (Index %4) (Buffer %5 [%6]) Data: %7

Fields

Name	Description
`Request`	—
`Connection`	—
`DataChunks`	—
`Index`	—
`Buffer`	—
`Length`	—
`Data`	—

Event ID 112 — %1: HTTP Sending Entity Complete (Error %6) (Connection: %2) (DataChunks %3) (PendingSendCount %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Sending Entity Complete (Error %6) (Connection: %2) (DataChunks %3) (PendingSendCount %4) (LastSend? %5)

Fields

Name	Description
`Request`	—
`Connection`	—
`DataChunks`	—
`PendingSendCount`	—
`LastSend`	—
`Error`	—

Event ID 113 — %1: Completing WebSendHttpRequest(Entity) (DataChunks %2) (Error %3) (CompletionContext %4) (CompletionInformation %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completing WebSendHttpRequest(Entity) (DataChunks %2) (Error %3) (CompletionContext %4) (CompletionInformation %5)

Fields

Name	Description
`Request`	—
`DataChunks`	—
`Error`	—
`CompletionContext`	—
`CompletionInformation`	—

Event ID 114 — %1: Completing WebSendHttpRequest(Entity) Complete (DataChunks %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completing WebSendHttpRequest(Entity) Complete (DataChunks %2)

Fields

Name	Description
`Request`	—
`DataChunks`	—
`Error`	—
`CompletionContext`	—
`CompletionInformation`	—

Event ID 115 — %1: WebHttpReceiveEntityBody (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebHttpReceiveEntityBody (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`DataChunks`	—
`DataChunkCount`	—
`CompletionContext`	—
`Error`	—

Event ID 116 — %1: WebHttpReceiveEntityBody Inline Completion (Handle: %2) (Error: %7) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebHttpReceiveEntityBody Inline Completion (Handle: %2) (Error: %7) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`DataChunks`	—
`DataChunkCount`	—
`CompletionContext`	—
`Error`	—

Event ID 117 — %1: Completing WebHttpReceiveEntityBody (DataChunks %2) (Error %3) (CompletionContext %4) (CompletionInformation %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completing WebHttpReceiveEntityBody (DataChunks %2) (Error %3) (CompletionContext %4) (CompletionInformation %5)

Fields

Name	Description
`Request`	—
`DataChunks`	—
`Error`	—
`CompletionContext`	—
`CompletionInformation`	—

Event ID 118 — %1: Completing WebHttpReceiveEntityBody Complete (DataChunks %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completing WebHttpReceiveEntityBody Complete (DataChunks %2)

Fields

Name	Description
`Request`	—
`DataChunks`	—
`Error`	—
`CompletionContext`	—
`CompletionInformation`	—

Event ID 119 — %1: HTTP Connection changing Buffer (OldBuffer %2 [%3]) (NewBuffer %5 [%6]) (Carryover %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Connection changing Buffer (OldBuffer %2 [%3]) (NewBuffer %5 [%6]) (Carryover %4)

Fields

Name	Description
`Connection`	—
`OldBuffer`	—
`OldBufferLength`	—
`BufferLengthData`	—
`NewBuffer`	—
`NewBufferLength`	—

Event ID 120 — %1: HTTP Connection Buffer Posting Receive (DataChunks %2) (Buffer: %3 [%4/%5/%6]).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Connection Buffer Posting Receive (DataChunks %2) (Buffer: %3 [%4/%5/%6])

Fields

Name	Description
`Connection`	—
`DataChunks`	—
`Buffer`	—
`BufferLengthConsumed`	—
`BufferLengthData`	—
`BufferLengthRemaining`	—
`Error`	—
`Information`	—

Event ID 121 — %1: HTTP Connection Buffer Completing Receive (DataChunks %2) (Buffer: %3 [%4/%5/%6]) (Error %7) (CompletionInformation %8).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Connection Buffer Completing Receive (DataChunks %2) (Buffer: %3 [%4/%5/%6]) (Error %7)  (CompletionInformation %8)

Fields

Name	Description
`Connection`	—
`DataChunks`	—
`Buffer`	—
`BufferLengthConsumed`	—
`BufferLengthData`	—
`BufferLengthRemaining`	—
`Error`	—
`Information`	—

Event ID 122 — %1: HTTP Connection Buffer Receive Details (DataChunks %2) (Length %3) Data: %4.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Connection Buffer Receive Details (DataChunks %2) (Length %3) Data: %4

Fields

Name	Description
`Connection`	—
`DataChunks`	—
`Length`	—
`Data`	—

Event ID 123 — %1: HTTP Parser (Connection %2) (Buffer: %3 [%4/%5/%6]) (ParserChunk %7 [%8]).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Parser (Connection %2) (Buffer: %3 [%4/%5/%6]) (ParserChunk %7 [%8])

Fields

Name	Description
`Request`	—
`Connection`	—
`Buffer`	—
`BufferLengthConsumed`	—
`BufferLengthData`	—
`BufferLengthRemaining`	—
`ChunkData`	—
`ChunkDataLength`	—
`Error`	—

Event ID 124 — %1: HTTP Parser Complete (Connection %2) (Error %9) (Buffer: %3 [%4/%5/%6]) (ParserChunk %7 [%8]).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Parser Complete (Connection %2) (Error %9) (Buffer: %3 [%4/%5/%6]) (ParserChunk %7 [%8])

Fields

Name	Description
`Request`	—
`Connection`	—
`Buffer`	—
`BufferLengthConsumed`	—
`BufferLengthData`	—
`BufferLengthRemaining`	—
`ChunkData`	—
`ChunkDataLength`	—
`Error`	—

Event ID 125 — %1: HTTP Parser Reset (Buffer %2) (HttpResponseCode %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Parser Reset (Buffer %2) (HttpResponseCode %3)

Fields

Name	Description
`Request`	—
`Buffer`	—
`HttpResponseCode`	—

Event ID 126 — %1: HTTP Receive From Parser (DataChunk %2) (ParserChunk %3 [%4]) (Error %5) (Context %6) (Information %7).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Receive From Parser (DataChunk %2) (ParserChunk %3 [%4]) (Error %5) (Context %6) (Information %7)

Fields

Name	Description
`Request`	—
`DataChunks`	—
`ChunkData`	—
`ChunkDataLength`	—
`Error`	—
`CompletionContext`	—
`CompletionInformation`	—

Event ID 127 — %1: HTTP Receive (DataChunk %2) (BytesToRecv %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Receive (DataChunk %2) (BytesToRecv %3)

Fields

Name	Description
`Request`	—
`DataChunks`	—
`BytesToReceive`	—
`Error`	—
`CompletionContext`	—
`CompletionInformation`	—

Event ID 128 — %1: HTTP Receive Complete (DataChunk %2) (BytesToRecv %3) (Error %4) (Context %5) (Information %6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Receive Complete (DataChunk %2) (BytesToRecv %3) (Error %4) (Context %5) (Information %6)

Fields

Name	Description
`Request`	—
`DataChunks`	—
`BytesToReceive`	—
`Error`	—
`CompletionContext`	—
`CompletionInformation`	—

Event ID 129 — %1: HTTP Receive Entity Details (DataChunk %2) (Index %3) (Length %4) Data %5.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP Receive Entity Details (DataChunk %2) (Index %3) (Length %4) Data %5

Fields

Name	Description
`Request`	—
`DataChunks`	—
`Index`	—
`Length`	—
`Data`	—

Event ID 130 — %1: WebSendHttpRequest (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebSendHttpRequest (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`DataChunks`	—
`DataChunkCount`	—
`CompletionContext`	—
`Error`	—

Event ID 131 — %1: WebSendHttpRequest Inline Completion (Handle: %2) (Error: %7) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebSendHttpRequest Inline Completion (Handle: %2) (Error: %7) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`DataChunks`	—
`DataChunkCount`	—
`CompletionContext`	—
`Error`	—

Event ID 132 — %1: WebHttpReceiveResponse (Handle: %2) (Flags %3) (ResponseFlags %4) CompletionContext (%5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebHttpReceiveResponse (Handle: %2) (Flags %3) (ResponseFlags %4) CompletionContext (%5)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`ResponseFlags`	—
`CompletionContext`	—
`Error`	—

Event ID 133 — %1: WebHttpReceiveEntityBody Inline Completion (Handle: %2) (Error: %6) (Flags: %3) (ResponseFlags %4) CompletionContext (%5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebHttpReceiveEntityBody Inline Completion (Handle: %2) (Error: %6) (Flags: %3) (ResponseFlags %4) CompletionContext (%5)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`ResponseFlags`	—
`CompletionContext`	—
`Error`	—

Event ID 134 — %1: Completing WebHttpReceiveEntityBody (Error %3) (ResponseFlags %2) (CompletionInformation %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completing WebHttpReceiveEntityBody (Error %3) (ResponseFlags %2) (CompletionInformation %4)

Fields

Name	Description
`Request`	—
`ResponseFlags`	—
`Error`	—
`CompletionContext`	—

Event ID 135 — %1: Completing WebHttpReceiveEntityBody Complete.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completing WebHttpReceiveEntityBody Complete

Fields

Name	Description
`Request`	—
`ResponseFlags`	—
`Error`	—
`CompletionContext`	—

Event ID 136 — %1: WebCancelHttpRequest (Handle: %2) (Flags %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCancelHttpRequest (Handle: %2) (Flags %3)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`Error`	—

Event ID 137 — %1: WebCancelHttpRequest Complete (Error: %4) (Handle: %2) (Flags %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCancelHttpRequest Complete (Error: %4) (Handle: %2) (Flags %3)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`Error`	—

Event ID 200 — %1: Connecting (Socket %2) (Context %5) (RemaingAddress %6) Address: %4.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Connecting (Socket %2) (Context %5) (RemaingAddress %6) Address: %4.

Fields

Name	Description
`Connection`	—
`SocketHandle`	—
`AddressLength`	—
`Address`	—
`Context`	—
`RemainingAddressCount`	—
`Error`	—
`Http3ClientConnectionId`	—

Event ID 201 — %1: Connection established (Socket %2) (Context %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Connection established (Socket %2) (Context %5)

Fields

Name	Description
`Connection`	—
`SocketHandle`	—
`AddressLength`	—
`Address`	—
`Context`	—
`RemainingAddressCount`	—
`Error`	—
`Http3ClientConnectionId`	—

Event ID 202 — %1: Connect failed with error %7 (Socket %2) (Context %5) (RemaingAddress %6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Connect failed with error %7 (Socket %2) (Context %5) (RemaingAddress %6)

Fields

Name	Description
`Connection`	—
`SocketHandle`	—
`AddressLength`	—
`Address`	—
`Context`	—
`RemainingAddressCount`	—
`Error`	—
`Http3ClientConnectionId`	—

Event ID 203 — Socket %2 created on Endpoint %1.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

Socket %2 created on Endpoint %1.

Fields

Name	Description
`Connection`	—
`SocketHandle`	—
`Error`	—
`Http3ClientConnectionId`	—

Event ID 204 — %1: Socket %2 Closed (Reason = %3, Status = %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Socket %2 Closed (Reason = %3, Status = %4).

Fields

Name	Description
`Endpoint`	—
`Socket`	—
`Reason`	—
`Result`	—
`Http3ClientConnectionId`	—
`Aborted`	—

Event ID 205 — %1: Name Resolution Request (Name %2) (Timeout %3) (CompletionContext: %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Name Resolution Request (Name %2) (Timeout %3) (CompletionContext: %4)

Fields

Name	Description
`DnsQuery`	—
`HostName`	—
`Timeout`	—
`CompletionContext`	—

Event ID 206 — %1: Name Resolution Request Completed (FQDN %2) (Canonical %3) (AddressCount: %4) AddressData: %6.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Name Resolution Request Completed (FQDN %2) (Canonical %3) (AddressCount: %4) AddressData: %6

Fields

Name	Description
`DnsQuery`	—
`FQDN`	—
`CanonicalName`	—
`AddressCount`	—
`SockaddrLength`	—
`SockAddr`	—

Event ID 207 — %1: Name Resolution Request Failed (Error %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Name Resolution Request Failed (Error %2)

Fields

Name	Description
`DnsQuery`	—
`Error`	—

Event ID 208 — %1: Name Resolution Request queued to %2.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Name Resolution Request queued to %2

Fields

Name	Description
`DnsQuery`	—
`CacheEntry`	—

Event ID 209 — %1: Name Resolution Request is cancelled.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Name Resolution Request is cancelled

Fields

Name	Description
`ReferenceContext`	—

Event ID 210 — %1: Name Resolution Request Timed-out.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Name Resolution Request Timed-out

Fields

Name	Description
`ReferenceContext`	—

Event ID 211 — %1: Resolving addresses (Host %2) (Flags: %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Resolving addresses (Host %2) (Flags: %3)

Fields

Name	Description
`CacheEntry`	—
`ResolveName`	—
`Flags`	—
`Error`	—
`AddressCount`	—

Event ID 212 — %1: Address resolution completed (Error = %4) (Host %2) (Flags: %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Address resolution completed (Error = %4) (Host %2) (Flags: %3).(AddressCount %5)

Fields

Name	Description
`CacheEntry`	—
`ResolveName`	—
`Flags`	—
`Error`	—
`AddressCount`	—

Event ID 213 — %1: Winsock Send Entity Start(DataChunks %2) (Socket %3) (Buffers %4) (Context %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Winsock Send Entity Start(DataChunks %2) (Socket %3) (Buffers %4) (Context %5)

Fields

Name	Description
`Connection`	—
`DataChunks`	—
`SocketHandle`	—
`Buffer`	—
`Context`	—
`Error`	—
`Information`	—
`Http3ClientStreamId`	—
`BufferLength`	—
`IsEof`	—
`IsHeaderPairs`	—

Event ID 214 — %1: Winsock Send Entity Complete (Error %6) (Information %7) (Socket %3) (Buffers %4) (Context %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Winsock Send Entity Complete (Error %6) (Information %7) (Socket %3) (Buffers %4) (Context %5)

Fields

Name	Description
`Connection`	—
`DataChunks`	—
`SocketHandle`	—
`Buffer`	—
`Context`	—
`Error`	—
`Information`	—
`Http3ClientStreamId`	—
`BufferLength`	—
`IsEof`	—
`IsHeaderPairs`	—

Event ID 215 — %1: Winsock Recv Entity Start (DataChunks %2) (Socket %3) (Buffers %4) (Context %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Winsock Recv Entity Start (DataChunks %2) (Socket %3) (Buffers %4) (Context %5)

Fields

Name	Description
`Connection`	—
`DataChunks`	—
`SocketHandle`	—
`Buffer`	—
`Context`	—
`Error`	—
`Information`	—
`Http3ClientStreamId`	—
`BufferLength`	—
`IsEof`	—
`IsHeaderPairs`	—

Event ID 216 — %1: Winsock Recv Entity Complete(Error %6) (Information %7) (Socket %3) (Buffers %4) (Context %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Winsock Recv Entity Complete(Error %6) (Information %7) (Socket %3) (Buffers %4) (Context %5)

Fields

Name	Description
`Connection`	—
`DataChunks`	—
`SocketHandle`	—
`Buffer`	—
`Context`	—
`Error`	—
`Information`	—
`Http3ClientStreamId`	—
`BufferLength`	—
`IsEof`	—
`IsHeaderPairs`	—

Event ID 217 — %1: (H/3 Connection ID %2) Got Stream (Stream Connection %3) (H/3 Stream ID %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: (H/3 Connection ID %2) Got Stream (Stream Connection %3) (H/3 Stream ID %4)

Fields

Name	Description
`Connection`	—
`Http3ClientConnectionId`	—
`StreamConnection`	—
`Http3ClientStreamId`	—

Event ID 218 — %1: Read Stream Data Indicated (StreamId %2) (Size %3) (Headers %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Read Stream Data Indicated (StreamId %2) (Size %3) (Headers %4)

Fields

Name	Description
`Connection`	—
`StreamId`	—
`Size`	—
`Headers`	—

Event ID 219 — %1: Stream Created (StreamId %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Stream Created (StreamId %2)

Fields

Name	Description
`Connection`	—
`StreamId`	—

Event ID 220 — %1: Stream Aborted (StreamId %2) (HRESULT error %3) (Reset Code %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Stream Aborted (StreamId %2) (HRESULT error %3) (Reset Code %4)

Fields

Name	Description
`Connection`	—
`StreamId`	—
`Error`	—
`ResetCode`	—

Event ID 221 — %1: Processing Initial HTTP/2 Setting (Id %2) (Value %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Processing Initial HTTP/2 Setting (Id %2) (Value %3)

Fields

Name	Description
`Connection`	—
`SettingId`	—
`SettingValue`	—

Event ID 222 — %1: Received WINDOW_UPDATE frame (StreamId %2) (WindowIncrement %3) (IsSession %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Received WINDOW_UPDATE frame (StreamId %2) (WindowIncrement %3) (IsSession %4)

Fields

Name	Description
`Connection`	—
`StreamId`	—
`WindowIncrement`	—
`IsSession`	—

Event ID 223 — %1: Received GOAWAY frame (LastStreamId %2) (Error %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Received GOAWAY frame (LastStreamId %2) (Error %3)

Fields

Name	Description
`Connection`	—
`LastStreamId`	—
`Error`	—

Event ID 224 — %1: HTTP/2 Connection Aborted (Error %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP/2 Connection Aborted (Error %2)

Fields

Name	Description
`Connection`	—
`Error`	—

Event ID 225 — %1: HTTP/2 send window reached flow-control limit (StreamId %2) (IsSession %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: HTTP/2 send window reached flow-control limit (StreamId %2) (IsSession %3)

Fields

Name	Description
`Connection`	—
`StreamId`	—
`IsSession`	—

Event ID 700 — %1: InitializeSecurityContext - Credential Handle(%2:%3) Context Handle (%4:%5) (Hostname %6) (InputFlags %7) (Buffer %8 [%9/%10]).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: InitializeSecurityContext - Credential Handle(%2:%3) Context Handle (%4:%5) (Hostname %6) (InputFlags %7) (Buffer %8 [%9/%10])

Fields

Name	Description
`Connection`	—
`SecurityHandleHigh`	—
`SecurityHandleLow`	—
`CredHandleHigh`	—
`CredHandleLow`	—
`HostName`	—
`InputFlags`	—
`Buffer`	—
`BufferLengthData`	—
`BufferLengthRemaining`	—
`OutputFlags`	—
`DataChunks`	—
`DataChunkBufferLength`	—
`Result`	—

Event ID 703 — %1: InitializeSecurityContext returned - (%14) Credential Handle(%2:%3) Context Handle (%4:%5) (OutputFlags %11) (Buffer %8 [%9/%10]).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: InitializeSecurityContext returned - (%14) Credential Handle(%2:%3) Context Handle (%4:%5) (OutputFlags %11) (Buffer %8 [%9/%10]) (DataChunk %12 [%13])

Fields

Name	Description
`Connection`	—
`SecurityHandleHigh`	—
`SecurityHandleLow`	—
`CredHandleHigh`	—
`CredHandleLow`	—
`HostName`	—
`InputFlags`	—
`Buffer`	—
`BufferLengthData`	—
`BufferLengthRemaining`	—
`OutputFlags`	—
`DataChunks`	—
`DataChunkBufferLength`	—
`Result`	—

Event ID 704 — %1: InitializeSecurityContext Details (Pre) - Credential Handle(%2:%3) (Buffer %4 [%5/%6]) Data: %7.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: InitializeSecurityContext Details (Pre) - Credential Handle(%2:%3) (Buffer %4 [%5/%6]) Data: %7

Fields

Name	Description
`Connection`	—
`SecurityHandleHigh`	—
`SecurityHandleLow`	—
`Buffer`	—
`BufferLengthData`	—
`BufferLengthRemaining`	—
`Data`	—

Event ID 705 — %1: InitializeSecurityContext Details (Post) - Credential Handle(%2:%3) (DataChunk %4 [%5]) Data: %6.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: InitializeSecurityContext Details (Post) - Credential Handle(%2:%3) (DataChunk %4 [%5]) Data: %6

Fields

Name	Description
`Connection`	—
`SecurityHandleHigh`	—
`SecurityHandleLow`	—
`DataChunks`	—
`DataChunkBufferLength`	—
`Data`	—

Event ID 706 — %1: SSL Encryption (SSLIOContext %2) Context Handle(%3:%4) (DataChunks: %5) (Index: %6) (OutBuffer: %7[%8]) (Flags %9).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Encryption (SSLIOContext %2) Context Handle(%3:%4) (DataChunks: %5) (Index: %6) (OutBuffer: %7[%8]) (Flags %9)

Fields

Name	Description
`Connection`	—
`SslIOContext`	—
`CredHandleHigh`	—
`CredHandleLow`	—
`DataChunks`	—
`Index`	—
`Buffer`	—
`Length`	—
`Flags`	—
`Error`	—

Event ID 707 — %1: SSL Encryption Complete (SSLIOContext %2) (ErrorCode: %10) Context Handle(%3:%4) (DataChunks: %5) (Index: %6) (InBuffer: %7[%8]) (Flags %9).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Encryption Complete (SSLIOContext %2) (ErrorCode: %10) Context Handle(%3:%4) (DataChunks: %5) (Index: %6) (InBuffer: %7[%8]) (Flags %9)

Fields

Name	Description
`Connection`	—
`SslIOContext`	—
`CredHandleHigh`	—
`CredHandleLow`	—
`DataChunks`	—
`Index`	—
`Buffer`	—
`Length`	—
`Flags`	—
`Error`	—

Event ID 708 — %1: SSL Encryption Failed (SSLIOContext %2) (ErrorCode: %10) Context Handle(%3:%4) (DataChunks: %5) (Index: %6) (Flags %9).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Encryption Failed (SSLIOContext %2) (ErrorCode: %10) Context Handle(%3:%4) (DataChunks: %5) (Index: %6) (Flags %9)

Fields

Name	Description
`Connection`	—
`SslIOContext`	—
`CredHandleHigh`	—
`CredHandleLow`	—
`DataChunks`	—
`Index`	—
`Buffer`	—
`Length`	—
`Flags`	—
`Error`	—

Event ID 709 — %1: SSL Encryption Details (SSLIOContext %2) Context Handle(%3:%4) (DataChunks: %5) (Index: %6) (OutBuffer: %7[%8]) (Flags %9) Data:%10.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Encryption Details (SSLIOContext %2) Context Handle(%3:%4) (DataChunks: %5) (Index: %6) (OutBuffer: %7[%8]) (Flags %9) Data:%10

Fields

Name	Description
`Connection`	—
`SslIOContext`	—
`CredHandleHigh`	—
`CredHandleLow`	—
`DataChunks`	—
`Index`	—
`Buffer`	—
`Length`	—
`Flags`	—
`Data`	—

Event ID 710 — %1: SSL Queue Send Entity (SSLIOContext %2) (DataChunks: %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Queue Send Entity (SSLIOContext %2) (DataChunks: %3) (RequestDisconnect? %4)

Fields

Name	Description
`Connection`	—
`SslIOContext`	—
`DataChunks`	—
`RequestDisconnect`	—
`Error`	—

Event ID 711 — %1: SSL Send Entity Complete (SSLIOContext: %2) (Error: %5) (DataChunks: %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Send Entity Complete (SSLIOContext: %2) (Error: %5) (DataChunks: %3) (RequestDisconnect? %4)

Fields

Name	Description
`Connection`	—
`SslIOContext`	—
`DataChunks`	—
`RequestDisconnect`	—
`Error`	—

Event ID 712 — %1: SSL Cert Validation - (Error: %6) Context Handle(%2:%3) (IgnoredServerCertErrors %4) (CertErrors %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Cert Validation - (Error: %6) Context Handle(%2:%3) (IgnoredServerCertErrors %4) (CertErrors %5)

Fields

Name	Description
`Connection`	—
`ContextHandleHigh`	—
`ContextHandleLow`	—
`IgnoredServerCertErrors`	—
`ServerCertErrors`	—
`Error`	—
`Reason`	—

Event ID 713 — %1: SSL Cert Validation Failure - %7 (Error: %6) Context Handle(%2:%3) (IgnoredServerCertErrors %4) (CertErrors %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Cert Validation Failure - %7 (Error: %6) Context Handle(%2:%3) (IgnoredServerCertErrors %4) (CertErrors %5)

Fields

Name	Description
`Connection`	—
`ContextHandleHigh`	—
`ContextHandleLow`	—
`IgnoredServerCertErrors`	—
`ServerCertErrors`	—
`Error`	—
`Reason`	—

Event ID 720 — %1: SSL Queue Recv Entity Data Chunk (SSLIOContext %2) (DataChunks: %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Queue Recv Entity Data Chunk (SSLIOContext %2) (DataChunks: %3)

Fields

Name	Description
`Connection`	—
`SslIOContext`	—
`DataChunks`	—

Event ID 721 — %1: SSL Filling Up Recv Entity Data Chunk (SSLIOContext: %2) (DataChunks: %3) (PlainData %4[%5]) (Information: %6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Filling Up Recv Entity Data Chunk (SSLIOContext: %2) (DataChunks: %3) (PlainData %4[%5]) (Information: %6)

Fields

Name	Description
`Connection`	—
`SslIOContext`	—
`DataChunks`	—
`PlainData`	—
`PlainDataLength`	—
`Information`	—
`Error`	—

Event ID 722 — %1: SSL Decryption - Context Handle(%2:%3) (Buffer %4[%5/%6]) (PlainData %7[%8]).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Decryption - Context Handle(%2:%3) (Buffer %4[%5/%6]) (PlainData %7[%8])

Fields

Name	Description
`Connection`	—
`ContextHandleHigh`	—
`ContextHandleLow`	—
`Buffer`	—
`BufferLengthData`	—
`BufferLengthRemaining`	—
`PlainData`	—
`PlainDataLength`	—
`SecStatus`	—
`Error`	—

Event ID 723 — %1: SSL Decryption Complete (SecStatus %9) (Error %10) Context Handle(%2:%3) (Buffer %4[%5/%6]) (PlainData %7[%8]).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Decryption Complete (SecStatus %9) (Error %10) Context Handle(%2:%3) (Buffer %4[%5/%6]) (PlainData %7[%8])

Fields

Name	Description
`Connection`	—
`ContextHandleHigh`	—
`ContextHandleLow`	—
`Buffer`	—
`BufferLengthData`	—
`BufferLengthRemaining`	—
`PlainData`	—
`PlainDataLength`	—
`SecStatus`	—
`Error`	—

Event ID 724 — %1: SSL Receive Buffer Posting Receive (DataChunk %2) (Buffer %3[%4/%5]).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Receive Buffer Posting Receive (DataChunk %2) (Buffer %3[%4/%5])

Fields

Name	Description
`Connection`	—
`DataChunks`	—
`Buffer`	—
`Consumed`	—
`Available`	—
`Information`	—
`Error`	—

Event ID 725 — %1: SSL Receive Buffer Receive Complete (DataChunk %2) (Error %7) (Information %6) (Buffer %3[%4/%5]).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Receive Buffer Receive Complete (DataChunk %2) (Error %7) (Information %6) (Buffer %3[%4/%5])

Fields

Name	Description
`Connection`	—
`DataChunks`	—
`Buffer`	—
`Consumed`	—
`Available`	—
`Information`	—
`Error`	—

Event ID 726 — %1: SSL Receive Buffer Details: (Buffer %2[%3/%4]) Data: %5.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Receive Buffer Details: (Buffer %2[%3/%4]) Data: %5

Fields

Name	Description
`Connection`	—
`Buffer`	—
`BufferLengthData`	—
`BufferLengthRemaining`	—
`Data`	—
`DummyWorkaroundVal`	—

Event ID 727 — %1: SSL Receive Buffer Posting Receive (Buffer %2) (NewBuffer: %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL Receive Buffer Posting Receive (Buffer %2) (NewBuffer: %3)

Fields

Name	Description
`Connection`	—
`OldBuffer`	—
`NewBuffer`	—

Event ID 728 — %1: SSL AcquireCredentialsHandle - (EnabledProtocols %2) (ClientCert %3) (EnableRevertToSelfClientCertificate %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL AcquireCredentialsHandle - (EnabledProtocols %2) (ClientCert %3) (EnableRevertToSelfClientCertificate %4)

Fields

Name	Description
`Connection`	—
`EnabledProtocols`	—
`SSLClientCert`	—
`EnableRevertToSelfClientCertificate`	—
`CipherConfig`	—
`CredHandleHigh`	—
`CredHandleLow`	—
`Result`	—

Event ID 729 — %1: SSL AcquireCredentialsHandle returned - (%7) Credential Handle(%5:%6) (EnabledProtocols %2) (ClientCert %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL AcquireCredentialsHandle returned - (%7) Credential Handle(%5:%6) (EnabledProtocols %2) (ClientCert %3) (EnableRevertToSelfClientCertificate %4)

Fields

Name	Description
`Connection`	—
`EnabledProtocols`	—
`SSLClientCert`	—
`EnableRevertToSelfClientCertificate`	—
`CipherConfig`	—
`CredHandleHigh`	—
`CredHandleLow`	—
`Result`	—

Event ID 730 — %1: SSL AcquireCredentialsHandle failed - (%7) (EnabledProtocols %2) (ClientCert %3) (EnableRevertToSelfClientCertificate %4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: SSL AcquireCredentialsHandle failed - (%7) (EnabledProtocols %2) (ClientCert %3) (EnableRevertToSelfClientCertificate %4)

Fields

Name	Description
`Connection`	—
`EnabledProtocols`	—
`SSLClientCert`	—
`EnableRevertToSelfClientCertificate`	—
`CipherConfig`	—
`CredHandleHigh`	—
`CredHandleLow`	—
`Result`	—

Event ID 731 — Failed to create HTTP/3 API session due to TLS 1.

Provider: Microsoft-Windows-WebIO
Channel: Operational

Message

Failed to create HTTP/3 API session due to TLS 1.3 disabled - Error %1

Fields

Name	Description
`Error`	—

Event ID 900 — %1: WebCompleteProtocolUpgrade completed successfully.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCompleteProtocolUpgrade completed successfully. (Handle %2) (Request %3[%4]) (Session %5[%6])

Fields

Name	Description
`ProtocolObject`	—
`ProtocolHandle`	—
`Request`	—
`RequestHandle`	—
`Session`	—
`SessionHandle`	—
`Error`	—

Event ID 901 — %1: WebCompleteProtocolUpgrade failed with error: %7.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCompleteProtocolUpgrade failed with error: %7. (Handle %2) (Request %3[%4]) (Session %5[%6])

Fields

Name	Description
`ProtocolObject`	—
`ProtocolHandle`	—
`Request`	—
`RequestHandle`	—
`Session`	—
`SessionHandle`	—
`Error`	—

Event ID 902 — %1: WebProtocolCancelHandle (Handle: %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebProtocolCancelHandle (Handle: %2)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`Error`	—

Event ID 903 — %1: WebProtocolCancelHandle Complete (Error: %3) (Handle: %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebProtocolCancelHandle Complete (Error: %3) (Handle: %2)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`Error`	—

Event ID 904 — %1: WebCloseProtocolHandle called (Handle %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCloseProtocolHandle called (Handle %2)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Flags`	—
`Error`	—

Event ID 905 — %1: WebCloseProtocolHandle completed (Error %4) (Handle %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebCloseProtocolHandle completed (Error %4) (Handle %2)

Fields

Name	Description
`ApiObject`	—
`ApiHandle`	—
`Flags`	—
`Error`	—

Event ID 906 — %1: Set Protocol Option %3 (Handle %2) (Error %6) (Length %4) (Value %5).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Set Protocol Option %3 (Handle %2) (Error %6) (Length %4) (Value %5)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Option`	—
`Length`	—
`Value`	—
`Error`	—

Event ID 907 — %1: WebProtocolSendData (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebProtocolSendData (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`DataChunks`	—
`DataChunkCount`	—
`CompletionContext`	—
`Error`	—

Event ID 908 — %1: WebProtocolSendData Inline Completion (Handle: %2) (Error: %7) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebProtocolSendData Inline Completion (Handle: %2) (Error: %7) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`DataChunks`	—
`DataChunkCount`	—
`CompletionContext`	—
`Error`	—

Event ID 909 — %1: Completing WebProtocolSendData (Handle: %2) (Error: %3) CompletionContext (%4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completing WebProtocolSendData (Handle: %2) (Error: %3) CompletionContext (%4)

Fields

Name	Description
`ProtocolObject`	—
`Handle`	—
`Context`	—
`Error`	—
`Information`	—

Event ID 910 — %1: Completing WebProtocolSendData Complete (Handle: %2) (Error: %3) CompletionContext (%4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completing WebProtocolSendData Complete (Handle: %2) (Error: %3) CompletionContext (%4)

Fields

Name	Description
`ProtocolObject`	—
`Handle`	—
`Context`	—
`Error`	—
`Information`	—

Event ID 911 — %1: WebProtocolReceiveData (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebProtocolReceiveData (Handle: %2) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`DataChunks`	—
`DataChunkCount`	—
`CompletionContext`	—
`Error`	—

Event ID 912 — %1: WebProtocolReceiveData Inline Completion (Handle: %2) (Error: %7) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: WebProtocolReceiveData Inline Completion (Handle: %2) (Error: %7) (Flags: %3) (DataChunks %4 [%5]) CompletionContext (%6)

Fields

Name	Description
`Request`	—
`RequestHandle`	—
`Flags`	—
`DataChunks`	—
`DataChunkCount`	—
`CompletionContext`	—
`Error`	—

Event ID 913 — %1: Completing WebProtocolReceiveData (Handle: %2) (Error: %3) CompletionContext (%4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completing WebProtocolReceiveData (Handle: %2) (Error: %3) CompletionContext (%4)

Fields

Name	Description
`ProtocolObject`	—
`Handle`	—
`Context`	—
`Error`	—
`Information`	—

Event ID 914 — %1: Completing WebProtocolReceiveData Complete (Handle: %2) (Error: %3) CompletionContext (%4).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: Completing WebProtocolReceiveData Complete (Handle: %2) (Error: %3) CompletionContext (%4)

Fields

Name	Description
`ProtocolObject`	—
`Handle`	—
`Context`	—
`Error`	—
`Information`	—

Event ID 2100 — %1: =====Request Initialize===================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Request Initialize===================

Fields

Name	Description
`Context`	—

Event ID 2101 — %1: =====Query Endpoints======================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Query Endpoints======================

Fields

Name	Description
`Context`	—

Event ID 2102 — %1: =====Waiting For Available Connection=====.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Waiting For Available Connection=====

Fields

Name	Description
`Context`	—

Event ID 2111 — %1: =====Request Connect======================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Request Connect======================

Fields

Name	Description
`Context`	—

Event ID 2112 — %1: =====Name Resolution======================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Name Resolution======================

Fields

Name	Description
`Context`	—

Event ID 2113 — %1: =====TCP Connect==========================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====TCP Connect==========================

Fields

Name	Description
`Context`	—

Event ID 2114 — %1: =====SSL Negotiation======================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====SSL Negotiation======================

Fields

Name	Description
`Context`	—

Event ID 2120 — %1: =====Generate Headers=====================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Generate Headers=====================

Fields

Name	Description
`Context`	—

Event ID 2121 — %1: =====Send Headers=========================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Send Headers=========================

Fields

Name	Description
`Context`	—

Event ID 2122 — %1: =====Send Entity==========================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Send Entity==========================

Fields

Name	Description
`Context`	—

Event ID 2123 — %1: =====Send Complete========================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Send Complete========================

Fields

Name	Description
`Context`	—

Event ID 2130 — %1: =====Receive Headers======================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Receive Headers======================

Fields

Name	Description
`Context`	—

Event ID 2131 — %1: =====Receive Entity=======================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Receive Entity=======================

Fields

Name	Description
`Context`	—

Event ID 2132 — %1: =====Receive Complete=====================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Receive Complete=====================

Fields

Name	Description
`Context`	—

Event ID 2140 — %1: =====Request Restart======================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Request Restart======================

Fields

Name	Description
`Context`	—

Event ID 2141 — %1: =====Request Done=========================.

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%1: =====Request Done=========================

Fields

Name	Description
`Context`	—

Event ID 59992 — Restore Thread Token %1 (Error: %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

Restore Thread Token %1 (Error: %2)

Fields

Name	Description
`Token`	—
`Error`	—

Event ID 59993 — Set Thread Token %1 (OldToken %2) (Error: %3).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

Set Thread Token %1 (OldToken %2) (Error: %3)

Fields

Name	Description
`Token`	—
`OldToken`	—
`Error`	—

Event ID 59994 — Get Thread Token %1 (Error: %3) (SID: %2).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

Get Thread Token %1 (Error: %3) (SID: %2)

Fields

Name	Description
`Token`	—
`SID`	—
`Error`	—

Event ID 59995 — Canceling %2 Thread Action (Context: %1).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

Canceling %2 Thread Action (Context: %1)

Fields

Name	Description
`Context`	—
`EtwQueueActionType`	—

Event ID 59996 — Queue %2 Thread Action (Context: %1).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

Queue %2 Thread Action (Context: %1)

Fields

Name	Description
`Context`	—
`EtwQueueActionType`	—

Event ID 59997 — Stopping %2 Thread Action (Context: %1).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

Stopping %2 Thread Action (Context: %1)

Fields

Name	Description
`Context`	—
`EtwQueueActionType`	—

Event ID 59998 — Starting %2 Thread Action (Context: %1).

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

Starting %2 Thread Action (Context: %1)

Fields

Name	Description
`Context`	—
`EtwQueueActionType`	—

Event ID 59999 —

Provider: Microsoft-Windows-WebIO
Channel: Diagnostic

Message

%2

Fields

Name	Description
`Length`	—
`Message`	—