This happens under seldom circumstances, if the following things are true:
- EventReporter and WinSyslog are running on the same machine.
- EventReporter is configured to send Eventlog entries to WinSyslog (127.0.0.1 for example)
- Some actions defined in WinSyslog are generating an error (Which is also written into the NT Eventlog)
EventReporter is sending an Eventlog entry to the local WinSyslog. The Ruleset is processed by WinSyslog and an action (ODBC-Logging for example) causes an error (Maybe the database server is down). WinSyslog writtes this error into the NT Eventlog. Next time EventReporter wakes up, the whole process repeats and that is causing the high CPU utilization.
To solve this problem stop the EventReporter Service and check the WinSyslog Ruleset for any errors and try to solve them. If you don’t have success, then please contact Adiscon Support for help.