Microsoft-Windows-Wired-AutoConfig

101 events across 2 channels

Event IDTitleChannel
13021A pre-logon connection was not attempted.Operational
13022A pre-logon connection was attempted.Operational
13031A post-logon connection was not attempted.Operational
13032A post-logon connection was attempted.Operational
13033The post-logon connection attempt is complete.Operational
15500The network adapter has been unplugged.Operational
15501The network adapter has been connected.Operational
15502The profile was applied on the network adapter.Operational
15503Wired 802.Operational
15504Wired 802.Operational
15505Wired 802.Operational
15506Network authentication attempts have been temporarily suspended on this network …Operational
15507Network authentication attempts have been resumed on this network adapter.Operational
15508There has been an NDIS Port state change on this network adapter.Operational
15509The operational state on the network adapter was identified.Operational
15510A network adapter was added to the system.Operational
15511The Wired AutoConfig service entered the running state.Operational
15512The Wired AutoConfig service entered the stopped state.Operational
15513A network adapter was removed from the system.Operational
15514Wired 802.Operational
15515The Wired AutoConfig service is starting.Operational
15516The Wired AutoConfig service is stopping.Operational
20001No interactive console session to send UI requestDiagnostic
20002ACM: IntfCompleteTimely failed, error %1.Diagnostic
20003There are no available connectionsDiagnostic
20004MSM failed to initialize the interface, error %1.Diagnostic
20005Failed to load profile, error %1.Diagnostic
20006No profile found in db, error %1.Diagnostic
20007ACM: UI request could not be sent.Diagnostic
20008IntfCompletePlap failed, error %1.Diagnostic
20009Interface does not have any available networksDiagnostic
20010Invalid state of the adapter %1.Diagnostic
20011Media is disconnected, SSO can't be doneDiagnostic
20012Failed to make the PLAP runtime state , error %1.Diagnostic
20013Failed to make the timely runtime state , error %1.Diagnostic
20014Interface does not have a profileDiagnostic
20015OneXSetEapUserData failed, error %1.Diagnostic
20016AcmQueryUserDataProperties failed, error %1.Diagnostic
20017Dot3AcmQueryUserDataByGuid failed, error %1.Diagnostic
20018DsRoleGetPrimaryDomainInformation failed, error %1.Diagnostic
20019Adapter is connected , we have a valid IPDiagnostic
20020Don't have time to wait for DC connectivity.Diagnostic
20021Waiting for DC connectivityDiagnostic
20022Wait for ip address change successfully completedDiagnostic
20024Wait for ip address change timed outDiagnostic
20025Wait for ip address change failed with errorDiagnostic
20026Waiting for ip address change notificationDiagnostic
20028Wait for 1x completion successfully completedDiagnostic
20029Adapter not connected.Diagnostic
200301x completed with a failure %1.Diagnostic
20031Wait for 1x completion failed with return codeDiagnostic
20032Wait for 1x completion timed outDiagnostic
20033IntfDoTimely took longer than our timeout allows.Diagnostic
20034IntfDoTimely completed successfullyDiagnostic
20035IntfDoTimely failed, error %1.Diagnostic
20036No TIMELY profiles were found.Diagnostic
20037Timely1x - Interface %1, profile %3 - Start %4, Stop %5.Diagnostic
20038FindTimelyIntfAndProfile failed, error %1.Diagnostic
21001DeviceLayerOpenHandle failed, Error %1.Diagnostic
21002DeviceLayerQueryOID failed %1, OID %3.Diagnostic
21003DeviceLayerSetOID failed %1, OID %3.Diagnostic
21004DeviceLayerSendPacket failed.Diagnostic
21005DeviceLayerReceivePacket failed.Diagnostic
21006Packet only %4 bytes, skipped.Diagnostic
21007Invalid packet type %4, skipped.Diagnostic
21008The read request was cancelledDiagnostic
21009Receiving data error %1.Diagnostic
21010Packet skipped, error %1.Diagnostic
21011Send data failed, error %1.Diagnostic
21012Interface(%4): pAcmConnectionProgress failed %1.Diagnostic
21013Interface(%4): pAcmQueryUserData failed %1.Diagnostic
21014Interface(%4): pAcmSetMsmProfile failed %1.Diagnostic
21015Interface(%4): pAcmSetUserData failed %1.Diagnostic
21016Interface(%4): pAcmMsmNotify failed %1.Diagnostic
21017Interface(%4): pAcmMediaChange failed, error %1.Diagnostic
21018Interface(%4): pAcmUIRequest failed %1.Diagnostic
21019Interface(%4): pAcmConnectionCompletionRoutine failed %1.Diagnostic
21020Interface(%1): State Transition %3 --> %4.Diagnostic
21021Interface: Received AuthNotStarted result from 1xDiagnostic
21022Interface: Received AuthInvalid result from 1xDiagnostic
21023Interface: Start processing event:Diagnostic
21024Interface: Completed processing event:Diagnostic
21025Interface(%4): StartOneXAuth failed %1.Diagnostic
21026Interface(%4): SendOneXPacket failed %1.Diagnostic
21027Interface: TIMING OUT 802.Diagnostic
21028Interface: NOT TIMING OUT 802.Diagnostic
21029Interface(%4): DeviceLayerGetCurrentMediaState failed %1.Diagnostic
21030No 1X port exists.Diagnostic
21031Interface(%1): Set the SWITCH MAC address to %2.Diagnostic
21032Interface(%4): OpenDeviceHandle failed %1.Diagnostic
21033Interface: Start processing eventDiagnostic
21034Interface(%1): ProcessDot3MsmEvent: Dot3MsmPerformStateMachineProcessing FAILed …Diagnostic
21035Interface: Completed processing eventDiagnostic
21036Finished initializing a new interface with id = %1 and friendly name = %2.Diagnostic
21037Dot3MsmInit failed %1.Diagnostic
21038Dot3MSMInitAdapter failed %1.Diagnostic
21039Failed to parse original request %1.Diagnostic
21040Failed to parse UI Response %1.Diagnostic
21041Interface(%4): OneXUIResponse failed %1.Diagnostic
21042Interface(%4): Dot3MsmQueryPendingUIRequest failed %1.Diagnostic
21043OneXValidateProfile failed %1.Diagnostic

Event ID 13021 — A pre-logon connection was not attempted.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

A pre-logon connection was not attempted.

Result: %1
Reason: %2

Fields

NameDescription
Result
Reason

Event ID 13022 — A pre-logon connection was attempted.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

A pre-logon connection was attempted.

Result: %1
Interface GUID: %2
Requested Fields: %3

Fields

NameDescription
Result
InterfaceGuid
RequestedFields

Event ID 13031 — A post-logon connection was not attempted.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

A post-logon connection was not attempted.

Result: %1
Reason: %2

Fields

NameDescription
Result
Reason

Event ID 13032 — A post-logon connection was attempted.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

A post-logon connection was attempted.

Result: %1
Interface GUID: %2

Fields

NameDescription
Result
InterfaceGuid

Event ID 13033 — The post-logon connection attempt is complete.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

The post-logon connection attempt is complete.

Network connection attempt result: %1
Reason: %2
Interface GUID: %3

Fields

NameDescription
Result
Reason
InterfaceGuid

Event ID 15500 — The network adapter has been unplugged.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

The network adapter has been unplugged.

	Network Adapter: %2
	Interface GUID: %1

Fields

NameDescription
InterfaceGuid
InterfaceDescription

Event ID 15501 — The network adapter has been connected.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

The network adapter has been connected.

	Network Adapter: %2
	Interface GUID: %1

Fields

NameDescription
InterfaceGuid
InterfaceDescription

Event ID 15502 — The profile was applied on the network adapter.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

The profile was applied on the network adapter.

	Network Adapter: %2
	Interface GUID: %1
	Profile Type: %3
	Profile Content: %4

Fields

NameDescription
InterfaceGuid
InterfaceDescription
ProfileType
ProfileContent

Event ID 15503 — Wired 802.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

Wired 802.1X Authentication was started.

	Network Adapter: %2
	Interface GUID: %1
	Connection ID: %3

Fields

NameDescription
InterfaceGuid
InterfaceDescription
ConnectionID

Event ID 15504 — Wired 802.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

Wired 802.1X Authentication was restarted.

	Network Adapter: %2
	Interface GUID: %1
	Connection ID: %3
	Restart Reason: %4

Fields

NameDescription
InterfaceGuid
InterfaceDescription
ConnectionID
RestartReason

Event ID 15505 — Wired 802.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

Wired 802.1X Authentication succeeded.

	Network Adapter: %2
	Interface GUID: %1
	Peer Address: %3
	Local Address: %4
	Connection ID: %5
	Identity: %6
	User: %7
	Domain: %8
	Reason: %9
	Reason Text: %10
	Error Code: %11

Fields

NameDescription
InterfaceGuid
InterfaceDescription
SwitchMAC
LocalMAC
ConnectionID
Identity
User
Domain
ReasonCode
ReasonText
ErrorCode
ExplicitCredentials

Event ID 15506 — Network authentication attempts have been temporarily suspended on this network adapter.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

Network authentication attempts have been temporarily suspended on this network adapter.

	Network Adapter: %2
	Interface GUID: %1
	Reason Code: %3
	Length of block timer (seconds): %4

Fields

NameDescription
InterfaceGuid
InterfaceDescription
ReasonCode
BlockingTime

Event ID 15507 — Network authentication attempts have been resumed on this network adapter.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

Network authentication attempts have been resumed on this network adapter.

	Network Adapter: %2
	Interface GUID: %1

Fields

NameDescription
InterfaceGuid
InterfaceDescription

Event ID 15508 — There has been an NDIS Port state change on this network adapter.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

There has been an NDIS Port state change on this network adapter.

	Network Adapter: %2
	Interface GUID: %1
	NDIS Control State: %3
	NDIS Auth State: %4

Fields

NameDescription
InterfaceGuid
InterfaceDescription
NdisPortControlState
NdisPortAuthState

Event ID 15509 — The operational state on the network adapter was identified.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

The operational state on the network adapter was identified.

	Network Adapter: %2
	Interface GUID: %1
	Service State: %3

Fields

NameDescription
InterfaceGuid
InterfaceDescription
AdapterState

Event ID 15510 — A network adapter was added to the system.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

A network adapter was added to the system.

	Network Adapter: %2
	Interface GUID: %1

Fields

NameDescription
InterfaceGuid
InterfaceDescription

Event ID 15511 — The Wired AutoConfig service entered the running state.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

The Wired AutoConfig service entered the running state.

Event ID 15512 — The Wired AutoConfig service entered the stopped state.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

The Wired AutoConfig service entered the stopped state.

Event ID 15513 — A network adapter was removed from the system.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

A network adapter was removed from the system.

	Network Adapter: %2
	Interface GUID: %1

Fields

NameDescription
InterfaceGuid
InterfaceDescription

Event ID 15514 — Wired 802.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

Wired 802.1X Authentication failed.

	Network Adapter: %2
	Interface GUID: %1
	Peer Address: %3
	Local Address: %4
	Connection ID: %5
	Identity: %6
	User: %7
	Domain: %8
	Reason: %9
	Reason Text: %10
	Error Code: %11

Fields

NameDescription
InterfaceGuid
InterfaceDescription
SwitchMAC
LocalMAC
ConnectionID
Identity
User
Domain
ReasonCode
ReasonText
ErrorCode
ExplicitCredentials

Event ID 15515 — The Wired AutoConfig service is starting.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

The Wired AutoConfig service is starting.

Event ID 15516 — The Wired AutoConfig service is stopping.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Operational

Message

The Wired AutoConfig service is stopping.

Event ID 20001 — No interactive console session to send UI request

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

No interactive console session to send UI request

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20002 — ACM: IntfCompleteTimely failed, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

ACM: IntfCompleteTimely failed, error %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20003 — There are no available connections

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

There are no available connections

Fields

NameDescription
ErrorCode
Location
Context

Event ID 20004 — MSM failed to initialize the interface, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

MSM failed to initialize the interface, error %1.

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20005 — Failed to load profile, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Failed to load profile, error %1.

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20006 — No profile found in db, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

No profile found in db, error %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20007 — ACM: UI request could not be sent.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

ACM: UI request could not be sent.

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20008 — IntfCompletePlap failed, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

IntfCompletePlap failed, error %1.

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20009 — Interface does not have any available networks

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface does not have any available networks

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20010 — Invalid state of the adapter %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Invalid state of the adapter %1.

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20011 — Media is disconnected, SSO can't be done

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Media is disconnected, SSO can't be done

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20012 — Failed to make the PLAP runtime state , error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Failed to make the PLAP runtime state , error %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20013 — Failed to make the timely runtime state , error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Failed to make the timely runtime state , error %1.

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20014 — Interface does not have a profile

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface does not have a profile

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 20015 — OneXSetEapUserData failed, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

OneXSetEapUserData failed, error %1.

Fields

NameDescription
ErrorCode
Location
Context

Event ID 20016 — AcmQueryUserDataProperties failed, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

AcmQueryUserDataProperties failed, error %1.

Fields

NameDescription
ErrorCode
Location
Context

Event ID 20017 — Dot3AcmQueryUserDataByGuid failed, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Dot3AcmQueryUserDataByGuid failed, error %1.

Fields

NameDescription
ErrorCode
Location
Context

Event ID 20018 — DsRoleGetPrimaryDomainInformation failed, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

DsRoleGetPrimaryDomainInformation failed, error %1

Fields

NameDescription
ErrorCode
Location
Context

Event ID 20019 — Adapter is connected , we have a valid IP

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Adapter is connected , we have a valid IP

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20020 — Don't have time to wait for DC connectivity.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Don't have time to wait for DC connectivity. Returning now

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20021 — Waiting for DC connectivity

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Waiting for DC connectivity

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20022 — Wait for ip address change successfully completed

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Wait for ip address change successfully completed

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20024 — Wait for ip address change timed out

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Wait for ip address change timed out

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20025 — Wait for ip address change failed with error

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Wait for ip address change failed with error (%1)

Fields

NameDescription
Error
Location
Context
InterfaceGuid
ProfileName

Event ID 20026 — Waiting for ip address change notification

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Waiting for ip address change notification

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20028 — Wait for 1x completion successfully completed

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Wait for 1x completion successfully completed

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20029 — Adapter not connected.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Adapter not connected. Returning now.

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20030 — 1x completed with a failure %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

1x completed with a failure %1

Fields

NameDescription
Error
Location
Context
InterfaceGuid
ProfileName

Event ID 20031 — Wait for 1x completion failed with return code

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Wait for 1x completion failed with return code (%1)

Fields

NameDescription
Error
Location
Context
InterfaceGuid
ProfileName

Event ID 20032 — Wait for 1x completion timed out

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Wait for 1x completion timed out

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20033 — IntfDoTimely took longer than our timeout allows.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

IntfDoTimely took longer than our timeout allows. Returning now

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20034 — IntfDoTimely completed successfully

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

IntfDoTimely completed successfully

Fields

NameDescription
InterfaceGuid
ProfileName
Location
Context

Event ID 20035 — IntfDoTimely failed, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

IntfDoTimely failed, error %1

Fields

NameDescription
Error
Location
Context
InterfaceGuid
ProfileName

Event ID 20036 — No TIMELY profiles were found.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

No TIMELY profiles were found. Completing the timely processing

Fields

NameDescription
ErrorCode
Location
Context

Event ID 20037 — Timely1x - Interface %1, profile %3 - Start %4, Stop %5.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Timely1x - Interface %1, profile %3 - Start %4, Stop %5

Fields

NameDescription
InterfaceGuid
Profile
Start
Stop
Duration

Event ID 20038 — FindTimelyIntfAndProfile failed, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

FindTimelyIntfAndProfile failed, error %1

Fields

NameDescription
ErrorCode
Location
Context

Event ID 21001 — DeviceLayerOpenHandle failed, Error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

DeviceLayerOpenHandle failed, Error %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceContext

Event ID 21002 — DeviceLayerQueryOID failed %1, OID %3.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

DeviceLayerQueryOID failed %1, OID %3

Fields

NameDescription
ErrorCode
Location
Context
InterfaceContext

Event ID 21003 — DeviceLayerSetOID failed %1, OID %3.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

DeviceLayerSetOID failed %1, OID %3

Fields

NameDescription
ErrorCode
Location
Context
InterfaceContext

Event ID 21004 — DeviceLayerSendPacket failed.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

DeviceLayerSendPacket failed, %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceContext

Event ID 21005 — DeviceLayerReceivePacket failed.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

DeviceLayerReceivePacket failed, %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceContext

Event ID 21006 — Packet only %4 bytes, skipped.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Packet only %4 bytes, skipped

Fields

NameDescription
ErrorCode
InterfaceContext
PacketContext
Size

Event ID 21007 — Invalid packet type %4, skipped.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Invalid packet type %4, skipped

Fields

NameDescription
ErrorCode
InterfaceContext
PacketContext
Type

Event ID 21008 — The read request was cancelled

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

The read request was cancelled

Fields

NameDescription
ErrorCode
InterfaceContext
PacketContext

Event ID 21009 — Receiving data error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Receiving data error %1

Fields

NameDescription
ErrorCode
InterfaceContext
PacketContext

Event ID 21010 — Packet skipped, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Packet skipped, error %1

Fields

NameDescription
ErrorCode
InterfaceContext
PacketContext

Event ID 21011 — Send data failed, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Send data failed, error %1

Fields

NameDescription
ErrorCode
InterfaceContext
PacketContext

Event ID 21012 — Interface(%4): pAcmConnectionProgress failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): pAcmConnectionProgress failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21013 — Interface(%4): pAcmQueryUserData failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): pAcmQueryUserData failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21014 — Interface(%4): pAcmSetMsmProfile failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): pAcmSetMsmProfile failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21015 — Interface(%4): pAcmSetUserData failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): pAcmSetUserData failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21016 — Interface(%4): pAcmMsmNotify failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): pAcmMsmNotify failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21017 — Interface(%4): pAcmMediaChange failed, error %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): pAcmMediaChange failed, error %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21018 — Interface(%4): pAcmUIRequest failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): pAcmUIRequest failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21019 — Interface(%4): pAcmConnectionCompletionRoutine failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): pAcmConnectionCompletionRoutine failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21020 — Interface(%1): State Transition %3 --> %4.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%1): State Transition %3 --> %4

Fields

NameDescription
InterfaceGuid
InterfaceDescription
OldState
NewState

Event ID 21021 — Interface: Received AuthNotStarted result from 1x

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): Received AuthNotStarted result from 1x

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21022 — Interface: Received AuthInvalid result from 1x

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): Received AuthInvalid result from 1x

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21023 — Interface: Start processing event:

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%1): Start processing event: (%3)

Fields

NameDescription
InterfaceGuid
InterfaceDescription
EventId
Status

Event ID 21024 — Interface: Completed processing event:

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%1): Completed processing event: (%3)

Fields

NameDescription
InterfaceGuid
InterfaceDescription
EventId
Status

Event ID 21025 — Interface(%4): StartOneXAuth failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): StartOneXAuth failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21026 — Interface(%4): SendOneXPacket failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): SendOneXPacket failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21027 — Interface: TIMING OUT 802.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): TIMING OUT 802.1x Authentication

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21028 — Interface: NOT TIMING OUT 802.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): NOT TIMING OUT 802.1x authentication, next timer in %3 msec

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21029 — Interface(%4): DeviceLayerGetCurrentMediaState failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): DeviceLayerGetCurrentMediaState failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21030 — No 1X port exists.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

No 1X port exists. Ignoring the packet received

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21031 — Interface(%1): Set the SWITCH MAC address to %2.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%1): Set the SWITCH MAC address to %2

Fields

NameDescription
InterfaceGuid
InterfaceDescription
MACAddr

Event ID 21032 — Interface(%4): OpenDeviceHandle failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): OpenDeviceHandle failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21033 — Interface: Start processing event

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%1): Start processing event (%3)

Fields

NameDescription
InterfaceGuid
InterfaceDescription
EventId
Status

Event ID 21034 — Interface(%1): ProcessDot3MsmEvent: Dot3MsmPerformStateMachineProcessing FAILed (%4), Event=%3.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%1): ProcessDot3MsmEvent:  Dot3MsmPerformStateMachineProcessing FAILed (%4), Event=%3

Fields

NameDescription
InterfaceGuid
InterfaceDescription
EventId
Status

Event ID 21035 — Interface: Completed processing event

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%1): Completed processing event (%3)

Fields

NameDescription
InterfaceGuid
InterfaceDescription
EventId
Status

Event ID 21036 — Finished initializing a new interface with id = %1 and friendly name = %2.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Finished initializing a new interface with id = %1 and friendly name = %2

Fields

NameDescription
InterfaceGuid
InterfaceDescription
Location
Context

Event ID 21037 — Dot3MsmInit failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Dot3MsmInit failed %1

Fields

NameDescription
ErrorCode
Location
Context

Event ID 21038 — Dot3MSMInitAdapter failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Dot3MSMInitAdapter failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21039 — Failed to parse original request %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Failed to parse original request %1

Fields

NameDescription
ErrorCode
Location
Context

Event ID 21040 — Failed to parse UI Response %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Failed to parse UI Response %1

Fields

NameDescription
ErrorCode
Location
Context

Event ID 21041 — Interface(%4): OneXUIResponse failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): OneXUIResponse failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21042 — Interface(%4): Dot3MsmQueryPendingUIRequest failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

Interface(%4): Dot3MsmQueryPendingUIRequest failed %1

Fields

NameDescription
ErrorCode
Location
Context
InterfaceGuid
InterfaceDescription

Event ID 21043 — OneXValidateProfile failed %1.

Provider
Microsoft-Windows-Wired-AutoConfig
Channel
Diagnostic

Message

OneXValidateProfile failed %1

Fields

NameDescription
ErrorCode
Location
Context