To use a MySQL Database with WinSyslog, EventReporter or MonitorWare Agent, you need to install some components (If you haven’t) first. Go to https://www.mysql.com/downloads/index.html. If you don’t have any MySQL Server, download MySQL-3.23.5 for Windows for example (Or a newer version if there is one). Most important, you need to download an install the ODBC […]

All Cisco products we know support logging to a syslog host like WinSyslog. This article covers all devices that use IOS (e. g. routers and switches). Syslog logging needs both to be configured as well as turned on. To configure, you must be in enable mode (see your Cisco documentation on how to enter enable […]

What are the numeric values for event severity levels? The severity of an event describes the importance of an event. These severity levels are represented by numeric values. Those values are: Severity Numeric value SUCCESS 1 ERROR 2 WARNING 4 INFORMATION 8 AUDIT_SUCCESS 16 AUDIT_FAILURE 32

I know that the Windows event log size settings are not optimal. So how can I change them and what are better values? Indeed, the default settings are just 512 KB and overwrite after 7 days. While the 512 KB settings do not actually pose a problem the 7 day overwrite does. Effectively, this means […]

Many Adiscon products (e.g. WinSyslog and EventReporter) come with an online version checking feature. This feature is implemented via Microsoft’s XML parser. Unfortunately, we had to learn the the redistributable XML parser component does not properly setup on some machines. As far as we have found out, it does not install correctly if no Internet […]

Message: “Couldn’t read last record for Security log (state 87) – nLastRecord set to 0 to recover.” This actually is no error, but a status message. There can be three reasons for this message: This message occurs when by any chance the last entry in the event log gets deleted. By the network administrator or […]

When EventReporter is configured to send email message, several SMTP error codes might happen while connecting to the mail server. These are: Error Cause Suggested Action -1 EventReporter could not at all connect to the mail server. Check that the mail server’s IP address or host name is correctly configured. Check that the port used […]

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) What happens? EventReporter is sending an […]

Unfortunately, there is no general answer to this questions. However, we have learned that in the majority of cases on of the following issues is causing the problem: Check the facility EventReporter is using when sending messages By default, EventReporter sends to the LOCAL_0 facility. This default can be changed with the EventReporter client. Be […]

NT Event log severities are mapped as follows: NT SYSLOG EVENTLOG_AUDIT_SUCCESS LOG_NOTICE EVENTLOG_INFORMATION_TYPE LOG_NOTICE EVENTLOG_AUDIT_FAILURE LOG_WARNING EVENTLOG_WARNING_TYPE LOG_WARNING EVENTLOG_ERROR_TYPE LOG_ERR