How do I resolve driver errors when I use MySQL with EventSentry?

Below are some common MySQL driver errors and their recommended solutions.

When installing the driver, or after it has been installed and the connection is being utilized, you may experience the following error:
Specified driver could not be loaded due to system error 126: The specified module could not be found

Solution: Install the Microsoft Visual C++ Runtime 2010 version that applies to your server:
x64 runtime: https://www.microsoft.com/en-us/download/details.aspx?id=14632
x86 runtime: https://www.microsoft.com/en-us/download/confirmation.aspx?id=5555
IMPORTANT: If the EventSentry server itself is 64-bit, for 3.3 series and newer it will need both the x64 and x86 runtimes installed

The agent may experience one of these errors at random:
OdbcExpandError: [08S01] [MySQL][ODBC 5.3 Driver]MySQL server has gone away (2006)
OdbcExpandError: [08S01] [MySQL][ODBC 5.3 Driver]Lost connection to MySQL server during query (2013)

Solution: Use the MySQL 5.1 driver, it is the most stable and is not known to randomly disconnect or drop connections. The driver can be found in the "C:\Program Files (x86)\EventSentry\mysql" folder on the EventSentry server.
IMPORTANT: Update your database connection string in the EventSentry console ( https://www.eventsentry.com/documentation/help/html/?targetsodbc.htm ) to reference the new driver name and then push the new settings and remotely restart the agent services for the driver change to take effect. You should also click Home > Services in the EventSentry console toolbar and restart all of the listed components.