Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider

80 events across 2 channels

Event IDTitleChannel
1000The Windows Scripted Diagnostic Provider API IDiagnosticProvider …Operational
1001The Windows Scripted Diagnostic Provider API IDiagnosticProvider …Operational
1002The Windows Scripted Diagnostic Provider API IDiagnosticProvider …Operational
1003The Windows Scripted Diagnostic Provider API IDiagnosticProvider …Operational
1004The Windows Scripted Diagnostic Provider API IDiagnosticProvider …Operational
1010The Windows Scripted Diagnostic Provider API IDiagnosticProvider Cancel method …Operational
1011The Windows Scripted Diagnostic Provider API IDiagnosticProvider Cancel method …Operational
1012The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to …Operational
1013The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to …Operational
1015The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property …Operational
1016The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property …Operational
1017The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property …Debug
1018The Windows Scripted Diagnostic Provider API IDiagnosticProvider …Debug
2000The diagnostic package index information was successfully loaded from %1.Operational
2001Failed to scan diagnostic package index information from %2, with error (%1).Operational
2002Failed to load the resource (%2;%3) with error code (%1).Operational
3000Sending request to the remote server %1 at the URL path %2.Operational
3001Failed to connect to the remote server %1 at the URL path %2 due to lack of …Operational
3002Failed to connect to the remote server %1 at the URL path %2 with error %3.Operational
3003Timed out while communicating with the remote server %1 at the URL path %2.Operational
3004Timed out waiting for a response from the remote server %1 at the URL path %2.Operational
3005Response from the remote server %1 at the URL path %2 returned the following …Operational
3006Received response from the remote server %1 at the URL path %2.Operational
3007Parsed valid response from the remote server %1 at the URL path %2.Operational
3008Response received from the remote server %1 at the URL path %2 is invalid for …Operational
3009Response received from the remote server %1 at the URL path %2 is malformed.Operational
3010Attempting to send data to remote server using the following proxy …Debug
3011Failed to send data to remote server using the following proxy configuration: …Debug
3012Failed to send data to remote server because list of proxy servers was exhausted …Operational
3013Connection to remote server has been reset or terminated while waiting for a …Operational
3014The following system configuration will be used when querying content providers: …Operational
4000Starting to scan diagnostic package index information from %1.Debug
4001Finished scanning diagnostic package index information from %1.Debug
4006Starting to query content providers for scripted diagnostic content packages.Debug
4007Finished querying content providers for scripted diagnostic content packages …Debug
4008Starting to cancel content providers.Debug
4009Finished cancelling content providers with error code.Debug
4010Starting to cancel local content provider.Debug
4011Finished cancelling local content provider with error code.Debug
4012Starting to cancel remote content provider.Debug
4013Finished cancelling remove content provider with error code.Debug
4014Starting to gather system configuration necessary for scripted diagnostic …Debug
4015Finished gathering system configuration necessary for scripted diagnostic …Debug
4016Started to connect to remote server %1 using URL path %2.Debug
4017Finished connecting to remote server %1 using URL path %2.Debug
4018Sending POST request to the remote server %1 using the URL path: %2 with request …Debug
4019Response received from remote server.Debug
4020Starting to parse response from the remote server %1 POST request to the URL …Debug
4021Finished parsing response from the remote server %1 POST request to the URL …Debug
4022Starting to acquire lock in function %1.Debug
4023Finished acquiring lock in function %1.Debug
4024Starting to add result to Diagnostic Collection.Debug
4025Finished adding result to Diagnostic Collection with error code.Debug
4026Starting to load resource from %1.Debug
4027Finished loading resource from %1.Debug
5000%1 succeeded.Debug
5001%1 succeeded.Debug
5002%1 succeeded.Debug
5004%1 succeeded.Debug
5005%1 succeeded.Debug
5006%1 succeeded.Debug
5008%1 succeeded.Debug
5009%1 succeeded.Debug
5010%1 failed because the system ran out of memory.Debug
5011%1 failed with error (%2) because the input parameter, %3, was NULL.Debug
5012%1 failed with error (%2).Debug
5013%1 succeeded.Debug
5014%1 failed with error (%2) because the index, %3, is out of bounds of the …Debug
5015%1 succeeded.Debug
5016%1 failed with error (%2) because the collection already contains an object of …Debug
5017%1 succeeded.Debug
5018%1 failed with error (%2) because the collection already contains an object of …Operational
5019Local Content Diagnostic Provider search parameter: %1 has value: %2.Debug
5020Search Result includes a diagnostic with the following identifier %1.Debug
5021Deserializing diagnostic from index file %2 failed with error code (%1) because …Operational
5022Debug
5023Debug
5024Debug
5025Debug
5026Deserializing diagnostic failed index file %2 with error code (%1) because the …Operational

Event ID 1000 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method succeeded.  The input Culture/Locale was %1.  The size of the result set was %2.

Fields

NameDescription
UILanguage
ResultSize

Event ID 1001 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed because the system ran out of memory.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed because the system ran out of memory.

Event ID 1002 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method was canceled by the caller.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method was canceled by the caller.

Event ID 1003 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed with error.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed with error (%1).

Fields

NameDescription
Error

Event ID 1004 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed.  The input Culture/Locale, %1, is not a valid Language identifier.

Fields

NameDescription
UILanguage

Event ID 1010 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider Cancel method succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider Cancel method succeeded.

Event ID 1011 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider Cancel method failed with error.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider Cancel method failed with error (%1).

Fields

NameDescription
Error

Event ID 1012 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to cancel the connected diagnostic provider with error.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to cancel the connected diagnostic provider with error (%1).

Fields

NameDescription
Error

Event ID 1013 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to cancel the local diagnostic provider with error.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to cancel the local diagnostic provider with error (%1).

Fields

NameDescription
Error

Event ID 1015 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is being overridden by Group Policy.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is being overridden by Group Policy.  The property will be interpreted as being set to VARIANT_FALSE.

Event ID 1016 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is being overridden by the Administrator through...

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is being overridden by the Administrator through a System Wide Preference.  The property will be interpreted as being set to VARIANT_FALSE.

Event ID 1017 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is set to %1.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is set to %1.

Fields

NameDescription
QueryRemoteServer

Event ID 1018 — The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed because the input IDiagnosticMetadat...

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed because the input IDiagnosticMetadataCollection object was empty.

Event ID 2000 — The diagnostic package index information was successfully loaded from %1.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The diagnostic package index information was successfully loaded from %1.

Fields

NameDescription
IndexPath

Event ID 2001 — Failed to scan diagnostic package index information from %2, with error (%1).

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Failed to scan diagnostic package index information from %2, with error (%1).

Fields

NameDescription
Error
IndexPath

Event ID 2002 — Failed to load the resource (%2;%3) with error code (%1).

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Failed to load the resource (%2;%3) with error code (%1).

Fields

NameDescription
Error
Resource
ResourceId

Event ID 3000 — Sending request to the remote server %1 at the URL path %2.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Sending request to the remote server %1 at the URL path %2.  Contents of the request are: %3.

Fields

NameDescription
Hostname
Url
RequestBody

Event ID 3001 — Failed to connect to the remote server %1 at the URL path %2 due to lack of network access.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Failed to connect to the remote server %1 at the URL path %2 due to lack of network access.

Fields

NameDescription
Hostname
Url

References

Event ID 3002 — Failed to connect to the remote server %1 at the URL path %2 with error %3.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Failed to connect to the remote server %1 at the URL path %2 with error %3.

Fields

NameDescription
Hostname
Url
Error

References

Event ID 3003 — Timed out while communicating with the remote server %1 at the URL path %2.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Timed out while communicating with the remote server %1 at the URL path %2.

Fields

NameDescription
Hostname
Url

Event ID 3004 — Timed out waiting for a response from the remote server %1 at the URL path %2.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Timed out waiting for a response from the remote server %1 at the URL path %2.

Fields

NameDescription
Hostname
Url

References

Event ID 3005 — Response from the remote server %1 at the URL path %2 returned the following error response code: %3.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Response from the remote server %1 at the URL path %2 returned the following error response code: %3.

Fields

NameDescription
Hostname
Url
ResponseCode

Event ID 3006 — Received response from the remote server %1 at the URL path %2.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Received response from the remote server %1 at the URL path %2.

Fields

NameDescription
Hostname
Url

Event ID 3007 — Parsed valid response from the remote server %1 at the URL path %2.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Parsed valid response from the remote server %1 at the URL path %2.

Fields

NameDescription
Hostname
Url

References

Event ID 3008 — Response received from the remote server %1 at the URL path %2 is invalid for the following reason: %3.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Response received from the remote server %1 at the URL path %2 is invalid for the following reason: %3.

Fields

NameDescription
Hostname
Url
Reason

Event ID 3009 — Response received from the remote server %1 at the URL path %2 is malformed.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Response received from the remote server %1 at the URL path %2 is malformed.

Fields

NameDescription
Hostname
Url

Event ID 3010 — Attempting to send data to remote server using the following proxy configuration: Access Type; Proxy Server; Proxy Bypass Server.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Attempting to send data to remote server using the following proxy configuration: Access Type (%1); Proxy Server (%2); Proxy Bypass Server (%3).

Fields

NameDescription
AccessType
Proxy
ProxyBypass

References

Event ID 3011 — Failed to send data to remote server using the following proxy configuration: Access Type; Proxy Server; Proxy Bypass Server because of proxy failure.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Failed to send data to remote server using the following proxy configuration: Access Type (%2); Proxy Server (%3); Proxy Bypass Server (%4) because of proxy failure (%1).

Fields

NameDescription
Error
AccessType
Proxy
ProxyBypass

References

Event ID 3012 — Failed to send data to remote server because list of proxy servers was exhausted without receiving a response.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Failed to send data to remote server because list of proxy servers was exhausted without receiving a response. The error code returned to caller is %1.

Fields

NameDescription
Error

References

Event ID 3013 — Connection to remote server has been reset or terminated while waiting for a response.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Connection to remote server has been reset or terminated while waiting for a response.  The error code returned to the caller is %1.

Fields

NameDescription
Error

Event ID 3014 — The following system configuration will be used when querying content providers: OS Major Version (%1); OS Minor Version (%2); Service Pack Major.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

The following system configuration will be used when querying content providers: OS Major Version (%1); OS Minor Version (%2); Service Pack Major (%3); Service Pack Minor (%4); Build Number (%5); Product Type (%6); Processor Architecture (%7); Culture (%8); System Type (%9); OEM (%10); Model (%11); IsMobilePc (%12); IsInternal (%13); GeoId (%14); Family (%15); OEM SKU (%16); Version (%17); Base Board OEM (%18); Base Board Model (%19); Base Board Version (%20); BIOS Vendor (%21); BIOS Version (%22); BIOS Release Date (%23); BIOS Major Release (%24); BIOS Minor Release (%25); Embedded Controller Firmware Major Release (%26); Embedded Controller Firmware Minor Release (%27).

Fields

NameDescription
OSMajorVersion
OSMinorVersion
ServicePackMajor
ServicePackMinor
BuildNumber
ProductType
ProcessorArchitecture
Culture
SystemType
OEM
Model
IsMobilePc
IsInternal
GeoId
Family
OEMSKU
Version
BaseBoardOEM
BaseBoardModel
BaseBoardVersion
BIOSVendor
BIOSVersion
BIOSReleaseDate
BIOSMajorRelease
BIOSMinorRelease
ECFirmwareMajorRelease
ECFirmwareMinorRelease

Event ID 4000 — Starting to scan diagnostic package index information from %1.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Starting to scan diagnostic package index information from %1.

Fields

NameDescription
IndexPath

Event ID 4001 — Finished scanning diagnostic package index information from %1.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished scanning diagnostic package index information from %1.

Fields

NameDescription
IndexPath

Event ID 4006 — Starting to query content providers for scripted diagnostic content packages.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Starting to query content providers for scripted diagnostic content packages.

Event ID 4007 — Finished querying content providers for scripted diagnostic content packages with error code.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished querying content providers for scripted diagnostic content packages with error code (%1).

Fields

NameDescription
Error

Event ID 4008 — Starting to cancel content providers.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Starting to cancel content providers.

Event ID 4009 — Finished cancelling content providers with error code.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished cancelling content providers with error code (%1).

Fields

NameDescription
Error

Event ID 4010 — Starting to cancel local content provider.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Starting to cancel local content provider.

Event ID 4011 — Finished cancelling local content provider with error code.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished cancelling local content provider with error code (%1).

Fields

NameDescription
Error

Event ID 4012 — Starting to cancel remote content provider.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Starting to cancel remote content provider.

Event ID 4013 — Finished cancelling remove content provider with error code.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished cancelling remove content provider with error code (%1).

Fields

NameDescription
Error

Event ID 4014 — Starting to gather system configuration necessary for scripted diagnostic content package query.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Starting to gather system configuration necessary for scripted diagnostic content package query.

Event ID 4015 — Finished gathering system configuration necessary for scripted diagnostic content package query with error code.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished gathering system configuration necessary for scripted diagnostic content package query with error code (%1).

Fields

NameDescription
Error

Event ID 4016 — Started to connect to remote server %1 using URL path %2.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Started to connect to remote server %1 using URL path %2.

Fields

NameDescription
Hostname
Url

Event ID 4017 — Finished connecting to remote server %1 using URL path %2.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished connecting to remote server %1 using URL path %2.  The operation completed with error %3.

Fields

NameDescription
Hostname
Url
Error

Event ID 4018 — Sending POST request to the remote server %1 using the URL path: %2 with request body: %3.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Sending POST request to the remote server %1 using the URL path: %2 with request body: %3.

Fields

NameDescription
Hostname
Url
RequestBody

Event ID 4019 — Response received from remote server.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Response received from remote server.  The HTTP response was %1.  The operation completed with error %2.

Fields

NameDescription
HttpError
Error

Event ID 4020 — Starting to parse response from the remote server %1 POST request to the URL path: %2 with request body: %3.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Starting to parse response from the remote server %1 POST request to the URL path: %2 with request body: %3.

Fields

NameDescription
Hostname
Url
RequestBody

Event ID 4021 — Finished parsing response from the remote server %1 POST request to the URL path: %2 with request body: %3 with error %4.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished parsing response from the remote server %1 POST request to the URL path: %2 with request body: %3 with error %4.

Fields

NameDescription
Hostname
Url
RequestBody
Error

Event ID 4022 — Starting to acquire lock in function %1.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Starting to acquire lock in function %1.

Fields

NameDescription
Method

Event ID 4023 — Finished acquiring lock in function %1.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished acquiring lock in function %1.

Fields

NameDescription
Method

Event ID 4024 — Starting to add result to Diagnostic Collection.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Starting to add result to Diagnostic Collection.

Event ID 4025 — Finished adding result to Diagnostic Collection with error code.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished adding result to Diagnostic Collection with error code (%1).

Fields

NameDescription
Error

Event ID 4026 — Starting to load resource from %1.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Starting to load resource from %1.

Fields

NameDescription
Resource

Event ID 4027 — Finished loading resource from %1.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Finished loading resource from %1.

Fields

NameDescription
Resource

Event ID 5000 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.

Fields

NameDescription
Method

Event ID 5001 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.  The corresponding object property was set to %2.

Fields

NameDescription
Method
Value

Event ID 5002 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.  The corresponding object property was set to %2.

Fields

NameDescription
Method
Value

Event ID 5004 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.  The corresponding object property was set to %2.

Fields

NameDescription
Method
Value

Event ID 5005 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.  The output parameter was set to %2.

Fields

NameDescription
Method
Value

Event ID 5006 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.  The output parameter was set to %2.

Fields

NameDescription
Method
Value

Event ID 5008 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.  The output parameter was set to %2.

Fields

NameDescription
Method
Value

Event ID 5009 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.  The output parameter was set to %2.

Fields

NameDescription
Method
Value

Event ID 5010 — %1 failed because the system ran out of memory.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 failed because the system ran out of memory.

Fields

NameDescription
Method

Event ID 5011 — %1 failed with error (%2) because the input parameter, %3, was NULL.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 failed with error (%2) because the input parameter, %3, was NULL.

Fields

NameDescription
Method
Error
Parameter

Event ID 5012 — %1 failed with error (%2).

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 failed with error (%2).

Fields

NameDescription
Method
Error

Event ID 5013 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.  The output parameter was set to the item in the collection at index %2.

Fields

NameDescription
Method
Value

Event ID 5014 — %1 failed with error (%2) because the index, %3, is out of bounds of the enumeration or the enumeration is empty.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 failed with error (%2) because the index, %3, is out of bounds of the enumeration or the enumeration is empty.

Fields

NameDescription
Method
Error
Index

Event ID 5015 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.  The object was added to the collection at index %2.  The new size of the collection is %3.

Fields

NameDescription
Method
Index
Count

Event ID 5016 — %1 failed with error (%2) because the collection already contains an object of type, %3, with value, %4.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 failed with error (%2) because the collection already contains an object of type, %3, with value, %4.

Fields

NameDescription
Method
Error
Type
Value

Event ID 5017 — %1 succeeded.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

%1 succeeded.  The size of the collection increased by %2 object(s).  The new size of the collection is %3.

Fields

NameDescription
Method
ItemsAdded
Count

Event ID 5018 — %1 failed with error (%2) because the collection already contains an object of with identifier, %3, and publisher, %4, with a greater version (%5).

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

%1 failed with error (%2) because the collection already contains an object of with identifier, %3, and publisher, %4, with a greater version (%5).

Fields

NameDescription
Method
Error
Id
Publisher
Version

Event ID 5019 — Local Content Diagnostic Provider search parameter: %1 has value: %2.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Local Content Diagnostic Provider search parameter: %1 has value: %2.

Fields

NameDescription
Parameter
Value

Event ID 5020 — Search Result includes a diagnostic with the following identifier %1.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Message

Search Result includes a diagnostic with the following identifier %1.  The publisher of the Diagnostic is %2. The version of the Diagnostic is %3.  The URL for the diagnostic is: %4.

Fields

NameDescription
Id
Publisher
Version
Url

Event ID 5021 — Deserializing diagnostic from index file %2 failed with error code (%1) because the XML does not represent a valid Diagnostic.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Deserializing diagnostic from index file %2 failed with error code (%1) because the XML does not represent a valid Diagnostic.

Fields

NameDescription
Error
IndexPath

Event ID 5022 —

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Fields

NameDescription
Name
Address

Event ID 5023 —

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Fields

NameDescription
Name
Address

Event ID 5024 —

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Fields

NameDescription
Name
Address
RefCount

Event ID 5025 —

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Debug

Fields

NameDescription
Name
Address
RefCount

Event ID 5026 — Deserializing diagnostic failed index file %2 with error code (%1) because the XML does not contain valid XML.

Provider
Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
Channel
Operational

Message

Deserializing diagnostic failed index file %2 with error code (%1) because the XML does not contain valid XML.

Fields

NameDescription
Error
IndexPath