Kiwi Syslog Won't start

Is there anything else listening on port 514?

You can also go into Setup, and then Inputs.  Click on UDP, and deselect Listen for UDP Syslog messages.  Next try to start the service.  If is starts, I would get a Wireshark capture and check the volume of syslog messages coming in.

Just thought I'd reply to this since I have the exact same error, and I'm *also* using this to capture data from an Avaya phone system.

The problem in my case was that under Inputs > TCP, I had set the "Bind to address" field to the IP of my phone system, but that's not correct.  I removed the address from that field and left it blank and presto - I get logging!

I think that field might be for if you're running it on a server with multiple interfaces/IPs, it will need to know which to listen on. Not sure though.

I am on windows 10 Pro with all updates, version 21H1 build 19043.1151

I confirm nothing else on port 514 by running 'netstat -ano'. 

The problem is this message is reported on startup, so you can't get into the setup menu.

THE FOLLOWING INTERNAL PROGRAM ERROR HAS OCCURRED:

Standard Version = 9.7.2.1
Error Number: -2146233087
Description: Could not bind server socket: The requested address is not valid in its context
Module Name: Syslogd.frm
Procedure Name: InitialiseSockets
Line Number: 150

error log has this init:  "C:\Program Files (x86)\Syslogd\Errorlog.txt"

2021-08-08 14:13:32 *** INTERNAL PROGRAM ERROR - Please contact www.kiwisyslog.com/.../ ***
2021-08-08 14:13:32 Standard Version = 9.7.2.1 | Error Number: -2146233087 | Description: Could not bind server socket: The requested address is not valid in its context | Module Name: Syslogd.frm | Procedure Name: InitialiseSockets | Line Number: 150 | Date and time: 8/8/2021 2:13:32 PM