I am getting this error: (event ID 1001)
A configured syslog server service can not be started. Most often, this happens when more than one syslog server service is configured to use the same port and protocol, e.g. 514/UDP. Please make sure that only a single syslog server is defined to listen on the same port and protocol. If you would like to do multiple actions, this can be done within a single rule set that is bound to a single syslog server service. The socket subsystem reported the following reason: “Can’t bind to socket – have given up after 60 seconds…”
on a windows XP pro box running SP2, fully updated. Now, we have GFI Event Manager that is using a syslog server to kick out info on port 5140, and I am trying to find out what it is conflict with?!? Is there a command I can run that will tell me all applicable syslog servers? Anyone have any ideas how I can resolve this?