Knowledge Base


When using ODBC targets you will need to make sure that: The System DSN referenced in the ODBC target is present on all computers writing to the database. This requirement does not apply to version 2.50 and higher which also supports connection strings. Otherwise you can use AutoAdministrator to push out DSN names to remote machines. ...

KB-ID 11
Category: Notifications
Applies to:

Some AntiVirus software products e.g. McAfee starting with version 8.x block and/or intercept outgoing connections to port 25. This will interfere with the EventSentry SMTP notification target which sends emails using SMTP port 25. You will need to disable or customize the SMTP protection feature of your antivirus product to make the SMTP...

KB-ID 17
Category: Notifications
Applies to:

This is usually a permissions issue since the EventSentry agent is running under the LocalSystem account by default. Please click the help link below DOCID 18 for more information.

KB-ID 20
Category: Notifications
Applies to:

This is usually a permissions issue since the EventSentry agent is running under the LocalSystem account by default. Please click the help link below DOCID 18 for more information.

KB-ID 19
Category: Notifications
Applies to:

This is usually due to an incorrectly configured System DSN. When configuring the DSN make sure that the SQL Server authentication type is set to With SQL Server authentication using a login ID and password entered by the user. If set to Windows NT authentication the EventSentry agent will attempt to connect to the database using the s...

KB-ID 24
Category: Notifications
Applies to:

This inconsistency only applies to entries written to the database by the TEST button. Regular entries written by the agents will show the time in your local time zone. This problem has been resolved in version 2.50 where the TEST button will generate a correct date.

KB-ID 26
Category: Notifications
Applies to: up to v2.43

While it is possible for multiple EventSentry agents to write to the same file it is not recommended. A file is always locked during a write operation which will prevent concurrent access to the file and might result in data loss.

KB-ID 31
Category: Notifications
Applies to:

This depends on the notifications used. Below you can find a list of the standard ports used for the support notifications in EventSentry. Deploy Manage or Update agent: Port 445 TCP cannot be changed Collector: Port 5001 TCP configurable Email SMTPWithout Collector: Port 25 TCP configurable Syslog: Port 514 UDP and/or...

KB-ID 40
Category: Notifications
Applies to: All Versions

There are a number of reasons why you might not be receiving emails from the remote machines running the EventSentry agents. Please check each step below to resolve this problem: Make sure that your AntiVirus e.g. McAfee software is not blocking outgoing emails to port 25. See the additional links below for more information. Make sur...

KB-ID 61
Category: Notifications
Applies to:

Yes you can use EventSentry with MSDE however we do not recommend it as it provides limited administration capabilities and requires you to do many configuration changes through the registry. When installing MSDE make sure that you enable both SQL and Windows mixed authentication. If you have already installed MSDE and need to turn on mi...

KB-ID 68
Category: Notifications
Applies to: