1
answer
new

Issue nxlog on windows 2012 server and run dhcp server

Hi all
We have been forced some issue here we try to start nxlog service and every 00.00 a.m. event log dhcp occured error and if we stop run this service error not occured. Please let us know how to solve this issue.
Please help us on this matter.
Looking forward to your reply.
Thank you.

Support ticket opened onSeptember 29, 2017 - 6:24am
4
answers
active

im_wseventing and ssl certificates

__________________Issue___________________

We are unclear on the proper certificate practice for im_wseventing. We have attempted to generate some self signed certs to use on our local network, but have run into this error:

2017-04-28 14:22:55 INFO Connection accepted from 10.X.X.64:56036
2017-04-28 14:22:55 ERROR im_wseventing got disconnected during SSL handshake

 

Below is our config, and we believe this to be an issue with SSL.

 

We followed the instructions found in both the user guide and the manual.

Support ticket opened onApril 28, 2017 - 8:28pm
8
answers
active

Error 1401. System error 87. When trying install under win32process

MSI (s) (E4:9C) [19:13:39:684]: Product: NXLog-CE -- Error 1401. Could not create key: S-1-5-21-1688939787-1905098679-239004068-17022\Software\Microsoft.  System error 87.  Verify that you have sufficient access to that key, or contact your support personnel.

Error 1401. Could not create key: S-1-5-21-1688939787-1905098679-239004068-17022\Software\Microsoft.  System error 87.  Verify that you have sufficient access to that key, or contact your support personnel.

when using this method as part of a script...

Support ticket opened onMarch 29, 2017 - 6:35pm
2
answers
active

Laptop Problem with Socket Connection

We are using the community edition and are having this problem with Windows 7 laptops:

Support ticket opened onFebruary 28, 2017 - 7:10pm
4
answers
active

Issue with nxlog Windows service

Hello,

It seems that there is some kind of conflict or bug in nxlog-ce-2.8.1248 (I'm not sure about earlier versions) where, upon boot, nxlog gets stuck in a loop initiating connections to a remote machine (Logstash in my case using om_tcp).

I only became aware of this after installing nxlog on server that had the group policy "Audit Filtering Platform Connection" enabled on successful connections; this actually generated so many events that it filled up my elasticsearch cluster (I've attached a sample of the event the filled the cluster).

Support ticket opened onSeptember 17, 2014 - 3:40pm