WinSyslog Event ID 11183: Configuration reload was skipped because the log-rotation scheduler did not stop#

Answer#

The product could not stop the existing log-rotation scheduler within the reload timeout. It keeps the current scheduler owner alive and does not apply the requested configuration reload.

Event details#

Event ID: 11183
Severity: Warning
Component: Configuration reload
Windows Event Log source: AdisconWinSyslog
Available since: 26.07
Message pattern: Configuration reload skipped because the log rotation scheduler did not stop before its bounded timeout.

Possible causes#

A rotation, compression, or archive operation is still active or blocked.
The archive destination is slow or unavailable.
The bounded stop timeout expired before scheduler shutdown completed.

Immediate checks#

Confirm that the current configuration remains active.
Inspect pending rotation work, archive availability, file locks, and storage performance.
Allow the scheduler to finish and perform one controlled reload.

Detailed procedures#

Diagnose log rotation and retention — Verify trigger, names, handles, destination access, and retention.
Validate configuration and reload it safely — Back up, inspect, correct, and test the exact invalid configuration object.
Collect an Event ID and neighboring product events — Preserve the complete event and the product events immediately before and after it.
Export configuration and collect a bounded debug log — Create a text configuration export and time-bounded debug capture, then disable debugging.

Verify the result#

Confirm that the later reload succeeds and the intended configuration becomes active without Event ID 11183.

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.