Fields #

Fields #

Fields #

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": ""
}

Fields #

Fields #

Fields #

Fields #

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.

Description

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

Message #

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

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.

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.

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.

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.