Microsoft-Windows-WAS-ListenerAdapter

13 events across 2 channels

Event	Title	Channel	Sample
7001	Listener Adapter protocol 'ListenerAdapterProtocol' failed to connect to Windows …	Operational	N
7002	Listener Adapter protocol 'ListenerAdapterProtocol' is waiting to connect to …	Operational	N
7003	Listener Adapter protocol 'ListenerAdapterProtocol' successfully connected to …	Application	Y
7003	Listener Adapter protocol 'ListenerAdapterProtocol' successfully connected to …	Operational	Y
7004	Listener Adapter protocol 'ListenerAdapterProtocol' is unable to connect to …	Operational	N
7005	Listener Adapter protocol 'ListenerAdapterProtocol' attempted to communicate to …	Operational	N
7006	Listener Adapter protocol 'ListenerAdapterProtocol' received bad data from …	Operational	N
1073748826	Listener Adapter protocol 'ListenerAdapterProtocol' is waiting to connect to …	Operational	N
1073748827	Listener Adapter protocol 'ListenerAdapterProtocol' successfully connected to …	Operational	Y
2147490649	Listener Adapter protocol 'ListenerAdapterProtocol' failed to connect to Windows …	Operational	N
3221232476	Listener Adapter protocol 'ListenerAdapterProtocol' is unable to connect to …	Operational	N
3221232477	Listener Adapter protocol 'ListenerAdapterProtocol' attempted to communicate to …	Operational	N
3221232478	Listener Adapter protocol 'ListenerAdapterProtocol' received bad data from …	Operational	N

Event ID 7001: Listener Adapter protocol 'ListenerAdapterProtocol' failed to connect to Windows Process Activation Service due to identity permissions mismatch

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational

Fields #

Name	Description
`ListenerAdapterProtocol` UnicodeString
`ProcessID` UnicodeString

Event ID 7002: Listener Adapter protocol 'ListenerAdapterProtocol' is waiting to connect to Windows Process Activation Service

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational

Fields #

Name	Description
`ListenerAdapterProtocol` UnicodeString

Event ID 7003: Listener Adapter protocol 'ListenerAdapterProtocol' successfully connected to Windows Process Activation Service

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Application
Level: Informational

Fields #

Name	Description
`ListenerAdapterProtocol`

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-WAS-ListenerAdapter",
    "guid": "{D60ACC81-2608-4617-BFB7-2452BF002430}",
    "event_source_name": "WAS-LA",
    "event_id": 7003,
    "version": 0,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "keywords": 36028797018963968,
    "time_created": "2026-03-13T20:11:57.751575+00:00",
    "event_record_id": 3688,
    "correlation": {},
    "execution": {
      "process_id": 0,
      "thread_id": 0
    },
    "channel": "Application",
    "computer": "LAB-DC01.ludus.domain",
    "security": {
      "user_id": ""
    }
  },
  "event_data": {
    "ListenerAdapterProtocol": "net.tcp"
  },
  "message": ""
}

Event ID 7003: Listener Adapter protocol 'ListenerAdapterProtocol' successfully connected to Windows Process Activation Service

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational
Level: 4

Fields #

Name	Description
`ListenerAdapterProtocol` UnicodeString

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-WAS-ListenerAdapter",
    "event_id": 7003,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "time_created": "2026-03-13T20:11:57.7515758+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Application"
  },
  "event_data": {
    "ListenerAdapterProtocol": "net.tcp"
  }
}

Event ID 7004: Listener Adapter protocol 'ListenerAdapterProtocol' is unable to connect to Windows Process Activation Service because it has been disabled

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational

Fields #

Name	Description
`ListenerAdapterProtocol` UnicodeString

Event ID 7005: Listener Adapter protocol 'ListenerAdapterProtocol' attempted to communicate to Windows Process Activation Service and failed

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational

Fields #

Name	Description
`ListenerAdapterProtocol` UnicodeString

Event ID 7006: Listener Adapter protocol 'ListenerAdapterProtocol' received bad data from Windows Process Activation Service and is shutting itself down

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational

Fields #

Name	Description
`ListenerAdapterProtocol` UnicodeString

Event ID 1073748826: Listener Adapter protocol 'ListenerAdapterProtocol' is waiting to connect to Windows Process Activation Service.

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational

Description

Listener Adapter protocol 'ListenerAdapterProtocol' is waiting to connect to Windows Process Activation Service. This event will only be logged once. Cause: This could be caused by either Windows Process Activation Service not being started, the protocol not being configured in <listenerAdapters> section, or another process already connected as Listener Adapter for that protocol. Fix: Ensure that Windows Process Activation Service is running, the protocol is configured in the <listenerAdapters> section, and that another process has not already connected as the Listener Adapter for that protocol.

Message #

Listener Adapter protocol '%1' is waiting to connect to Windows Process Activation Service.  This event will only be logged once.  Cause: This could be caused by either Windows Process Activation Service not being started, the protocol not being configured in <listenerAdapters> section, or another process already connected as Listener Adapter for that protocol.  Fix: Ensure that Windows Process Activation Service is running, the protocol is configured in the <listenerAdapters> section, and that another process has not already connected as the Listener Adapter for that protocol.

Fields #

Name	Description
`ListenerAdapterProtocol`

Event ID 1073748827: Listener Adapter protocol 'ListenerAdapterProtocol' successfully connected to Windows Process Activation Service.

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational
Level: 4

Description

Listener Adapter protocol 'ListenerAdapterProtocol' successfully connected to Windows Process Activation Service.

Message #

Listener Adapter protocol '%1' successfully connected to Windows Process Activation Service.

Fields #

Name	Description
`ListenerAdapterProtocol`

Example Event #

{
  "system": {
    "provider": "Microsoft-Windows-WAS-ListenerAdapter",
    "event_id": 7003,
    "level": 4,
    "task": 0,
    "opcode": 0,
    "time_created": "2026-03-13T20:11:57.7515758+00:00",
    "computer": "JD-DC01-2022.ludus.domain",
    "channel": "Application"
  },
  "event_data": {
    "ListenerAdapterProtocol": "net.tcp"
  }
}

Event ID 2147490649: Listener Adapter protocol 'ListenerAdapterProtocol' failed to connect to Windows Process Activation Service due to identity permissions mismatch.

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational

Description

Listener Adapter protocol 'ListenerAdapterProtocol' failed to connect to Windows Process Activation Service due to identity permissions mismatch. Cause: Configured Identity for protocol 'ListenerAdapterProtocol' in applicationHost.config does not match identity of process 'ProcessID' hosting Listener Adapter. Fix: Ensure that the identity for protocol 'ListenerAdapterProtocol' is configured correctly in applicationHost.config.

Message #

Listener Adapter protocol '%1' failed to connect to Windows Process Activation Service due to identity permissions mismatch.  Cause: Configured Identity for protocol '%1' in applicationHost.config does not match identity of process '%2' hosting Listener Adapter.  Fix: Ensure that the identity for protocol '%1' is configured correctly in applicationHost.config.

Fields #

Name	Description
`ListenerAdapterProtocol`
`ProcessID`

Event ID 3221232476: Listener Adapter protocol 'ListenerAdapterProtocol' is unable to connect to Windows Process Activation Service because it has been disabled.

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational

Description

Listener Adapter protocol 'ListenerAdapterProtocol' is unable to connect to Windows Process Activation Service because it has been disabled. Cause: Listener Adapter protocol 'ListenerAdapterProtocol' has been marked as disabled by Windows Process Activation Service due catastrophic failure. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.

Message #

Listener Adapter protocol '%1' is unable to connect to Windows Process Activation Service because it has been disabled.  Cause: Listener Adapter protocol '%1' has been marked as disabled by Windows Process Activation Service due catastrophic failure.  Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.

Fields #

Name	Description
`ListenerAdapterProtocol`

Event ID 3221232477: Listener Adapter protocol 'ListenerAdapterProtocol' attempted to communicate to Windows Process Activation Service and failed.

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational

Description

Listener Adapter protocol 'ListenerAdapterProtocol' attempted to communicate to Windows Process Activation Service and failed. The Listener Adapter is now in a bad state. Cause: This is caused by Out of Memory issues or failures between Windows Process Activation Service and Listener Adapter. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.

Message #

Listener Adapter protocol '%1' attempted to communicate to Windows Process Activation Service and failed. The Listener Adapter is now in a bad state.  Cause: This is caused by Out of Memory issues or failures between Windows Process Activation Service and Listener Adapter.  Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.

Fields #

Name	Description
`ListenerAdapterProtocol`

Event ID 3221232478: Listener Adapter protocol 'ListenerAdapterProtocol' received bad data from Windows Process Activation Service and is shutting itself down.

Provider: Microsoft-Windows-WAS-ListenerAdapter
Channel: Operational

Description

Listener Adapter protocol 'ListenerAdapterProtocol' received bad data from Windows Process Activation Service and is shutting itself down. Cause: Listener Adapter received bad data from Windows Process Activation Service. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.

Message #

Listener Adapter protocol '%1' received bad data from Windows Process Activation Service and is shutting itself down.  Cause: Listener Adapter received bad data from Windows Process Activation Service. Fix: To fix this condition, stop Listener Adapter then Windows Process Activation Service, restart Windows Process Activation Service, and finally restart Listener Adapter.

Fields #

Name	Description
`ListenerAdapterProtocol`

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID d60acc81-2608-4617-bfb7-2452bf002430

Defined in iisres.dll, which carries the event manifest.

Observed on:

WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.1, captured 2026-06-02

Downloads

Microsoft-Windows-WAS-ListenerAdapter registered manifest XML (in the WS2022-20348.4893 manifest pack, 1.9 MB) manifest-xml

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)