6
responses

We are running into errors running nxlog-ce on Windows 2016. When is this going to be supported? Our only alternative is to move to Beats which will happen quickly if there is no ETA on this.

Here are some examples of the errors we see: 2018-01-11 14:34:22 WARNING got ERROR_INVALID_PARAMETER (errorcode: 87) for the Security log, will try to reopen in 512 sec. ReadFromLast is TRUE and will try to restart from the last position. This might result in uncollected logs. 2018-01-11 14:34:22 WARNING got ERROR_INVALID_PARAMETER (errorcode: 87) for the Windows PowerShell log, will try to reopen in 512 sec. ReadFromLast is TRUE and will try to restart from the last position. This might result in uncollected logs.=

AskedJanuary 17, 2018 - 4:02pm

Comments (6)

  • dbreise's picture

    im_mvistalog is the correct module to use for +2003 Window. However, I'm having problems with that module on Server 2016 and I haven't found a solution yet:

    <11>Mar 23 11:32:43 ************ MSWinEventLog 4 N/A N/A Fri Mar 23 11:32:43 2018 N/A nxlog-ce N/A N/A N/A ************ N/A ### ASSERTION FAILED at line 319 in im_msvistalog.c/im_msvistalog_event_to_logdata(): "event != NULL" ### N/A

Answers (0)