• Most COVID-19 rules have ended in New Zealand.
    • You must still isolate for 7 days if you have COVID-19.
    • You must wear a face mask in healthcare facilities, such as hospitals. International travellers will not need proof of COVID-19 vaccination.
    From 13 September 2022, to enter New Zealand, you do not need proof of vaccination.

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

Andy

Administrator
Creative Team
User ID
1
Joined
7 Jan 2019
Messages
771
Reaction score
32
Points
28
You receive the error message: Login Failed: Connection has failed with the state of 'Not connected'

eset-smc.png

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:
Bash:
[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:
Bash:
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:
    Bash:
    yum remove mysql-connector-odbc.x86_64
  • Then install the compatible 5.3 ODBC driver, type:
    Bash:
    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:
Bash:
[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

New member
User ID
937
Joined
5 Jan 2022
Messages
1
Reaction score
1
Points
3
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

Administrator
Creative Team
User ID
1
Joined
7 Jan 2019
Messages
771
Reaction score
32
Points
28
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

New member
User ID
1136
Joined
12 Nov 2022
Messages
2
Reaction score
0
Points
1
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

Administrator
Creative Team
User ID
1
Joined
7 Jan 2019
Messages
771
Reaction score
32
Points
28
Hi @jruiz, you'll need to downgrade the ODBC driver to version 5.3 👍
 

jruiz

New member
User ID
1136
Joined
12 Nov 2022
Messages
2
Reaction score
0
Points
1
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.

1668699069969.png


Any ideas?
 
 Short URL:
Top