WinSyslog Event ID 11189: Input service could not find its assigned ruleset#

Answer#

A configured input service references a ruleset that does not exist. Because that service requires a ruleset, the product does not start it.

Event ID: 11189
Severity: Error
Component: Service configuration
Windows Event Log source: AdisconWinSyslog
Available since: 26.07
Message pattern: No ruleset was found for service ‘{service_name}’; requested ruleset was ‘{ruleset_name}’. The service was not started.

Open the affected service and record its assigned ruleset.
Confirm that a ruleset with that exact name exists.
Correct the assignment or restore the ruleset, then validate and reload the configuration.

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.

Confirm that the input service starts and a controlled event reaches the assigned ruleset without Event ID 11189.

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.

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