ESET Security Management Center Login Failed: Connection has failed with the state Not connected

[Andy]

You receive the error message: Login Failed: Connection has failed with the state of 'Not connected'

This error message means that there is an issue with the connection between Webserver and ESMC Server or the ESMC Server and ESMC Database (but the connection between the Browser and Webserver is probably working).

In that case, we want to investigate the connection between ESMC Server and ESMC Database.

On the ESMC console, type in:

[root@av ~]# odbcinst-q -d
[MySQL ODBC 5.3 Unicode Driver]
[MySQL ODBC 5.3 ANSI Driver]
[root@av ~]#

You may have the different ODBC driver, but to confirm, let's have an additional look by using the concatenate (cat command) on this file: /etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini

If the output is:

DatabaseType=MySqlOdbc
DatabaseConnectionString=Driver=MySQL ODBC 5.3 Unicode Driver;Server=...

Then congratulations! We have found the root cause. The problem appears ESMC Server can't talk with ESMC Database due to incompatible ODBC driver, this most likely caused by the OS update (yum update).

Here's the solution for this issue:

• We want to remove the currently installed ODBC driver, type:

  yum remove mysql-connector-odbc.x86_64

• Then install the compatible 5.3 ODBC driver, type:

  wget https://downloads.mysql.com/archives/get/file/mysql-connector-odbc-5.3.10-1.el7.x86_64.rpm
  chmod +x mysql-connector-odbc-5.3.10-1.el7.x86_64.rpm
  yum localinstall mysql-connector-odbc-5.3.10-1.el7.x86_64.rpm

• Restart the server and your ESMC should now back online.

For your reference, I'm using the official ESET Remote Administrator Appliance (Hyper-V version), which I believe it's derived from CentOS:

[root@av ~]# uname -a
Linux av.genesis.saputra.org 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@av ~]#

Let me know if you find this article useful by commenting down below, you can also ask me any questions. Cheers

 

[Anon12345678]

I know this is two years later but I found this thread while searching for a solution for this problem and you nailed the exact problem. Downgrading the mysql-connector-odbc package solved the issue, though it seems mysql might have changed their URL scheme a little bit so I had to find the download from https://downloads.mysql.com/archives/c-odbc/

Thanks for putting this together!

 

[Andy]

I know this is two years later but I found this thread while searching for a solution for this problem and you nailed the exact problem. Downgrading the mysql-connector-odbc package solved the issue, though it seems mysql might have changed their URL scheme a little bit so I had to find the download from https://downloads.mysql.com/archives/c-odbc/

Thanks for putting this together!

Thanks for your feedback, as well as the URL update. Cheers

 

[jruiz]

Hi, I am facing the same error after updating the Eset protect to 10.0.2133.0

On /etc/odbcinst.ini file I have defined the following drivers.

[MySQL ODBC 8.0 Unicode Driver]
Driver=/usr/lib64/libmyodbc8w.so
UsageCount=2

[MySQL ODBC 8.0 ANSI Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=2

[MySQL]
Description=ODBC for MySQL
Driver=/usr/lib64/libmyodbc8w.so
Setup=/usr/lib64/libodbcmyS.so
FileUsage=1
UsageCount=2

And on the /StartupConfiguration.ini

DatabaseType=MySqlOdbc
DatabaseConnectionString=Driver=MySQL ODBC 8.0 Unicode Driver;Server=127.0.0.1;Port=3306;User=era;Password={XXXXXXXXXXXXXXXX}
;CharSet=utf8;NO_LOCALE=1;NO_SSPS=1;Database=era_db;

Should I downgrade to some version? To what exactly?

I am using the ESET Remote Administrator Appliance (Vsphere), derived from CentOS.

Thanks in advance.

 

[Andy]

Hi @jruiz, you'll need to downgrade the ODBC driver to version 5.3

 

[jruiz]

Hi @jruiz, you'll need to downgrade the ODBC driver to version 5.3

No luck...
Removed 8 version as you mentioned.

Installed the 5.3 version.
Installed Packages
mysql-connector-odbc.x86_64 5.3.10-1.el7 @/mysql-connector-odbc-5.3.10-1.el7.x86_64

Updated StartupConfiguration.ini accordingly
DatabaseType=MySqlOdbc
DatabaseConnectionString=Driver=MySQL ODBC 5.3 Unicode Driver;Server=127.0.0.1;Port=3306;User=era;Password={XXXXXX};CharSet=utf8;NO_LOCALE=1;NO_SSPS=1;Database=era_db;

odbcinst.ini content
[PostgreSQL]
Description=ODBC for PostgreSQL
Driver=/usr/lib/psqlodbcw.so
Setup=/usr/lib/libodbcpsqlS.so
Driver64=/usr/lib64/psqlodbcw.so
Setup64=/usr/lib64/libodbcpsqlS.so
FileUsage=1
UsageCount=5

[MySQL ODBC 5.3 Unicode Driver]
Driver=/usr/lib64/libmyodbc5w.so
UsageCount=4

[MySQL ODBC 5.3 ANSI Driver]
Driver=/usr/lib64/libmyodbc5a.so
UsageCount=4


Checked that the file exists:
-rwxr-xr-x. 1 root root 4871024 Jan 19 2018 /usr/lib64/libmyodbc5w.so

And finally rebooted the system.

Any ideas?

 

[Andy]

@jruiz: Sorry for the delayed response. I just came back from the Christmas-New Year holiday.
Please ensure you're using the original ESET Remote Administrator Appliance from ESET.

 

[jruiz]

@jruiz: Sorry for the delayed response. I just came back from the Christmas-New Year holiday.
Please ensure you're using the original ESET Remote Administrator Appliance from ESET.

I was using the original.
Finally I resolved creating a new virtual appliance and restoring the backup I did previously.
Thanks anyway!!

 

[Andy]

I was using the original.
Finally I resolved creating a new virtual appliance and restoring the backup I did previously.
Thanks anyway!!

Great to hear that you were able to resolve the issue by creating a new virtual appliance and restoring the backup.
Avoid updating system packages manually using apt, as it can cause issues.
Let me know if you need any further assistance in the future.