Microsoft-Windows-Runtime-Networking

76 events across 1 channel

Event ID	Title	Channel
1	%1 at %2 started.	Tracing
2	%1 at %2 failed to start.	Tracing
3	%1 at %2 completed successfully.	Tracing
4	%1 at %2 failed with error code %3: %4.	Tracing
5	%1 at %2 was cancelled.	Tracing
6	%1 at %2 was closed.	Tracing
7	Failed to parse URI '.	Tracing
8	Failed to create URI with base URI '.	Tracing
9	Add HTTP header '.	Tracing
10	Start connect request to '.	Tracing
11	Start connect request to '.	Tracing
12	Failed connect request to '.	Tracing
13	Opening request to '.	Tracing
14	Failed open request to '.	Tracing
15	Request context %1 has request handle %2 to '%3'.	Tracing
16	Set HTTP send and receive timeout to %2ms on request handle %1.	Tracing
17	Start send to request handle %1 with content length %2.	Tracing
18	Request handle %1 completed synchronously.	Tracing
19	Request context %1 completed send asynchronously.	Tracing
20	Writing %2 bytes to request handle %1.	Tracing
21	Failed to send entity body to request handle %1.	Tracing
22	Sent HTTP request at request handle %1: %2.	Tracing
23	Start to receive response from request handle %1.	Tracing
24	Received HTTP response from request handle %1 with status code %2 and status …	Tracing
25	Receive HTTP response from request handle %1: %2.	Tracing
26	Failed to receive HTTP response from request handle %1.	Tracing
27	Request context %1 received HTTP response of %2 bytes, which is over the %3 …	Tracing
28	Request context %1 resubmitting the request.	Tracing
29	Reusing the request handle %1 for server '%2'.	Tracing
30	Request context %1 was aborted.	Tracing
31	Progress to '.	Tracing
32	HTTP request to '.	Tracing
33	%1 at %2 failed to process HTTP response '%3'.	Tracing
34	%1::%2 is called.	Tracing
35	%1::%2 returned successfully.	Tracing
36	%1::%2 failed with HRESULT %3: %4.	Tracing
37	Win32 API %1 failed with error code %2: %3.	Tracing
38	Unable to cancel GetAddrInfoEx with handle %1.	Tracing
39	Unable to cancel DnsQueryEx with handle %1.	Tracing
40	DatagramSocket %1 failed to deliver event and stopped receiving due to error %2: …	Tracing
41	DatagramSocket %1 is raising event with %2 bytes received from sender '%4'.	Tracing
42	DatagramSocket %1 started receiving message at socket %2.	Tracing
43	DatagramSocket %1 failed to start receiving.	Tracing
44	%1 at %2 is trying to receive %3 bytes at socket %4.	Tracing
45	%1 at %2 has received %3 bytes and continues to receive the remaining %4 bytes.	Tracing
46	%1 at %2 received %3 bytes.	Tracing
47	TCP socket %1 is connected: local port = %2; remote IP address: %3; remote port …	Tracing
48	UDP socket %1 is connected to remote address: %3.	Tracing
49	The datagram received by socket %1 from sender '%3' does not contain IP packet …	Tracing
50	%1 at %2 sent %3 bytes.	Tracing
51	%1 at %2 is trying to send %3 bytes at socket %4.	Tracing
52	MessageWebSocket %1 received the close frame from the server.	Tracing
53	MessageWebSocket %1 is raising event with %2 bytes received.	Tracing
54	MessageWebSocket %1 failed to start receiving.	Tracing
55	MessageWebSocket %1 failed to deliver event and stopped receiving due to error …	Tracing
57	WebSocket %1 is sending the close frame.	Tracing
58	WebSocket %1 is receiving the close frame.	Tracing
59	WebSocket %1 I/O operation completed with error.	Tracing
60	WebSocket %1 at %2 sent %3 bytes.	Tracing
61	WebSocket %1 at %2 is trying to send %3 bytes at WebSocket %4.	Tracing
62	%1 is already closed and CompleteDelivery is pending with: outstanding read …	Tracing
63	%1.	Tracing
64	%1.	Tracing
65	%1.	Tracing
66	Socket connection established.	Tracing
67	Proxy lookup for socket connection to '.	Tracing
68	Proxy lookup for socket connection to '.	Tracing
69	Ignored server certificate error count.	Tracing
70	Server certificate thumbprint: '.	Tracing
71	Failed to flush reads and wait for pending I/O to complete with context %1.	Tracing
72	Handle %1: HTTP/2 enabled.	Tracing
73	%1 - Line: %2 Status: %3.	Tracing
74	Async operation %1 at %2 started server custom validation.	Tracing
75	Async operation %1 at %2 waiting for completion of server custom validation.	Tracing
76	Async operation %1 at %2 failed server custom validation.	Tracing
77	Async operation %1 at %2 successfully completed server custom validation.	Tracing

Event ID 1 — %1 at %2 started.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 started.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 2 — %1 at %2 failed to start.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 failed to start. The error code is %3: %4

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—
`errorCode`	—
`hresult`	—

Event ID 3 — %1 at %2 completed successfully.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 completed successfully.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 4 — %1 at %2 failed with error code %3: %4.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 failed with error code %3: %4.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—
`errorCode`	—
`hresult`	—

Event ID 5 — %1 at %2 was cancelled.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 was cancelled.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 6 — %1 at %2 was closed.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 was closed.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 7 — Failed to parse URI '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Failed to parse URI '%1'.

Fields

Name	Description
`uri`	—

Event ID 8 — Failed to create URI with base URI '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Failed to create URI with base URI '%1' and relative URI '%2'.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 9 — Add HTTP header '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Add HTTP header '%1: %2'.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 10 — Start connect request to '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Start connect request to '%1' with credential of '%2'.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 11 — Start connect request to '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Start connect request to '%1' with default credential.

Fields

Name	Description
`uri`	—

Event ID 12 — Failed connect request to '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Failed connect request to '%1' at port %2. The last error is %3: %4

Fields

Name	Description
`uri`	—
`port`	—
`errorCode`	—
`errorMessage`	—

Event ID 13 — Opening request to '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Opening request to '%1' to '%2' with flags %3.

Fields

Name	Description
`str1`	—
`str2`	—
`flags`	—

Event ID 14 — Failed open request to '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Failed open request to '%1'. The last error is %2: %3

Fields

Name	Description
`uri`	—
`port`	—
`errorCode`	—
`errorMessage`	—

Event ID 15 — Request context %1 has request handle %2 to '%3'.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Request context %1 has request handle %2 to '%3'.

Fields

Name	Description
`obj1`	—
`obj2`	—
`uri`	—

Event ID 16 — Set HTTP send and receive timeout to %2ms on request handle %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Set HTTP send and receive timeout to %2ms on request handle %1.

Fields

Name	Description
`obj`	—
`length`	—

Event ID 17 — Start send to request handle %1 with content length %2.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Start send to request handle %1 with content length %2.

Fields

Name	Description
`obj`	—
`length`	—

Event ID 18 — Request handle %1 completed synchronously.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Request handle %1 completed synchronously.

Fields

Name	Description
`obj`	—

Event ID 19 — Request context %1 completed send asynchronously.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Request context %1 completed send asynchronously.

Fields

Name	Description
`obj`	—

Event ID 20 — Writing %2 bytes to request handle %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Writing %2 bytes to request handle %1.

Fields

Name	Description
`obj`	—
`length`	—

Event ID 21 — Failed to send entity body to request handle %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Failed to send entity body to request handle %1. The last error is %2: %3

Fields

Name	Description
`obj`	—
`errorCode`	—
`errorMessage`	—

Event ID 22 — Sent HTTP request at request handle %1: %2.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Sent HTTP request at request handle %1: %2

Fields

Name	Description
`obj`	—
`statusDescription`	—

Event ID 23 — Start to receive response from request handle %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Start to receive response from request handle %1.

Fields

Name	Description
`obj`	—

Event ID 24 — Received HTTP response from request handle %1 with status code %2 and status description '%3'.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Received HTTP response from request handle %1 with status code %2 and status description '%3'.

Fields

Name	Description
`obj`	—
`statusCode`	—
`statusDescription`	—

Event ID 25 — Receive HTTP response from request handle %1: %2.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Receive HTTP response from request handle %1: %2

Fields

Name	Description
`obj`	—
`statusDescription`	—

Event ID 26 — Failed to receive HTTP response from request handle %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Failed to receive HTTP response from request handle %1. The last error is %2: %3

Fields

Name	Description
`obj`	—
`errorCode`	—
`errorMessage`	—

Event ID 27 — Request context %1 received HTTP response of %2 bytes, which is over the %3 limit.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Request context %1 received HTTP response of %2 bytes, which is over the %3 limit.

Fields

Name	Description
`obj`	—
`length`	—
`limit`	—

Event ID 28 — Request context %1 resubmitting the request.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Request context %1 resubmitting the request.

Fields

Name	Description
`obj`	—

Event ID 29 — Reusing the request handle %1 for server '%2'.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Reusing the request handle %1 for server '%2'.

Fields

Name	Description
`obj`	—
`statusDescription`	—

Event ID 30 — Request context %1 was aborted.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Request context %1 was aborted.

Fields

Name	Description
`obj`	—

Event ID 31 — Progress to '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Progress to '%1': %2 bytes sent; %3 total bytes to send; %4 bytes received; %5 total bytes to receive.

Fields

Name	Description
`statusDescription`	—
`int1`	—
`int2`	—
`int3`	—
`int4`	—

Event ID 32 — HTTP request to '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

HTTP request to '%1' completed. The error code is %2: %3

Fields

Name	Description
`uri`	—
`hresult`	—
`errorMessage`	—

Event ID 33 — %1 at %2 failed to process HTTP response '%3'.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 failed to process HTTP response '%3'. The error code is %4: %5

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—
`response`	—
`errorCode`	—
`hresult`	—

Event ID 34 — %1::%2 is called.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1::%2 is called.

Fields

Name	Description
`runtimeClass`	—
`api`	—

Event ID 35 — %1::%2 returned successfully.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1::%2 returned successfully.

Fields

Name	Description
`runtimeClass`	—
`api`	—

Event ID 36 — %1::%2 failed with HRESULT %3: %4.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1::%2 failed with HRESULT %3: %4

Fields

Name	Description
`runtimeClass`	—
`api`	—
`hresult`	—
`errorMessage`	—

Event ID 37 — Win32 API %1 failed with error code %2: %3.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Win32 API %1 failed with error code %2: %3.

Fields

Name	Description
`win32Api`	—
`error`	—
`errorMessage`	—

Event ID 38 — Unable to cancel GetAddrInfoEx with handle %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Unable to cancel GetAddrInfoEx with handle %1. The error code was %2: %3.

Fields

Name	Description
`obj`	—
`errorCode`	—
`errorMessage`	—

Event ID 39 — Unable to cancel DnsQueryEx with handle %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Unable to cancel DnsQueryEx with handle %1. The error code was %2: %3.

Fields

Name	Description
`obj`	—
`errorCode`	—
`errorMessage`	—

Event ID 40 — DatagramSocket %1 failed to deliver event and stopped receiving due to error %2: %3.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

DatagramSocket %1 failed to deliver event and stopped receiving due to error %2: %3.

Fields

Name	Description
`obj`	—
`hresult`	—
`errorMessage`	—

Event ID 41 — DatagramSocket %1 is raising event with %2 bytes received from sender '%4'.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

DatagramSocket %1 is raising event with %2 bytes received from sender '%4'.

Fields

Name	Description
`obj`	—
`bytesRead`	—
`size`	—
`address`	—

Event ID 42 — DatagramSocket %1 started receiving message at socket %2.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

DatagramSocket %1 started receiving message at socket %2.

Fields

Name	Description
`obj`	—
`handle`	—

Event ID 43 — DatagramSocket %1 failed to start receiving.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

DatagramSocket %1 failed to start receiving. The HRESULT was %2: %3.

Fields

Name	Description
`obj`	—
`hresult`	—
`errorMessage`	—

Event ID 44 — %1 at %2 is trying to receive %3 bytes at socket %4.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 is trying to receive %3 bytes at socket %4.

Fields

Name	Description
`asyncOperation`	—
`obj`	—
`length`	—
`handle`	—

Event ID 45 — %1 at %2 has received %3 bytes and continues to receive the remaining %4 bytes.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 has received %3 bytes and continues to receive the remaining %4 bytes.

Fields

Name	Description
`asyncOperation`	—
`obj`	—
`read`	—
`length`	—

Event ID 46 — %1 at %2 received %3 bytes.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 received %3 bytes.

Fields

Name	Description
`asyncOperation`	—
`obj`	—
`length`	—

Event ID 47 — TCP socket %1 is connected: local port = %2; remote IP address: %3; remote port = %4.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

TCP socket %1 is connected: local port = %2; remote IP address: %3; remote port = %4.

Fields

Name	Description
`obj`	—
`port1`	—
`ip`	—
`port2`	—

Event ID 48 — UDP socket %1 is connected to remote address: %3.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

UDP socket %1 is connected to remote address: %3.

Fields

Name	Description
`obj`	—
`size`	—
`address`	—

Event ID 49 — The datagram received by socket %1 from sender '%3' does not contain IP packet information.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

The datagram received by socket %1 from sender '%3' does not contain IP packet information.

Fields

Name	Description
`obj`	—
`size`	—
`address`	—

Event ID 50 — %1 at %2 sent %3 bytes.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 sent %3 bytes.

Fields

Name	Description
`asyncOperation`	—
`obj`	—
`length`	—

Event ID 51 — %1 at %2 is trying to send %3 bytes at socket %4.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 at %2 is trying to send %3 bytes at socket %4.

Fields

Name	Description
`asyncOperation`	—
`obj`	—
`length`	—
`handle`	—

Event ID 52 — MessageWebSocket %1 received the close frame from the server.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

MessageWebSocket %1 received the close frame from the server.

Fields

Name	Description
`obj`	—

Event ID 53 — MessageWebSocket %1 is raising event with %2 bytes received.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

MessageWebSocket %1 is raising event with %2 bytes received.

Fields

Name	Description
`obj`	—
`length`	—

Event ID 54 — MessageWebSocket %1 failed to start receiving.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

MessageWebSocket %1 failed to start receiving. The HRESULT was %2: %3.

Fields

Name	Description
`obj`	—
`hresult`	—
`errorMessage`	—

Event ID 55 — MessageWebSocket %1 failed to deliver event and stopped receiving due to error %2: %3.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

MessageWebSocket %1 failed to deliver event and stopped receiving due to error %2: %3.

Fields

Name	Description
`obj`	—
`hresult`	—
`errorMessage`	—

Event ID 57 — WebSocket %1 is sending the close frame.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

WebSocket %1 is sending the close frame.

Fields

Name	Description
`obj`	—

Event ID 58 — WebSocket %1 is receiving the close frame.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

WebSocket %1 is receiving the close frame. Code: %2; Reason: %3

Fields

Name	Description
`Reason`	1 is receiving the close frame. Code.
`obj`	—
`statusCode`	—
`statusDescription`	—

Event ID 59 — WebSocket %1 I/O operation completed with error.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

WebSocket %1 I/O operation completed with error. The HRESULT was %2: %3.

Fields

Name	Description
`obj`	—
`hresult`	—
`errorMessage`	—

Event ID 60 — WebSocket %1 at %2 sent %3 bytes.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

WebSocket %1 at %2 sent %3 bytes.

Fields

Name	Description
`asyncOperation`	—
`obj`	—
`length`	—

Event ID 61 — WebSocket %1 at %2 is trying to send %3 bytes at WebSocket %4.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

WebSocket %1 at %2 is trying to send %3 bytes at WebSocket %4.

Fields

Name	Description
`asyncOperation`	—
`obj`	—
`length`	—
`handle`	—

Event ID 62 — %1 is already closed and CompleteDelivery is pending with: outstanding read operations: %2.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 is already closed and CompleteDelivery is pending with: outstanding read operations: %2.

Fields

Name	Description
`runtimeClass`	—
`pendingOperations`	—

Event ID 63 — %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1.CompleteDelivery is pending with: outstanding read operations: %2, pending Winsock requests: %3, data available: %4.

Fields

Name	Description
`pending_Winsock_requests`	1.CompleteDelivery is pending with: outstanding read operations.
`data_available`	—
`runtimeClass`	—
`pendingOperations`	—
`winsockPendingOperations`	—
`winsockDataAvailable`	—

Event ID 64 — %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1.Flush is pending with: outstanding write operations: %2.

Fields

Name	Description
`runtimeClass`	—
`pendingOperations`	—

Event ID 65 — %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1.CompleteDelivery is pending with: outstanding read operations: %2.

Fields

Name	Description
`runtimeClass`	—
`pendingOperations`	—

Event ID 66 — Socket connection established.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Socket connection established: %1.

Fields

Name	Description
`Socket_connection_established`	—
`connectorType`	—

Event ID 67 — Proxy lookup for socket connection to '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Proxy lookup for socket connection to '%1' completed successfully: %2.

Fields

Name	Description
`value`	—
`resolutionResult`	—

Event ID 68 — Proxy lookup for socket connection to '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Proxy lookup for socket connection to '%1' completed with error %2: %3

Fields

Name	Description
`value`	—
`errorCode`	—
`errorMessage`	—

Event ID 69 — Ignored server certificate error count.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Ignored server certificate error count: %1

Fields

Name	Description
`Ignored_server_certificate_error_count`	—
`errorCount`	—
`errorList`	—

Event ID 70 — Server certificate thumbprint: '.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Server certificate thumbprint: '%1', certificate error count: %3, contains fatal certificate errors: %2, intermediate certificate count: %5.

Fields

Name	Description
`contains_fatal_certificate_errors`	—
`intermediate_certificate_count`	1', certificate error count.
`certificateThumbprint`	—
`hasFatalError`	—
`errorCount`	—
`errorList`	—
`intermediateCertificatesCount`	—
`intermediateCertificatesList`	—

Event ID 71 — Failed to flush reads and wait for pending I/O to complete with context %1.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Failed to flush reads and wait for pending I/O to complete with context %1. Error was %2: %3.

Fields

Name	Description
`obj`	—
`hresult`	—
`errorMessage`	—

Event ID 72 — Handle %1: HTTP/2 enabled.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Handle %1: HTTP/2 enabled.

Fields

Name	Description
`obj`	—

Event ID 73 — %1 - Line: %2 Status: %3.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

%1 - Line: %2 Status: %3

Fields

Name	Description
`Status`	1 - Line.
`functionName`	—
`lineNumber`	—
`status`	—

Event ID 74 — Async operation %1 at %2 started server custom validation.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Async operation %1 at %2 started server custom validation.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 75 — Async operation %1 at %2 waiting for completion of server custom validation.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Async operation %1 at %2 waiting for completion of server custom validation.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 76 — Async operation %1 at %2 failed server custom validation.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Async operation %1 at %2 failed server custom validation.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 77 — Async operation %1 at %2 successfully completed server custom validation.

Provider: Microsoft-Windows-Runtime-Networking
Channel: Tracing

Message

Async operation %1 at %2 successfully completed server custom validation.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—