WinSyslog Event ID 11222: Consumed log-rotation queue file could not be deleted#

Answer#

The product loaded and consumed the durable log-rotation jobs, but could not delete the queue file afterward. Completed job keys remain tracked to avoid reprocessing them during the current run.

Event details#

  • Event ID: 11222

  • Severity: Warning

  • Component: Log rotation queue

  • Windows Event Log source: AdisconWinSyslog

  • Available since: 26.07

  • Message pattern: Could not delete consumed log rotation queue file: {queue_path}

Possible causes#

  • The queue file is locked by another process.

  • The service account lacks delete permission in the data directory.

  • Antivirus, backup, or storage software is holding the file.

Immediate checks#

  1. Confirm that the loaded rotation jobs were processed before changing the queue file.

  2. Check file locks and delete permission in the product data directory.

  3. Remove the blocking condition and allow cleanup to retry; preserve the file if job state is uncertain.

Detailed procedures#

Verify the result#

Confirm that the consumed queue file is removed and a controlled restart does not reprocess completed rotations.

Evidence to collect#

  • The complete Windows Application Event Log entry and neighboring product events from the same time window.

  • The exact product version, affected service or action name, and event timestamp with time zone.

  • The affected configuration object and a bounded debug log covering one controlled reproduction.

  • Remove passwords, tokens, license data, private keys, message payloads, personal data, and customer-identifying names, addresses, hostnames, domains, and network addresses before sharing evidence.

Escalation#

If the event continues after the detailed procedures, collect the listed evidence and contact Adiscon Support.