Microsoft-Windows-BackgroundTransfer-ContentPrefetcher

18 events across 1 channel

Event ID	Title	Channel
0	The content prefetcher task has started for app %1.	Operational
1	The content prefetcher task has completed for app %1.	Operational
2	Fetch URI %1 started.	Operational
3	Fetch Indirect Content URI %1 started.	Operational
4	Fetch URI %1 completed.	Operational
6	Fetch URI %1 Failed with error %2: %3.	Operational
7	Fetch URI %1 Failed with error: %2.	Operational
8	Fetch Indirect URI %1 responded with Xml data: %2.	Operational
9	Processing Indirect Content XML Document failed.	Operational
10	Fetching %1 Content URIs.	Operational
11	Skipping fetch of URI %1 because the limit has already been exceeded.	Operational
12	The content prefetcher task has completed for app %1 with error %2: %3.	Operational
13	The content prefetcher task has completed for app %1 with error %2.	Operational
14	The content prefetcher task has completed for app %1 with an unspecified error.	Operational
15	The content prefetcher task has completed for app %1 with error %2.	Operational
16	Fetch URI %1 Failed with error: %2.	Operational
17	Fetching %1 Indirect Content URIs.	Operational
18	The fetch of URI %1 was canceled due to timeout.	Operational

Event ID 0 — The content prefetcher task has started for app %1.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

The content prefetcher task has started for app %1

Fields

Name	Description
`appName`	—

Event ID 1 — The content prefetcher task has completed for app %1.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

The content prefetcher task has completed for app %1

Fields

Name	Description
`appName`	—

Event ID 2 — Fetch URI %1 started.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Fetch URI %1 started

Fields

Name	Description
`uri`	—

Event ID 3 — Fetch Indirect Content URI %1 started.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Fetch Indirect Content URI %1 started

Fields

Name	Description
`uri`	—

Event ID 4 — Fetch URI %1 completed.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Fetch URI %1 completed. Status: %2 %3

Fields

Name	Description
`uri`	—
`httpStatusCode`	—
`errorString`	—

Event ID 6 — Fetch URI %1 Failed with error %2: %3.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Fetch URI %1 Failed with error %2: %3

Fields

Name	Description
`uri`	—
`statusCode`	—
`errorString`	—

Event ID 7 — Fetch URI %1 Failed with error: %2.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Fetch URI %1 Failed with error: %2

Fields

Name	Description
`uri`	—
`errorString`	—

Event ID 8 — Fetch Indirect URI %1 responded with Xml data: %2.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Fetch Indirect URI %1 responded with Xml data:
 %2

Fields

Name	Description
`uri`	—
`xmlBlob`	—

Event ID 9 — Processing Indirect Content XML Document failed.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Processing Indirect Content XML Document failed. 
Error code: %1 
Error reason: %2
Source text:%3
Error offset:%4

Fields

Name	Description
`Error_code`	—
`Error_reason`	—
`Source_text`	—
`Error_offset`	—
`statusCode`	—
`errorReason`	—
`sourceText`	—
`errorOffset`	—

Event ID 10 — Fetching %1 Content URIs.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Fetching %1 Content URIs.

Fields

Name	Description
`count`	—

Event ID 11 — Skipping fetch of URI %1 because the limit has already been exceeded.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Skipping fetch of URI %1 because the limit has already been exceeded.

Fields

Name	Description
`uri`	—

Event ID 12 — The content prefetcher task has completed for app %1 with error %2: %3.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

The content prefetcher task has completed for app %1 with error %2: %3

Fields

Name	Description
`appName`	—
`httpStatusCode`	—
`errorString`	—

Event ID 13 — The content prefetcher task has completed for app %1 with error %2.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

The content prefetcher task has completed for app %1 with error %2

Fields

Name	Description
`appName`	—
`errorString`	—

Event ID 14 — The content prefetcher task has completed for app %1 with an unspecified error.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

The content prefetcher task has completed for app %1 with an unspecified error

Fields

Name	Description
`appName`	—

Event ID 15 — The content prefetcher task has completed for app %1 with error %2.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

The content prefetcher task has completed for app %1 with error %2

Fields

Name	Description
`appName`	—
`errorString`	—

Event ID 16 — Fetch URI %1 Failed with error: %2.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Fetch URI %1 Failed with error: %2

Fields

Name	Description
`uri`	—
`statusCode`	—

Event ID 17 — Fetching %1 Indirect Content URIs.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

Fetching %1 Indirect Content URIs.

Fields

Name	Description
`count`	—

Event ID 18 — The fetch of URI %1 was canceled due to timeout.

Provider: Microsoft-Windows-BackgroundTransfer-ContentPrefetcher
Channel: Operational

Message

The fetch of URI %1 was canceled due to timeout.

Fields

Name	Description
`uri`	—