Large eventlog entries makes nxlog "hang"

View thread

MagnusBjarnlid

We are using nxlog to collect eventlog information. Some entries can be large, in fact some message are split over several entries as a workaround for the maximum eventlog entry size. However, these large entries seem to hang nxlog so that it stops processing new entries. Typical error messages are:

---------------------------------------

2014-10-27 17:10:32 ERROR EvtNext failed with error 1734: The array bounds are invalid.  
2014-10-27 17:10:33 ERROR EvtUpdateBookmark failed: The handle is invalid.

----------------------------------------

Why is this? Is there any workaround?