Customer area
Your Syslog program helped me catch a hacker in action!
Loading...
INFO: Kiwi Syslog Daemon Service fails to start

Under most operating systems, the Kiwi Syslog Daemon Service will start without problems.
On some Windows 2000 Server systems, the Kiwi Syslog Daemon Service may have to wait for other system services to start, before it can start. If this is the case, you may see the error message "One or more system services failed to start" or "service hung on starting" (Event ID 7022) on the console after a reboot.

To ensure that the required services have started before Kiwi Syslog Daemon is started, you will need to modify the following registry setting:

Section: HKEY_LOCAL_MACHINE/SOFTWARE/Kiwi Enterprises/Syslogd/Properties

Value (STRING): NTServiceDependencies

Default value: Blank
Type: Text string of service names. Delimited by semi-colons.

E.g. ServiceName1;ServiceName2;ServiceName3


How to add service dependencies:

· Uninstall the service from the Manage menu

· Run RegEdit

· Locate the section "HKEY_LOCAL_MACHINE/SOFTWARE/Kiwi Enterprises/Syslogd/Properties"

· Create the new string value of "NTServiceDependencies"

· Modify the value data to include the list of services that need to start first

· E.g. "LanmanWorkstation;TCPIP;WMI" (without the quotes)

· Install the service from the Manage menu


The above will ensure that the Workstation, WMI (Windows Management Interface) and TCP/IP stack services are running, before trying to start the Kiwi Syslog Daemon Service.
0 votes so far for this article. Did this article help you? YES NO