|
Solutions for common problems with the ODBC target:
| • | If you are using DSN names then make sure that the DSN name you specified is a System DSN. User DSN names are not supported. |
| • | The DSN name you specified must match an existing System DSN that points to the correct database. These data source names (DSN) need to be setup on every computer where the EventSentry agent/service is installed. You can use AutoAdministrator to easily roll out data source names to multiple computers. |
| • | Make sure that all the necessary ODBC drivers for your database server are installed correctly on the host where EventSentry is installed. Microsoft Windows 2000 and higher ship with SQL Server and MS Access drivers installed by default. All other drivers will have to be installed manually. |
| • | The database needs to be setup as described in the previous chapter. |
| • | When attempting to write to a MS Access database that is located on a different server you will need to perform additional steps: |
| 1. | Reconfigure the EventSentry agent (service) to use a user account other than LocalSystem |
| 2. | Give Everyone permission to write to the Access database (not recommended). |
| 3. | Windows 2000 and higher: Give write permissions to the computer accounts (e.g. COMPUTER$), this will give permission to the LocalSystem account of the respective computer. |
Please refer to the troubleshooting FAQ (file target) for more information, this permission issue also applies to the file target.
|