Microsoft-Windows-Iphlpsvc-Trace

193 events across 5 channels

Event ID	Title	Channel
4051	Teredo %2: Forwarding %3 packet from %4 to %5.	Trace
4052	Teredo server: Received %2 from %3 , Sending %4 to %5.	Trace
4053	Teredo %2 received %3, Mapping to %4.	Trace
4054	Teredo client in state %1,received bad or invalid packet with %2.	Trace
4055	Teredo client state change: Previous state %1, Current state %2.	Trace
4056	Teredo client Sending %1 packet.	Trace
4057	Starting Teredo Offload with: LocalV6:%3 RemoteV6:%4 LocalV4:%5 RemoteV4:%6 …	Trace
4058		Trace
4059	Teredo server received bad or invalid packet with %1.	Trace
4060	%2 %3 mapping: %4.	Trace
4061	Teredo %2 transmitting packet to %3.	Trace
4062	Teredo %2 received %3 packet from %4.	Trace
4063	Teredo %2 received %3, sending %4 to %5.	Trace
4064	Teredo %2 received %3, sending %4 to %5.	Trace
4065	Teredo %2 received packet from %3.	Trace
4066	Teredo %2 received packet type %3; with source %4 destination %5 target %6.	Trace
4067	Teredo %2 transmitting %3 packet to %4.	Trace
4068	Teredo connectivity initiated by %1.	System
4069	%1 using Teredo connectivity.	System
4070	%1 no longer using Teredo connectivity.	System
4071	Teredo connectivity ended by %1.	System
4150	%1 interface %2 %3.	Trace
4151	ISATAP link local address for interface %2 was %3, is %4.	Trace
4152	ISATAP potential router interface list has changed.	Trace
4153	%2: Found route to %3 from interface %4.	Trace
4154	%2: For %3, router %4 is %5.	Debug
4155	For %2, router name: %3, is %4.	Debug
4157	%1 protocol started.	Trace
4158	%1 protocol stopped.	Trace
4159	%1 protocol initialized.	Trace
4160	%1 protocol uninitialized.	Trace
4161	ISATAP found interface %1 to reuse.	Trace
4162	%2: interface %5 address %4 %3.	Trace
4163	6to4: Updating route %2/%3 interface %4 metric %5 lifetime %6/%7 publish %8.	Trace
4164	6to4: Configuring interface %1 with following parameters: ICS PrivateInterface = …	Trace
4165	6to4: Routing State changed to %1 from %2.	Trace
4166	6to4: For interface %1, IPv4 address %2 was chosen for link layer address.	Trace
4167	%1:Change notification for compartment %2, HaveGlobalIPv6Address = %3, ICS …	Trace
4168	6to4: Configuring interface %1 in compartment %2 with routing state %3.	Trace
4169	Configuring interface %2 with address %3, lifetime %4, prefix %5 suffix %6.	Trace
4170	%1 Callback for %2.	Trace
4171	Teredo Client failed to start due to the following reason.	Trace
4172	Teredo Client stopped due to the following reason.	Trace
4173	6TO4 failed to start due to the following reason.	Trace
4174	ISATAP router address %1 was set with status %2.	Trace
4175	NLM found that the network is %1.	Trace
4176	Port-Prediction complete with: V4Addr:%1 V4Port:%2 LowerValue:%3 UpperValue:%4 …	Trace
4177	Teredo operation in action.	Trace
4178	Teredo operation started.	Trace
4179	Teredo operation ended.	Trace
4180	Teredo operation failed.	Trace
5000	IPHTTPS: InterfaceName:%1 InterfaceType:%2 RegistryState:%3 CurrentState:%4 …	Trace
5001	IPHTTPS: Interface %1 installation failed.	Trace
5002	IPHTTPS: Interface %1 update link address.	Trace
5003	IPHTTPS: Client interface %1 configured to use certificate %2 with preference = …	Trace
5004	IPHTTPS: Interface %1 cleanup complete.	Trace
5005	IPHTTPS: Interface %1 firewall exception added.	Trace
5006	IPHTTPS: Interface %1 performance counters added.	Trace
5007	IPHTTPS: Interface %1 Memory allocation failed.	Trace
5008	IPHTTPS: Interface %1 Tunnel device IO failed: %2.	Trace
5009	IPHTTPS: Interface %1 reusing an previously installed interface.	Trace
5010	IPHTTPS: Interface %1 deleted.	Trace
5011	IPHTTPS: Interface %1 media connect indication: Status= %2.	Trace
5012	IPHTTPS: Interface %1 media disconnect indication: Status= %2.	Trace
5013	IPHTTPS: Interface %1 deactivated.	Trace
5014	IPHTTPS: Adapter %1 uninstalled as it does not have associated registry …	Trace
5015	IPHTTPS: V6 Address change callback.	Trace
5016	IPHTTPS: Global connectivity state change.	Trace
5017	IPHTTPS: Interface callback.	Trace
5018	IPHTTPS: Interface %1 activated.	Trace
5019	IPHTTPS: Corp connectivity timer started.	Trace
5020	IPHTTPS: Corp connectivity timeout.	Trace
5021	IPHTTPS: Network change.	Trace
5022	IPHTTPS: Teredo dormancy change.	Trace
5023	IPHTTPS: Initialization failed.	Trace
5024	IPHTTPS: ND Packet.	Trace
5025	IPHTTPS: Client interface is being shutdown.	Trace
5026	IPHTTPS: Client IO Reference %1.	Trace
5027	IPHTTPS: Client IO Dereference %1.	Trace
5028	IPHTTPS: %1 Client Send Http Request: Status = %2.	Trace
5029	IPHTTPS: %1 Client Send Receive Response: Status = %2.	Trace
5030	IPHTTPS: %1 Client Send Http Status Code = %2.	Trace
5031	IPHTTPS: %1 Client Receive Entity Completion Status = %2.	Trace
5032	IPHTTPS: %1 Client Send Entity Completion Status = %2.	Trace
5033	IPHTTPS: %1 Client Scheduling a reconnect after %2 seconds.	Trace
5034	IPHTTPS: %1 Client restarting.	Trace
5035	IPHTTPS: %1 Client restarting due to internet connectivity.	Trace
5036	IPHTTPS: %1 Adding Client address mapping for address %2.	Trace
5037	IPHTTPS: %1 Removing Client address mapping for address %2.	Trace
5038	IPHTTPS: %1 Adding Pending packet for address %2.	Trace
5039	IPHTTPS: %1 Removing Pending packet for address %2.	Trace
5040	IPHTTPS: %1 Receive client certificate completed.	Trace
5041	IPHTTPS: %1 Send HTTP response completed.	Trace
5042	IPHTTPS: %1 Receive request completed.	Trace
5043	IPHTTPS: %1 Receive entity completed.	Trace
5044	IPHTTPS: %1 Send entity completed.	Trace
5045	IPHTTPS: %1 Dropped packet destined to %2 due to neighbor discovery timeout.	Trace
5046	IPHTTPS: %1 Sending neighbor solicitation for %2.	Trace
5047	IPHTTPS: IPHTTPS Interface Reference %1.	Trace
5048	IPHTTPS: IPHTTPS Interface Dereference %1.	Trace
5049	IPHTTPS: IPHTTPS Client Interface Reference %1.	Trace
5050	IPHTTPS: IPHTTPS Client Interface Dereference %1.	Trace
5051	IPHTTPS: IPHTTPS Server Interface Reference %1.	Trace
5052	IPHTTPS: IPHTTPS Server Interface Dereference %1.	Trace
5053	IPHTTPS: IPHTTPS Client Context Reference %1.	Trace
5054	IPHTTPS: IPHTTPS Client Context Dereference %1.	Trace
5055	IPHTTPS: Interface %1 installation aborted.	Trace
5061	IPHTTPS: Received WMI notification (%1) for interface %2.	Trace
5062	IPHTTPS: Received configuration change notification.	Trace
5063	IPHTTPS: %1 WinHTTP open failed with error code = %2.	Trace
5064	IPHTTPS: %1 failed to get proxy information; error code = %2.	Trace
5065	IPHTTPS: %1 proxy information: Access type = %2; proxy = %3; bypass = %4.	Trace
5066	IPHTTPS: Client interface %1 is being shutdown.	Trace
5067	IPHTTPS: Sending Duplicate Address Detection Response to client for Target.	Trace
5068	IPHTTPS: Interface canary is %1.	Trace
5069	IPHTTPS.	Trace
5100	DNS64: Query of type A from client %2 for name %3, received on interface %4 and …	Trace
5101	DNS64: Query of type AAAA from client %2 for name %3, received on interface %4 …	Trace
5102	DNS64: No matching IPv6 prefix found for IPv4 address %4, received for name %3 …	Trace
5103	DNS64: Configured A query latency value is too high.	Trace
5104	DNS64: AAAA response %5 received after A response %4 to query for name %3 by …	Trace
5105	DNS64: DNS64 Module Init Failed with status %3.	Trace
5106	DNS64: DNS64 Instance Create %1.	Trace
5107	DNS64: DNS64 Instance Delete %1.	Trace
5108	DNS64: DNS64 Instance Free %1.	Trace
5109	DNS64: DNS64 Instance Reference %1.	Trace
5110	DNS64: DNS64 Instance Dereference %1.	Trace
5111	DNS64: DNS64 Request %1 Create, with instance %4.	Trace
5112	DNS64: DNS64 Request %1 Free.	Trace
5113	DNS64: DNS64 Request Reference %1.	Trace
5114	DNS64: DNS64 Request Dereference %1.	Trace
5115	DNS64: DNS64 Request Processing - request %1 with query type %3 for name %2.	Trace
5116	DNS64: DNS64 Request Processing - request %1 completed with response code %3.	Trace
5117	DNS64: DNS64 Request Processing - request %1 cancelled.	Trace
5118	DNS64: DNS64 Request Processing - AAAA query issued for request %1, DnsQueryEx …	Trace
5119	DNS64: DNS64 Request Processing - AAAA query issued for request %1 completed …	Trace
5120	DNS64: DNS64 Request Processing - AAAA query cancelled for request %1.	Trace
5121	DNS64: DNS64 Request Processing - A query issued for request %1, DnsQueryEx …	Trace
5122	DNS64: DNS64 Request Processing - A query issued for request %1 completed with …	Trace
5123	DNS64: DNS64 Request Processing - A query cancelled for request %1.	Trace
5124	DNS64: DNS64 Request Processing - A query timer started for request %1.	Trace
5125	DNS64: DNS64 Request Processing - A query timer fired for request %1 with reason …	Trace
5126	DNS64: DNS64 Request Processing - Forwarded query issued for request %1, …	Trace
5127	DNS64: DNS64 Request Processing - Forwarded query issued for request %1 …	Trace
5128	DNS64: DNS64 Request Processing - Forwarded query cancelled for request %1.	Trace
5129	DNS64: DNS64 Request Processing - Processing locally PTR query matched …	Trace
5130	DNS64: DNS64 Request Processing - Copying records from AAAA query results for …	Trace
5131	DNS64: DNS64 Request Processing - Synthesizing records from A query results for …	Trace
5132	DNS64: DNS64 Request Processing - Merging records from A query results for …	Trace
5133	DNS64: DNS64 Request Processing - Copying records from AAAA query results to …	Trace
5200	Connectivity Platform operation in action: {Action}.	Iphlpsvc Etw Channel
5201	Connectivity Platform operation started: {Action}.	Iphlpsvc Etw Channel
5202	Connectivity Platform operation ended: {Action}.	Iphlpsvc Etw Channel
5203	Connectivity Platform operation failed: {Action}.	Iphlpsvc Etw Channel
5300	HA: {Action} started.	Iphlpsvc Etw Channel
5301	HA: {Action} failed with status {Status}.	Iphlpsvc Etw Channel
5302	HA: HEP discovery succeeded; found {Count} addresses.	Iphlpsvc Etw Channel
5303	HA: Connection attempt failed; retrying {Count} more times.	Iphlpsvc Etw Channel
5304	HA: Successfully connected to network {Network ID}.	Iphlpsvc Etw Channel
5401	PROXYMGR: %1: notifying providers of event: %2.	Trace
5402	PROXYMGR: %1: notifying clients of event: %2.	Trace
5403	PROXYMGR: %1 failed with status %2.	Trace
5404	PROXYMGR.	Trace
5501	DA MULTISITE: Configuring site %2 selected based on %1.	Trace
5502	DA MULTISITE: Configured AD site name, status %2.	Trace
5503	DA MULTISITE: Added a prefix to the prefix policy table, status %4.	Trace
5504	DA MULTISITE: Configured IPHTTPS to use profile %1, status %2.	Trace
5505	DA MULTISITE: Configured Teredo to use server %1, status %2.	Trace
5506	DA MULTISITE: Removed configuration for site %1.	Trace
5508	DA MULTISITE: Site %4 is selected based on probing.	Trace
5509	DA MULTISITE: Name resolution for multisite FQDN %2 started with error code %3.	Trace
5510	DA MULTISITE: Name resolution for multisite FQDN %1 cancelled.	Trace
5511	DA MULTISITE: Name resolution for multisite FQDN %2 completed with error code …	Trace
5512	DA MULTISITE: No potentially reachable site record found for the IP address %2 …	Trace
5513	DA MULTISITE: Site probing preparation finished with %3 site probes prepared.	Trace
5514	DA MULTISITE: Site probing prepared for URL %1 at timestamp %2.	Trace
5515	DA MULTISITE: Site probing started for URL %1 with error code %2 at timestamp …	Trace
5516	DA MULTISITE: Site probing cancelled for URL %1.	Trace
5517	DA MULTISITE: Site probe for URL %1 completed with error code %2, HTTP status %3 …	Trace
5518	DA MULTISITE: Timer expired in state %3.	Trace
5519	DASTMGR.	Trace
5550	ISATAP.	Trace
5600	6to4.	Trace
5607	DA MULTISITE: Corporate connectivity has been indicated in %2 milliseconds or …	Trace
5650	COMMON.	Trace
5651	ERROR.	Trace
5652		Trace
5653	FSM.	Trace
5654		Trace
5655	PortProxy.	Trace
5656		Operational
5656	CLATMGR.	Trace
5657		Operational

Event ID 4051 — Teredo %2: Forwarding %3 packet from %4 to %5.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo %2: Forwarding %3 packet from %4 to %5.

Fields

Name	Description
`IpAddrLength`	—
`ServiceType`	—
`TeredoPacketType`	—
`Source IP Address`	—
`Destination IP Address`	—
`SourceIPAddress`	—
`DestinationIPAddress`	—

Event ID 4052 — Teredo server: Received %2 from %3 , Sending %4 to %5.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo server: Received %2 from %3 , Sending %4 to %5.

Fields

Name	Description
`IpAddrLength`	—
`ReceivedTeredoPacketType`	—
`Source IP Address`	—
`SentTeredoPacketType`	—
`Destination IP Address`	—
`SourceIPAddress`	—
`DestinationIPAddress`	—

Event ID 4053 — Teredo %2 received %3, Mapping to %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo %2 received %3, Mapping to %4.
 source: %5, destination: %6, target: %7.

Fields

Name	Description
`source`	—
`destination`	—
`target`	—
`IpAddrLength`	—
`ServiceType`	—
`ReceivedTeredoPacketType`	—
`MappedTeredoPacketType`	—
`SourceIPAddress`	—
`DestinationIPAddress`	—
`TargetIPAddress`	—

Event ID 4054 — Teredo client in state %1,received bad or invalid packet with %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo client in state %1,received bad or invalid packet with %2.

Fields

Name	Description
`TeredoProtocolState`	—
`Bad or Invalid Packet`	—
`BadorInvalidPacket`	—

Event ID 4055 — Teredo client state change: Previous state %1, Current state %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo client state change: Previous state %1, Current state %2.

Fields

Name	Description
`PreviousTeredoProtocolState`	—
`CurrentTeredoProtocolState`	—

Event ID 4056 — Teredo client Sending %1 packet.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo client Sending %1 packet.

Fields

Name	Description
`TeredoPacketType`	—

Event ID 4057 — Starting Teredo Offload with: LocalV6:%3 RemoteV6:%4 LocalV4:%5 RemoteV4:%6 LocalPort:%7 RemotePort:%8.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Starting Teredo Offload with: 
LocalV6:%3 RemoteV6:%4 
LocalV4:%5 RemoteV4:%6 
LocalPort:%7 RemotePort:%8.

Fields

Name	Description
`LocalV6`	—
`RemoteV6`	—
`LocalV4`	[Starting Teredo Offload with] LocalV6.
`RemoteV4`	[Starting Teredo Offload with] RemoteV6.
`LocalPort`	[Starting Teredo Offload with] LocalV4.
`RemotePort`	[Starting Teredo Offload with] RemoteV4.
`IpAddrV4Length`	—
`IpAddrV6Length`	—
`SourceIpv6Address`	—
`DestinationIPv6Address`	—
`SourceIPv4Address`	—
`DestinationIPv4Address`	—
`SourcePort`	—
`DestinationPort`	—

Event ID 4058 —

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%1

Fields

Name	Description
`Description`	—

Event ID 4059 — Teredo server received bad or invalid packet with %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo server received bad or invalid packet with %1.

Fields

Name	Description
`Bad or Invalid Packet`	—
`BadorInvalidPacket`	—

Event ID 4060 — %2 %3 mapping: %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%2 %3 mapping: %4.

Fields

Name	Description
`SockAddrLength`	—
`ServiceType`	—
`MappingType`	—
`SocketAddress`	—

Event ID 4061 — Teredo %2 transmitting packet to %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo %2 transmitting packet to %3.

Fields

Name	Description
`AddrLength`	—
`Primary or Secondary`	—
`Destination Address`	—
`PrimaryorSecondary`	—
`DestinationAddress`	—

Event ID 4062 — Teredo %2 received %3 packet from %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo %2 received %3 packet from %4.

Fields

Name	Description
`AddrLength`	—
`ServiceType`	—
`TeredoPacketType`	—
`Source Ipv6 Address`	—
`SourceIpv6Address`	—

Event ID 4063 — Teredo %2 received %3, sending %4 to %5.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo %2 received %3, sending %4 to %5.

Fields

Name	Description
`IpAddrLength`	—
`ServiceType`	—
`ReceivedTeredoPacketType`	—
`MappedTeredoPacketType`	—
`Destination IP Address`	—
`DestinationIPAddress`	—

Event ID 4064 — Teredo %2 received %3, sending %4 to %5.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo %2 received %3, sending %4 to %5.

Fields

Name	Description
`AddrLength`	—
`ServiceType`	—
`ReceivedTeredoPacketType`	—
`MappedTeredoPacketType`	—
`Destination IP Address`	—
`DestinationIPAddress`	—

Event ID 4065 — Teredo %2 received packet from %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo %2 received packet from %3.

Fields

Name	Description
`AddrLength`	—
`Primary or Secondary`	—
`Socket Address`	—
`PrimaryorSecondary`	—
`SocketAddress`	—

Event ID 4066 — Teredo %2 received packet type %3; with source %4 destination %5 target %6.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo %2 received packet type %3;
 with source %4 destination %5 target %6.

Fields

Name	Description
`AddrLength`	—
`ServiceType`	—
`TeredoPacketType`	—
`Source Ipv6 Address`	—
`Destination IP Address`	—
`Target IP Address`	—
`SourceIpv6Address`	—
`DestinationIPAddress`	—
`TargetIPAddress`	—

Event ID 4067 — Teredo %2 transmitting %3 packet to %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo %2 transmitting %3 packet to %4.

Fields

Name	Description
`AddrLength`	—
`ServiceType`	—
`TeredoPacketType`	—
`Destination Address`	—
`DestinationAddress`	—

Event ID 4068 — Teredo connectivity initiated by %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: System

Message

Teredo connectivity initiated by %1

Fields

Name	Description
`Program`	—

Event ID 4069 — %1 using Teredo connectivity.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: System

Message

%1 using Teredo connectivity

Fields

Name	Description
`Program`	—

Event ID 4070 — %1 no longer using Teredo connectivity.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: System

Message

%1 no longer using Teredo connectivity

Fields

Name	Description
`Program`	—

Event ID 4071 — Teredo connectivity ended by %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: System

Message

Teredo connectivity ended by %1

Fields

Name	Description
`Program`	—

Event ID 4150 — %1 interface %2 %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%1 interface %2 %3.

Fields

Name	Description
`ProtocolType`	—
`Interface`	—
`InterfaceState`	—

Event ID 4151 — ISATAP link local address for interface %2 was %3, is %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

ISATAP link local address for interface %2 was %3, is %4.

Fields

Name	Description
`AddrLength`	—
`Interface`	—
`Current IPv4 Address`	—
`New IPv4 Address`	—
`CurrentIPv4Address`	—
`NewIPv4Address`	—

Event ID 4152 — ISATAP potential router interface list has changed.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

ISATAP potential router interface list has changed.

Event ID 4153 — %2: Found route to %3 from interface %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%2: Found route to %3 from interface %4.
Source = %5, Next Hop = %6.

Fields

Name	Description
`AddrLength`	—
`ProtocolType`	—
`Destination IPv4 Address`	—
`Interface`	—
`Source IPv4 Address`	—
`Next Hop IPv4 Address`	—
`DestinationIPv4Address`	—
`SourceIPv4Address`	—
`NextHopIPv4Address`	—

Event ID 4154 — %2: For %3, router %4 is %5.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Debug

Message

%2: For %3, router %4 is %5.

Fields

Name	Description
`AddrLength`	—
`ProtocolType`	—
`InterfaceName`	—
`Router IPv4 Address`	—
`Reachable`	—
`RouterIPv4Address`	—

Event ID 4155 — For %2, router name: %3, is %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Debug

Message

For %2, router name: %3, is %4. %5.

Fields

Name	Description
`AddrLength`	—
`InterfaceName`	—
`RouterName`	—
`Resolved`	—
`Router IPv4 Address`	—
`RouterIPv4Address`	—

Event ID 4157 — %1 protocol started.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%1 protocol started.

Fields

Name	Description
`ProtocolType`	—

Event ID 4158 — %1 protocol stopped.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%1 protocol stopped.

Fields

Name	Description
`ProtocolType`	—

Event ID 4159 — %1 protocol initialized.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%1 protocol initialized.

Fields

Name	Description
`ProtocolType`	—

Event ID 4160 — %1 protocol uninitialized.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%1 protocol uninitialized.

Fields

Name	Description
`ProtocolType`	—

Event ID 4161 — ISATAP found interface %1 to reuse.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

ISATAP found interface %1 to reuse.

Fields

Name	Description
`InterfaceName`	—

Event ID 4162 — %2: interface %5 address %4 %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%2: interface %5 address %4 %3.

Fields

Name	Description
`AddrLength`	—
`ProtocolType`	—
`AddedorDeleted`	—
`IPv4 Address`	—
`InterfaceName`	—
`IPv4Address`	—

Event ID 4163 — 6to4: Updating route %2/%3 interface %4 metric %5 lifetime %6/%7 publish %8.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

6to4: Updating route %2/%3 interface %4 metric %5 lifetime %6/%7 publish %8.

Fields

Name	Description
`AddrLength`	—
`IP Address`	—
`PrefixLen`	—
`InterfaceAlias`	—
`Metric`	—
`PreferredLifetime`	—
`ValidLifeTime`	—
`Publish`	—
`IPAddress`	—

Event ID 4164 — 6to4: Configuring interface %1 with following parameters: ICS PrivateInterface = %2 AdvertiseDefaultRoute = %3 Advertises = %4 Forwards = %5 NTStat...

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

6to4: Configuring interface %1 with following parameters:
ICS PrivateInterface = %2 AdvertiseDefaultRoute = %3 Advertises = %4 Forwards = %5 NTStatus = %6.

Fields

Name	Description
`InterfaceAlias`	—
`IcsPrivateInterface`	—
`AdvertiseDefaultRoute`	—
`Advertises`	—
`Forwards`	—
`Status`	—

Event ID 4165 — 6to4: Routing State changed to %1 from %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

6to4: Routing State changed to %1 from %2.

Fields

Name	Description
`New RoutingState`	—
`Old RoutingState`	—
`NewRoutingState`	—
`OldRoutingState`	—

Event ID 4166 — 6to4: For interface %1, IPv4 address %2 was chosen for link layer address.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

6to4: For interface %1, IPv4 address %2 was chosen for link layer address.

Fields

Name	Description
`InterfaceAlias`	—
`IP Address`	—
`IPAddress`	—

Event ID 4167 — %1:Change notification for compartment %2, HaveGlobalIPv6Address = %3, ICS Enabled = %4, GlobalIPv4AddressCount = %5.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%1:Change notification for compartment %2, HaveGlobalIPv6Address = %3, ICS Enabled =  %4, GlobalIPv4AddressCount = %5.

Fields

Name	Description
`ProtocolType`	—
`CompartmentId`	—
`HaveGlobalIpv6Address`	—
`ICS Enabled`	—
`GlobalIPv4AddressCount`	—
`ICSEnabled`	—

Event ID 4168 — 6to4: Configuring interface %1 in compartment %2 with routing state %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

6to4: Configuring interface %1 in compartment %2 with routing state %3.

Fields

Name	Description
`Interface Index`	—
`CompartmentId`	—
`RoutingState`	—
`InterfaceIndex`	—

Event ID 4169 — Configuring interface %2 with address %3, lifetime %4, prefix %5 suffix %6.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Configuring interface %2 with address %3, lifetime %4, prefix %5 suffix %6.

Fields

Name	Description
`AddrLength`	—
`InterfaceAlias`	—
`IP Address`	—
`Lifetime`	—
`PrefixConf`	—
`SuffixConf`	—
`IPAddress`	—

Event ID 4170 — %1 Callback for %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%1 Callback for %2.

Fields

Name	Description
`ProtocolCallback`	—
`ProtocolType`	—

Event ID 4171 — Teredo Client failed to start due to the following reason.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo Client failed to start due to the following reason: %1.

Fields

Name	Description
`TeredoReasonCode`	—

Event ID 4172 — Teredo Client stopped due to the following reason.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo Client stopped due to the following reason: %1.

Fields

Name	Description
`TeredoReasonCode`	—

Event ID 4173 — 6TO4 failed to start due to the following reason.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

6TO4 failed to start due to the following reason: %1.

Fields

Name	Description
`Windows Error Code`	—
`WindowsErrorCode`	—

Event ID 4174 — ISATAP router address %1 was set with status %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

ISATAP router address %1 was set with status %2.

Fields

Name	Description
`IsatapRouter`	—
`ErrorCode`	—

Event ID 4175 — NLM found that the network is %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

NLM found that the network is %1.

Fields

Name	Description
`NetworkType`	—

Event ID 4176 — Port-Prediction complete with: V4Addr:%1 V4Port:%2 LowerValue:%3 UpperValue:%4 PortPredicted:%5.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Port-Prediction complete with: V4Addr:%1 V4Port:%2 
LowerValue:%3 UpperValue:%4 
PortPredicted:%5.

Fields

Name	Description
`SourceIPv4Address`	—
`SourcePort`	—
`UpperValue`	—
`LowerValue`	—
`PortPredicted`	—

Event ID 4177 — Teredo operation in action.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo operation in action: %1.

Fields

Name	Description
`Action`	—

Event ID 4178 — Teredo operation started.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo operation started: %1.

Fields

Name	Description
`Teredo_operation_started`	—
`Action`	—

Event ID 4179 — Teredo operation ended.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo operation ended: %1.

Fields

Name	Description
`Teredo_operation_ended`	—
`Action`	—

Event ID 4180 — Teredo operation failed.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

Teredo operation failed: %1.

Fields

Name	Description
`Teredo_operation_failed`	—
`Action`	—

Event ID 5000 — IPHTTPS: InterfaceName:%1 InterfaceType:%2 RegistryState:%3 CurrentState:%4 URL:%5 AuthenticationMode:%6.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: InterfaceName:%1 InterfaceType:%2 RegistryState:%3 CurrentState:%4 URL:%5 AuthenticationMode:%6

Fields

Name	Description
`IPHTTPS_InterfaceName`	IPHTTPS: InterfaceName.
`InterfaceType`	—
`RegistryState`	—
`CurrentState`	—
`URL`	—
`AuthenticationMode`	—
`InterfaceName`	—

Event ID 5001 — IPHTTPS: Interface %1 installation failed.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 installation failed. Status = %2

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5002 — IPHTTPS: Interface %1 update link address.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 update link address. Status = %2

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5003 — IPHTTPS: Client interface %1 configured to use certificate %2 with preference = %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Client interface %1 configured to use certificate %2 with preference = %3

Fields

Name	Description
`InterfaceName`	—
`CertificateCN`	—
`Preference`	—

Event ID 5004 — IPHTTPS: Interface %1 cleanup complete.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 cleanup complete

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5005 — IPHTTPS: Interface %1 firewall exception added.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 firewall exception added. Status = %2

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5006 — IPHTTPS: Interface %1 performance counters added.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 performance counters added. Status = %2

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5007 — IPHTTPS: Interface %1 Memory allocation failed.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 Memory allocation failed

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5008 — IPHTTPS: Interface %1 Tunnel device IO failed: %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 Tunnel device IO failed: %2

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5009 — IPHTTPS: Interface %1 reusing an previously installed interface.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 reusing an previously installed interface

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5010 — IPHTTPS: Interface %1 deleted.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 deleted

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5011 — IPHTTPS: Interface %1 media connect indication: Status= %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 media connect indication: Status= %2

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5012 — IPHTTPS: Interface %1 media disconnect indication: Status= %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 media disconnect indication: Status= %2

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5013 — IPHTTPS: Interface %1 deactivated.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 deactivated.

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5014 — IPHTTPS: Adapter %1 uninstalled as it does not have associated registry configuration.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Adapter %1 uninstalled as it does not have associated registry configuration.Status = %2

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5015 — IPHTTPS: V6 Address change callback.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: V6 Address change callback. Address = %2 Added = %3 LimitedConnectivity = %4

Fields

Name	Description
`InterfaceIndex`	—
`Address`	—
`Added`	—
`LimitedConnectivity`	—

Event ID 5016 — IPHTTPS: Global connectivity state change.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Global connectivity state change. GlobalAddressCount = %1 Ipv4Connectivity = %2 Ipv6Connectivity = %3 CorpConnectivity = %4

Fields

Name	Description
`GlobalIpv6AddressCount`	—
`Ipv4Connectivity`	—
`Ipv6Connectivity`	—
`CorpConnectivity`	—

Event ID 5017 — IPHTTPS: Interface callback.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface callback. Index = %1 Added = %3 LimitedConnectivity = %4

Fields

Name	Description
`InterfaceIndex`	—
`Address`	—
`Added`	—
`LimitedConnectivity`	—

Event ID 5018 — IPHTTPS: Interface %1 activated.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 activated.

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5019 — IPHTTPS: Corp connectivity timer started.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Corp connectivity timer started. Due time = %1 (100ns units).

Fields

Name	Description
`DueTime`	—

Event ID 5020 — IPHTTPS: Corp connectivity timeout.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Corp connectivity timeout.

Fields

Name	Description
`DueTime`	—

Event ID 5021 — IPHTTPS: Network change.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Network change. Network GUID = %1 Added = %2

Fields

Name	Description
`NetworkGuid`	—
`Added`	—

Event ID 5022 — IPHTTPS: Teredo dormancy change.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Teredo dormancy change. New State = %1

Fields

Name	Description
`CurrentTeredoProtocolState`	—

Event ID 5023 — IPHTTPS: Initialization failed.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Initialization failed. Status = %1

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5024 — IPHTTPS: ND Packet.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: ND Packet. Packet type = %1, Target Address = %2, Prefix = %3, Default Router = %4.

Fields

Name	Description
`PacketType`	—
`TargetAddress`	—
`Prefix`	—
`DefaultRouter`	—

Event ID 5025 — IPHTTPS: Client interface is being shutdown.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Client interface is being shutdown.

Event ID 5026 — IPHTTPS: Client IO Reference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Client IO Reference %1.

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5027 — IPHTTPS: Client IO Dereference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Client IO Dereference %1.

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5028 — IPHTTPS: %1 Client Send Http Request: Status = %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Client Send Http Request: Status = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5029 — IPHTTPS: %1 Client Send Receive Response: Status = %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Client Send Receive Response: Status = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5030 — IPHTTPS: %1 Client Send Http Status Code = %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Client Send Http Status Code = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5031 — IPHTTPS: %1 Client Receive Entity Completion Status = %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Client Receive Entity Completion Status = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5032 — IPHTTPS: %1 Client Send Entity Completion Status = %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Client Send Entity Completion Status = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5033 — IPHTTPS: %1 Client Scheduling a reconnect after %2 seconds.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Client Scheduling a reconnect after %2 seconds.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5034 — IPHTTPS: %1 Client restarting.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Client restarting.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5035 — IPHTTPS: %1 Client restarting due to internet connectivity.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Client restarting due to internet connectivity.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5036 — IPHTTPS: %1 Adding Client address mapping for address %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Adding Client address mapping for address %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`Address`	—

Event ID 5037 — IPHTTPS: %1 Removing Client address mapping for address %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Removing Client address mapping for address %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`Address`	—

Event ID 5038 — IPHTTPS: %1 Adding Pending packet for address %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Adding Pending packet for address %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`Address`	—

Event ID 5039 — IPHTTPS: %1 Removing Pending packet for address %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Removing Pending packet for address %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`Address`	—

Event ID 5040 — IPHTTPS: %1 Receive client certificate completed.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Receive client certificate completed. Status = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5041 — IPHTTPS: %1 Send HTTP response completed.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Send HTTP response completed. Status = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5042 — IPHTTPS: %1 Receive request completed.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Receive request completed. Status = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5043 — IPHTTPS: %1 Receive entity completed.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Receive entity completed. Status = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5044 — IPHTTPS: %1 Send entity completed.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Send entity completed. Status = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5045 — IPHTTPS: %1 Dropped packet destined to %2 due to neighbor discovery timeout.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Dropped packet destined to %2 due to neighbor discovery timeout.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`DestinationAddress`	—

Event ID 5046 — IPHTTPS: %1 Sending neighbor solicitation for %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 Sending neighbor solicitation for %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`DestinationAddress`	—

Event ID 5047 — IPHTTPS: IPHTTPS Interface Reference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: IPHTTPS Interface Reference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5048 — IPHTTPS: IPHTTPS Interface Dereference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: IPHTTPS Interface Dereference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5049 — IPHTTPS: IPHTTPS Client Interface Reference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: IPHTTPS Client Interface Reference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5050 — IPHTTPS: IPHTTPS Client Interface Dereference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: IPHTTPS Client Interface Dereference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5051 — IPHTTPS: IPHTTPS Server Interface Reference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: IPHTTPS Server Interface Reference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5052 — IPHTTPS: IPHTTPS Server Interface Dereference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: IPHTTPS Server Interface Dereference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5053 — IPHTTPS: IPHTTPS Client Context Reference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: IPHTTPS Client Context Reference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5054 — IPHTTPS: IPHTTPS Client Context Dereference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: IPHTTPS Client Context Dereference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5055 — IPHTTPS: Interface %1 installation aborted.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface %1 installation aborted. IPHTTPS is disabled by DisabledComponents registry

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5061 — IPHTTPS: Received WMI notification (%1) for interface %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Received WMI notification (%1) for interface %2

Fields

Name	Description
`WmiNotificationType`	—
`InterfaceName`	—

Event ID 5062 — IPHTTPS: Received configuration change notification.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Received configuration change notification.

Event ID 5063 — IPHTTPS: %1 WinHTTP open failed with error code = %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 WinHTTP open failed with error code = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5064 — IPHTTPS: %1 failed to get proxy information; error code = %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 failed to get proxy information; error code = %2.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`StatusCode`	—

Event ID 5065 — IPHTTPS: %1 proxy information: Access type = %2; proxy = %3; bypass = %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1 proxy information: Access type = %2; proxy = %3; bypass = %4.

Fields

Name	Description
`IPHTTPS`	—
`InterfaceName`	—
`ProxyAccessType`	—
`Proxy`	—
`ProxyBypass`	—

Event ID 5066 — IPHTTPS: Client interface %1 is being shutdown.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Client interface %1 is being shutdown.

Fields

Name	Description
`InterfaceName`	—
`StatusCode`	—

Event ID 5067 — IPHTTPS: Sending Duplicate Address Detection Response to client for Target.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Sending Duplicate Address Detection Response to client (%1) for Target: %2

Fields

Name	Description
`ClientContext`	—
`TargetAddress`	—

Event ID 5068 — IPHTTPS: Interface canary is %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: Interface canary is %1

Fields

Name	Description
`Value`	—

Event ID 5069 — IPHTTPS.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

IPHTTPS: %1

Fields

Name	Description
`IPHTTPS`	—
`Action`	—

Event ID 5100 — DNS64: Query of type A from client %2 for name %3, received on interface %4 and sent on interface %5, failed with code %6.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: Query of type A from client %2 for name %3, received on interface %4 and sent on interface %5, failed with code %6.

Fields

Name	Description
`AddrLength`	—
`ClientIP`	—
`QuestionName`	—
`QueryReceiveInterface`	—
`QuerySendInterface`	—
`DnsStatus`	—

Event ID 5101 — DNS64: Query of type AAAA from client %2 for name %3, received on interface %4 and sent on interface %5, failed with code %6.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: Query of type AAAA from client %2 for name %3, received on interface %4 and sent on interface %5, failed with code %6.

Fields

Name	Description
`AddrLength`	—
`ClientIP`	—
`QuestionName`	—
`QueryReceiveInterface`	—
`QuerySendInterface`	—
`DnsStatus`	—

Event ID 5102 — DNS64: No matching IPv6 prefix found for IPv4 address %4, received for name %3 queried by client %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: No matching IPv6 prefix found for IPv4 address %4, received for name %3 queried by client %2.

Fields

Name	Description
`AddrLength`	—
`ClientIP`	—
`QuestionName`	—
`Translated IPv4 Address`	—
`TranslatedIPv4Address`	—

Event ID 5103 — DNS64: Configured A query latency value is too high.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: Configured A query latency value is too high.

Event ID 5104 — DNS64: AAAA response %5 received after A response %4 to query for name %3 by client %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: AAAA response %5 received after A response %4 to query for name %3 by client %2.

Fields

Name	Description
`AddrLength`	—
`ClientIP`	—
`QuestionName`	—
`IPv4 Address`	—
`IPv6 Address`	—
`IPv4Address`	—
`IPv6Address`	—

Event ID 5105 — DNS64: DNS64 Module Init Failed with status %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Module Init Failed with status %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5106 — DNS64: DNS64 Instance Create %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Instance Create %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5107 — DNS64: DNS64 Instance Delete %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Instance Delete %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5108 — DNS64: DNS64 Instance Free %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Instance Free %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5109 — DNS64: DNS64 Instance Reference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Instance Reference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5110 — DNS64: DNS64 Instance Dereference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Instance Dereference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5111 — DNS64: DNS64 Request %1 Create, with instance %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request %1 Create, with instance %4

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—
`Object2`	—

Event ID 5112 — DNS64: DNS64 Request %1 Free.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request %1 Free

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5113 — DNS64: DNS64 Request Reference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Reference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5114 — DNS64: DNS64 Request Dereference %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Dereference %1

Fields

Name	Description
`Object`	—
`FileName`	—
`LineNumber`	—

Event ID 5115 — DNS64: DNS64 Request Processing - request %1 with query type %3 for name %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - request %1 with query type %3 for name %2

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5116 — DNS64: DNS64 Request Processing - request %1 completed with response code %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - request %1 completed with response code %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5117 — DNS64: DNS64 Request Processing - request %1 cancelled.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - request %1 cancelled

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5118 — DNS64: DNS64 Request Processing - AAAA query issued for request %1, DnsQueryEx returned status %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - AAAA query issued for request %1, DnsQueryEx returned status %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5119 — DNS64: DNS64 Request Processing - AAAA query issued for request %1 completed with status %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - AAAA query issued for request %1 completed with status %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5120 — DNS64: DNS64 Request Processing - AAAA query cancelled for request %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - AAAA query cancelled for request %1

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5121 — DNS64: DNS64 Request Processing - A query issued for request %1, DnsQueryEx returned status %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - A query issued for request %1, DnsQueryEx returned status %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5122 — DNS64: DNS64 Request Processing - A query issued for request %1 completed with status %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - A query issued for request %1 completed with status %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5123 — DNS64: DNS64 Request Processing - A query cancelled for request %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - A query cancelled for request %1

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5124 — DNS64: DNS64 Request Processing - A query timer started for request %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - A query timer started for request %1

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5125 — DNS64: DNS64 Request Processing - A query timer fired for request %1 with reason %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - A query timer fired for request %1 with reason %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5126 — DNS64: DNS64 Request Processing - Forwarded query issued for request %1, DnsQueryEx returned status %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - Forwarded query issued for request %1, DnsQueryEx returned status %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5127 — DNS64: DNS64 Request Processing - Forwarded query issued for request %1 completed with status %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - Forwarded query issued for request %1 completed with status %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5128 — DNS64: DNS64 Request Processing - Forwarded query cancelled for request %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - Forwarded query cancelled for request %1

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5129 — DNS64: DNS64 Request Processing - Processing locally PTR query matched configured suffixes for request %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - Processing locally PTR query matched configured suffixes for request %1

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5130 — DNS64: DNS64 Request Processing - Copying records from AAAA query results for request %1, response code set to %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - Copying records from AAAA query results for request %1, response code set to %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5131 — DNS64: DNS64 Request Processing - Synthesizing records from A query results for request %1, response code set to %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - Synthesizing records from A query results for request %1, response code set to %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5132 — DNS64: DNS64 Request Processing - Merging records from A query results for request %1, response code set to %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - Merging records from A query results for request %1, response code set to %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5133 — DNS64: DNS64 Request Processing - Copying records from AAAA query results to otherwise empty response for request %1, response code set to %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DNS64: DNS64 Request Processing - Copying records from AAAA query results to otherwise empty response for request %1, response code set to %3

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5200 — Connectivity Platform operation in action: {Action}.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Iphlpsvc Etw Channel

Message

Connectivity Platform operation in action: {Action}.

Fields

Name	Description
`Action`	—

Event ID 5201 — Connectivity Platform operation started: {Action}.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Iphlpsvc Etw Channel

Message

Connectivity Platform operation started: {Action}.

Fields

Name	Description
`Action`	—

Event ID 5202 — Connectivity Platform operation ended: {Action}.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Iphlpsvc Etw Channel

Message

Connectivity Platform operation ended: {Action}.

Fields

Name	Description
`Action`	—

Event ID 5203 — Connectivity Platform operation failed: {Action}.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Iphlpsvc Etw Channel

Message

Connectivity Platform operation failed: {Action}.

Fields

Name	Description
`Action`	—

Event ID 5300 — HA: {Action} started.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Iphlpsvc Etw Channel

Message

HA: {Action} started.

Fields

Name	Description
`Action`	—

Event ID 5301 — HA: {Action} failed with status {Status}.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Iphlpsvc Etw Channel

Message

HA: {Action} failed with status {Status}.

Fields

Name	Description
`Action`	—
`Status`	—

Event ID 5302 — HA: HEP discovery succeeded; found {Count} addresses.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Iphlpsvc Etw Channel

Message

HA: HEP discovery succeeded; found {Count} addresses.

Fields

Name	Description
`Count`	—

Event ID 5303 — HA: Connection attempt failed; retrying {Count} more times.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Iphlpsvc Etw Channel

Message

HA: Connection attempt failed; retrying {Count} more times.

Fields

Name	Description
`Count`	—

Event ID 5304 — HA: Successfully connected to network {Network ID}.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Iphlpsvc Etw Channel

Message

HA: Successfully connected to network {Network ID}.

Event ID 5401 — PROXYMGR: %1: notifying providers of event: %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

PROXYMGR: %1: notifying providers of event: %2

Fields

Name	Description
`Reason`	—
`Event`	—

Event ID 5402 — PROXYMGR: %1: notifying clients of event: %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

PROXYMGR: %1: notifying clients of event: %2

Fields

Name	Description
`Reason`	—
`Event`	—

Event ID 5403 — PROXYMGR: %1 failed with status %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

PROXYMGR: %1 failed with status %2

Fields

Name	Description
`PROXYMGR`	—
`Action`	—
`Status`	—

Event ID 5404 — PROXYMGR.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

PROXYMGR: %1

Fields

Name	Description
`PROXYMGR`	—
`Action`	—

Event ID 5501 — DA MULTISITE: Configuring site %2 selected based on %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Configuring site %2 selected based on %1.

Fields

Name	Description
`SiteSelectionMethod`	—
`SiteName`	—
`IphttpsProfileName`	—
`TeredoServerIp`	—
`AddrLength`	—
`SiteIpv6Address`	—
`AdSiteName`	—
`CorporateRanges`	—

Event ID 5502 — DA MULTISITE: Configured AD site name, status %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Configured AD site name, status %2.

Fields

Name	Description
`AdSiteName`	—
`Status`	—

Event ID 5503 — DA MULTISITE: Added a prefix to the prefix policy table, status %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Added a prefix to the prefix policy table, status %4

Fields

Name	Description
`AddrLength`	—
`Prefix`	—
`PrefixLength`	—
`Status`	—

Event ID 5504 — DA MULTISITE: Configured IPHTTPS to use profile %1, status %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Configured IPHTTPS to use profile %1, status %2

Fields

Name	Description
`IphttpsProfileName`	—
`Status`	—

Event ID 5505 — DA MULTISITE: Configured Teredo to use server %1, status %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Configured Teredo to use server %1, status %2

Fields

Name	Description
`TeredoServerIp`	—
`Status`	—

Event ID 5506 — DA MULTISITE: Removed configuration for site %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Removed configuration for site %1.

Fields

Name	Description
`SiteName`	—

Event ID 5508 — DA MULTISITE: Site %4 is selected based on probing.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Site %4 is selected based on probing. Previously, TCP/IP sorting selected site %1 with metric %2 for address family %3.

Fields

Name	Description
`SortingSiteName`	—
`SortingMetric`	—
`AddressFamily`	—
`ProbingSiteName`	—

Event ID 5509 — DA MULTISITE: Name resolution for multisite FQDN %2 started with error code %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Name resolution for multisite FQDN %2 started with error code %3.

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5510 — DA MULTISITE: Name resolution for multisite FQDN %1 cancelled.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Name resolution for multisite FQDN %1 cancelled.

Fields

Name	Description
`Action`	—

Event ID 5511 — DA MULTISITE: Name resolution for multisite FQDN %2 completed with error code %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Name resolution for multisite FQDN %2 completed with error code %3.

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5512 — DA MULTISITE: No potentially reachable site record found for the IP address %2 resolved for the multisite FQDN.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: No potentially reachable site record found for the IP address %2 resolved for the multisite FQDN.

Fields

Name	Description
`AddrLength`	—
`Prefix`	—

Event ID 5513 — DA MULTISITE: Site probing preparation finished with %3 site probes prepared.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Site probing preparation finished with %3 site probes prepared.

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5514 — DA MULTISITE: Site probing prepared for URL %1 at timestamp %2.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Site probing prepared for URL %1 at timestamp %2.

Fields

Name	Description
`SiteUrl`	—
`Timestamp`	—

Event ID 5515 — DA MULTISITE: Site probing started for URL %1 with error code %2 at timestamp %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Site probing started for URL %1 with error code %2 at timestamp %3.

Fields

Name	Description
`SiteUrl`	—
`ErrorCode`	—
`Timestamp`	—

Event ID 5516 — DA MULTISITE: Site probing cancelled for URL %1.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Site probing cancelled for URL %1.

Fields

Name	Description
`Action`	—

Event ID 5517 — DA MULTISITE: Site probe for URL %1 completed with error code %2, HTTP status %3 at timestamp %4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Site probe for URL %1 completed with error code %2, HTTP status %3 at timestamp %4.

Fields

Name	Description
`SiteUrl`	—
`ErrorCode`	—
`HttpStatus`	—
`Timestamp`	—

Event ID 5518 — DA MULTISITE: Timer expired in state %3.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Timer expired in state %3.

Fields

Name	Description
`Object`	—
`Message`	—
`Value`	—

Event ID 5519 — DASTMGR.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DASTMGR: %1

Fields

Name	Description
`DASTMGR`	—
`Action`	—

Event ID 5550 — ISATAP.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

ISATAP: %1

Fields

Name	Description
`ISATAP`	—
`Action`	—

Event ID 5600 — 6to4.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

6to4: %1

Fields

Name	Description
`6to4`	—
`Action`	—

Event ID 5607 — DA MULTISITE: Corporate connectivity has been indicated in %2 milliseconds or less after site %1 configuration.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

DA MULTISITE: Corporate connectivity has been indicated in %2 milliseconds or less after site %1 configuration.

Fields

Name	Description
`SiteName`	—
`Delay`	—

Event ID 5650 — COMMON.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

COMMON: %1

Fields

Name	Description
`COMMON`	—
`Action`	—

Event ID 5651 — ERROR.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

ERROR: %1

Fields

Name	Description
`ERROR`	—
`Action`	—

Event ID 5652 —

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%1

Fields

Name	Description
`Action`	—

Event ID 5653 — FSM.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

FSM: %1

Fields

Name	Description
`FSM`	—
`Action`	—

Event ID 5654 —

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

%1

Fields

Name	Description
`Action`	—

Event ID 5655 — PortProxy.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

PortProxy: %1

Fields

Name	Description
`PortProxy`	—
`Action`	—

Event ID 5656 —

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Operational

Fields

Name	Description
`Action`	—

Event ID 5656 — CLATMGR.

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Trace

Message

CLATMGR: %1

Fields

Name	Description
`Action`	—

Event ID 5657 —

Provider: Microsoft-Windows-Iphlpsvc-Trace
Channel: Operational

Fields

Name	Description
`ErrorMessage`	—
`ErrorCode`	—