WinSyslog Event ID 11160: Corrupt log-rotation queue file was quarantined#

Answer#

The product detected an invalid durable log-rotation queue and successfully renamed it for quarantine. The invalid queue is not loaded; new rotation work can use a new queue file.

Event details#

  • Event ID: 11160

  • Severity: Warning

  • Component: Log rotation queue

  • Windows Event Log source: AdisconWinSyslog

  • Available since: 26.07

  • Message pattern: {reason} Renamed to: {quarantine_path}

Possible causes#

  • The previous service run ended while queue state was being persisted.

  • The queue file was externally modified or damaged.

  • Storage or backup software produced incomplete queue contents.

Immediate checks#

  1. Preserve the quarantined file for analysis and record its path.

  2. Check neighboring shutdown, storage, and file-system events.

  3. Verify that a new queue file is created and inspect whether any rotated files from the quarantined jobs remain pending.

Detailed procedures#

Verify the result#

Confirm that new log rotations complete and durable queue state can be saved and reloaded.

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#

This event normally records state rather than a failure. Escalate only when the state was unexpected or the associated operation does not recover.