When logging to a remote system, either when performing an archive, logging to a file or logging to a database, and you find that using the 'test' button works, but the logging does not, then this is probably due to the fact that Kiwi Syslog Daemon does not have sufficient permission to write to the remote system.

When doing a test from the Service Manager, the program uses the permissions of the currently logged in user and all their privileges. However, when actually logging from the service, the program is using the "Local System" account by default. This login does not usually have enough permissions to connect to remote systems.

We recommend you create the same username (such as "Syslog") on both systems, and give them the same password and permissions to access the disk and map drives (Administrator access to start with). Then set Kiwi Syslog Service to login with the new username. This can be done from the Windows Services manager (Start | Programs | Administrative Tools | Services).

A reboot will be required for the changes to take effect.

If you have created a "Log to ODBC database" Action, then you will also need to check that you have specified a "System DSN" and not a "User DSN" by mistake, as services require the use of a "System DSN".

Another thing that you will need to check; is that you are not using mapped drives to specify the location of your flatfile or database table. Mapped drives are created by the user who is currently logged into the system. If the Kiwi Syslog Daemon service is not using the same login then it will not be able to see these drives. We recommend that instead of using mapped drives you use UNC naming.

For example \\remotesystem\remotepath\remotefile.txt

If the problem listed above still exists after following the instructions provided, then please use the technical support form to receive further assistance.