Microsoft-Windows-Runtime-WebAPI

71 events across 1 channel

Event ID	Title	Channel
1	Async operation %1 at %2 started.	Tracing
2	Async operation %1 at %2 failed to start.	Tracing
3	Async operation %1 at %2 completed successfully.	Tracing
4	Async operation %1 at %2 failed with error code %3: %4.	Tracing
5	Async operation %1 at %2 was cancelled.	Tracing
6	Async operation %1 at %2 was closed.	Tracing
7	Async operation %1 at %2 called completion callback at %3.	Tracing
8	Async operation %1 at %2 called progress callback at %3.	Tracing
9	Async operation %1 at %2 failed to remove handler from GIT.	Tracing
10	Async operation %1 at %2 failed to register handler at GIT.	Tracing
11	Async operation %1 at %2 failed to retrieve handler from GIT.	Tracing
12	Failed to parse URI '.	Tracing
13	Failed to create URI with base URI '.	Tracing
14	Add HTTP header '.	Tracing
15	Start to connect to '.	Tracing
16	Start to connect to '.	Tracing
17	Failed to connect to '.	Tracing
18	Opening request to '.	Tracing
19	Failed to open request to '.	Tracing
20	Request context %1 has request handle %2 to '%3'.	Tracing
21	Set HTTP send and receive timeout to %2ms on request handle %1.	Tracing
22	Start to send to request handle %1 with content length %2.	Tracing
23	Request handle %1 completed synchronously.	Tracing
24	Request context %1 completed send asynchronously.	Tracing
25	Writing %2 bytes to request handle %1.	Tracing
26	Failed to send entity body to request handle %1.	Tracing
27	Sent HTTP request at request handle %1: %2.	Tracing
28	Start to receive response from request handle %1.	Tracing
29	Received HTTP response from request handle %1 with status code %2 and status …	Tracing
30	Receive HTTP response from request handle %1: %2.	Tracing
31	Failed to receive HTTP response from request handle %1.	Tracing
32	Request context %1 received HTTP response of %2 bytes, which is over the %3 …	Tracing
33	Request context %1 resubmiting the request.	Tracing
34	Reusing the request handle %1 for server '%2'.	Tracing
35	Request context %1 was aborted.	Tracing
36	Progress to '.	Tracing
37	HTTP request to '.	Tracing
38	Async operation %1 at %2 failed to process HTTP response '%3'.	Tracing
39	%1::%2 is called.	Tracing
40	%1::%2 returned successfully.	Tracing
41	%1::%2 failed with HRESULT %3: %4.	Tracing
42	Start downloading category document at '.	Tracing
43	Category document downloaded successfully at '.	Tracing
44	Failed to download category document at '.	Tracing
45	Failed to download category document at '.	Tracing
46	Failed to parse category document downloaded from '.	Tracing
47	Required element '.	Tracing
48	Required attribute '.	Tracing
49	Duplicated element '.	Tracing
50	Required element '.	Tracing
51	Required attribute '.	Tracing
52	The parsed 'feed' element does not have an 'author' element.	Tracing
53	Multiple '.	Tracing
54	Ignore the 'entry' element found in 'source' element.	Tracing
55	The 'entry' element does not have a 'content' element or a 'link' element with …	Tracing
56	The 'item' element is missing both 'title' and 'description' elements.	Tracing
57	The 'link' element with rel='enclosure' is missing 'length' attribute.	Tracing
58	Unexpected child element is found in element with XML.	Tracing
59	Unexpected 'type' attribute '.	Tracing
60	Unexpected 'type' attribute '.	Tracing
61	Element '.	Tracing
62	Atom text content with type='xhtml' must have a single child element 'div' in …	Tracing
63	Failed to parse date time '.	Tracing
64	Failed to parse integer '.	Tracing
65	Failed to parse document: '.	Tracing
66	Failed to create attribute node.	Tracing
67	Failed to create element node.	Tracing
68	Failed to add attribute '.	Tracing
69	Failed to parse JSON string '.	Tracing
70	The JSON string exceeded the maximum allowed depth %1.	Tracing
71	Handle %1: HTTP/2 enabled.	Tracing

Event ID 1 — Async operation %1 at %2 started.

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

Message

Async operation %1 at %2 started.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

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

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

Message

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

Fields

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

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

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

Message

Async operation %1 at %2 completed successfully.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

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

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

Message

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

Fields

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

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

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

Message

Async operation %1 at %2 was cancelled.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

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

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

Message

Async operation %1 at %2 was closed.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 7 — Async operation %1 at %2 called completion callback at %3.

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

Message

Async operation %1 at %2 called completion callback at %3.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—
`callback`	—

Event ID 8 — Async operation %1 at %2 called progress callback at %3.

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

Message

Async operation %1 at %2 called progress callback at %3.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—
`callback`	—

Event ID 9 — Async operation %1 at %2 failed to remove handler from GIT.

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

Message

Async operation %1 at %2 failed to remove handler from GIT. The error code is %3: %4

Fields

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

Event ID 10 — Async operation %1 at %2 failed to register handler at GIT.

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

Message

Async operation %1 at %2 failed to register handler at GIT. The error code is %3: %4

Fields

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

Event ID 11 — Async operation %1 at %2 failed to retrieve handler from GIT.

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

Message

Async operation %1 at %2 failed to retrieve handler from GIT. The error code is %3: %4

Fields

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

Event ID 12 — Failed to parse URI '.

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

Message

Failed to parse URI '%1'.

Fields

Name	Description
`uri`	—

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

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

Message

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

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 14 — Add HTTP header '.

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

Message

Add HTTP header '%1: %2'.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 15 — Start to connect to '.

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

Message

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

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 16 — Start to connect to '.

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

Message

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

Fields

Name	Description
`uri`	—

Event ID 17 — Failed to connect to '.

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

Message

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

Fields

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

Event ID 18 — Opening request to '.

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

Message

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

Fields

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

Event ID 19 — Failed to open request to '.

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

Message

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

Fields

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

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

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

Message

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

Fields

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

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

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

Message

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

Fields

Name	Description
`obj`	—
`length`	—

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

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

Message

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

Fields

Name	Description
`obj`	—
`length`	—

Event ID 23 — Request handle %1 completed synchronously.

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

Message

Request handle %1 completed synchronously.

Fields

Name	Description
`obj`	—

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

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

Message

Request context %1 completed send asynchronously.

Fields

Name	Description
`obj`	—

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

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

Message

Writing %2 bytes to request handle %1.

Fields

Name	Description
`obj`	—
`length`	—

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

Provider: Microsoft-Windows-Runtime-WebAPI
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 27 — Sent HTTP request at request handle %1: %2.

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

Message

Sent HTTP request at request handle %1: %2

Fields

Name	Description
`obj`	—
`statusDescription`	—

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

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

Message

Start to receive response from request handle %1.

Fields

Name	Description
`obj`	—

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

Provider: Microsoft-Windows-Runtime-WebAPI
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 30 — Receive HTTP response from request handle %1: %2.

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

Message

Receive HTTP response from request handle %1: %2

Fields

Name	Description
`obj`	—
`statusDescription`	—

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

Provider: Microsoft-Windows-Runtime-WebAPI
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 32 — Request context %1 received HTTP response of %2 bytes, which is over the %3 limit.

Provider: Microsoft-Windows-Runtime-WebAPI
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 33 — Request context %1 resubmiting the request.

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

Message

Request context %1 resubmiting the request.

Fields

Name	Description
`obj`	—

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

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

Message

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

Fields

Name	Description
`obj`	—
`statusDescription`	—

Event ID 35 — Request context %1 was aborted.

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

Message

Request context %1 was aborted.

Fields

Name	Description
`obj`	—

Event ID 36 — Progress to '.

Provider: Microsoft-Windows-Runtime-WebAPI
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 37 — HTTP request to '.

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

Message

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

Fields

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

Event ID 38 — Async operation %1 at %2 failed to process HTTP response '%3'.

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

Message

Async operation %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 39 — %1::%2 is called.

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

Message

%1::%2 is called.

Fields

Name	Description
`runtimeClass`	—
`api`	—

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

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

Message

%1::%2 returned successfully.

Fields

Name	Description
`runtimeClass`	—
`api`	—

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

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

Message

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

Fields

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

Event ID 42 — Start downloading category document at '.

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

Message

Start downloading category document at '%1'.

Fields

Name	Description
`uri`	—

Event ID 43 — Category document downloaded successfully at '.

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

Message

Category document downloaded successfully at '%1'.

Fields

Name	Description
`uri`	—

Event ID 44 — Failed to download category document at '.

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

Message

Failed to download category document at '%1'. The error code is %2: %3

Fields

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

Event ID 45 — Failed to download category document at '.

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

Message

Failed to download category document at '%1'. The HTTP status code was %2.

Fields

Name	Description
`uri`	—
`statusCode`	—

Event ID 46 — Failed to parse category document downloaded from '.

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

Message

Failed to parse category document downloaded from '%1'. The error code is %2: %3.

Fields

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

Event ID 47 — Required element '.

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

Message

Required element '%1' is missing.

Fields

Name	Description
`uri`	—

Event ID 48 — Required attribute '.

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

Message

Required attribute '%1' is missing on element '%2'.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 49 — Duplicated element '.

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

Message

Duplicated element '%1' found.

Fields

Name	Description
`uri`	—

Event ID 50 — Required element '.

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

Message

Required element '%1' is missing. Add one with default value.

Fields

Name	Description
`uri`	—

Event ID 51 — Required attribute '.

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

Message

Required attribute '%1' is missing on element '%2'. Add it with empty value.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 52 — The parsed 'feed' element does not have an 'author' element.

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

Message

The parsed 'feed' element does not have an 'author' element.

Event ID 53 — Multiple '.

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

Message

Multiple '%1' elements are found. Use the first and ignore the rest.

Fields

Name	Description
`uri`	—

Event ID 54 — Ignore the 'entry' element found in 'source' element.

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

Message

Ignore the 'entry' element found in 'source' element.

Event ID 55 — The 'entry' element does not have a 'content' element or a 'link' element with rel='alternate'.

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

Message

The 'entry' element does not have a 'content' element or a 'link' element with rel='alternate'. Element XML: %1

Fields

Name	Description
`uri`	—

Event ID 56 — The 'item' element is missing both 'title' and 'description' elements.

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

Message

The 'item' element is missing both 'title' and 'description' elements. Element XML: %1

Fields

Name	Description
`uri`	—

Event ID 57 — The 'link' element with rel='enclosure' is missing 'length' attribute.

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

Message

The 'link' element with rel='enclosure' is missing 'length' attribute. Element XML: %1

Fields

Name	Description
`uri`	—

Event ID 58 — Unexpected child element is found in element with XML.

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

Message

Unexpected child element is found in element with XML: %1

Fields

Name	Description
`uri`	—

Event ID 59 — Unexpected 'type' attribute '.

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

Message

Unexpected 'type' attribute '%1' when 'src' attribute is present. Element XML: %2

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 60 — Unexpected 'type' attribute '.

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

Message

Unexpected 'type' attribute '%1' in Atom text content. Only 'text', 'html' or 'xhtml' is allowed. Element XML: %2

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 61 — Element '.

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

Message

Element '%1' should not contain child element or text. Element XML: %2

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 62 — Atom text content with type='xhtml' must have a single child element 'div' in namespace 'http://www.

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

Message

Atom text content with type='xhtml' must have a single child element 'div' in namespace 'http://www.w3.org/1999/xhtml'.

Fields

Name	Description
`uri`	—

Event ID 63 — Failed to parse date time '.

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

Message

Failed to parse date time '%1'.

Fields

Name	Description
`uri`	—

Event ID 64 — Failed to parse integer '.

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

Message

Failed to parse integer '%1'.

Fields

Name	Description
`uri`	—

Event ID 65 — Failed to parse document: '.

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

Message

Failed to parse document: '%1'.

Fields

Name	Description
`uri`	—

Event ID 66 — Failed to create attribute node.

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

Message

Failed to create attribute node. The attribute '%1' in namespace '%2' is not a valid XML attribute.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 67 — Failed to create element node.

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

Message

Failed to create element node. The element '%1' in namespace '%2' is not a valid XML element.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 68 — Failed to add attribute '.

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

Message

Failed to add attribute '%1' in namespace '%2' in to the element. This may be caused by namespace conflict and may be resolved by setting a different namespace prefix on the attribute name.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 69 — Failed to parse JSON string '.

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

Message

Failed to parse JSON string '%1'. The error happened near %2.

Fields

Name	Description
`uri`	—
`statusCode`	—

Event ID 70 — The JSON string exceeded the maximum allowed depth %1.

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

Message

The JSON string exceeded the maximum allowed depth %1.

Fields

Name	Description
`obj`	—

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

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

Message

Handle %1: HTTP/2 enabled.

Fields

Name	Description
`obj`	—