im_msvistalog - Maximum Event Log Count Support

We have two Windows Server 2012 R2 servers with nxlog installed and several applications with their own event logs installed. Server 'A' has 260 event logs (including all of the default Microsoft event logs), server 'B' has 250.

When using the below configuration on Server 'A' the message "Couldn't read next event, corrupted eventlog?" is logged to the nxlog log file when starting the nxlog service - no events are forwarded to our LogStash instance, this behaviour does not happen on Server 'B':

<Input eventlog>

    Module      im_msvistalog

Support ticket opened onFebruary 26, 2016 - 4:23pm

nxlog-ce 2.9.1504 crashing continously


I was using version 2.8.1248, when "ERROR Failed to retrieve eventlog user data; The parameter is incorrect." started to appear. After upgrade to 2.9.1504 that error was gone, but NXlog kept on crashing, without any error message this time. NXlog crashes every time, after a couple of minutes running. There is no any outstanding messages in the logfile, even with DEBUG LogLevel set. In the event log there is an Application Error:

Support ticket opened onJanuary 25, 2016 - 1:25pm

NXlog service needs to be restarted to resume sending logs.

Hi guys,

I've got nxlog installed on a handful of Windows machines, forwarding event logs in a test environment.  I've noticed that if I restart the server receiving the logs, the clients won't resume sending until I've restarted the nxlog service.  Has anyone come up with a way around this?

The log file simply has many instances of:

Support ticket opened onNovember 20, 2015 - 5:29pm