Customer area
It puts your product out as the clear choice for potential buyers.
Loading...
ERROR: Problems getting Kiwi Syslog Daemon to log to a database

Problem:

"I am not getting messages logged to my database, but the test button works fine. What's wrong?"

Details...

You have installed Kiwi Syslog Daemon as a Windows service and have created a "Log to database" action that appears to be correctly configured.

You can create the table, insert test records and query the results back using the buttons provided on the "Log to database" action.

This all works fine in testing however you find that when Kiwi Syslog Daemon is receiving actual live data none of these records are being inserted into the table even though they match the conditions defined in the Rule?

Solution:

We find that this kind of issue is either related to the fact that a User DSN has possibly been set up rather than a System DSN (which is required by the service to do the actual logging) or else the account that the service is using does not have sufficient rights to log to the database table specified.

Currently when you press the Test button the logging gets performed by the current user that is logged in, ie. yourself - using your permissions. However when the service tries to write to the database it uses it's own settings based on the account that it has been installed under. This is usually LocalSystem which normally does not have sufficient permission.

In these cases we recommend that you change the service account to be something that has sufficient rights to log to the database. This can be done by either re-running the installation package and changing the default service account to use. Or it can be done from the Windows > Services control panel applet.

Another place that we recommend you check is in the Kiwi Syslog Daemon Errorlog.txt file. This file is located in the Kiwi Syslog Daemon installation folder. It may contain information relating to the connection of the database. For example; lack of permissions with the current user, incorrect login information etc. etc.

If you find that you have checked ALL these things and still can not get the logging to work then do not panic. Visit our support page, open a support case and one of our dedicated support staff will get back to you in no time at all.
100 % of 1 voters found this article helpful - Did you? YES NO