Ondrej 4 Posted December 22, 2021 Share Posted December 22, 2021 (edited) Hi, I face issue with PROTECT Server 9.0.1144.0 in combination with MS SQL Express 2019 under Windows Server 2019 (build 1809). Webconsole throws error Login failed: Connection has failed with state "Not connected". Found out that ESET PROTECT Server service keeps crashing after few seconds. Tried everything what Google proposed, but without success. Symptoms are identical as described in these threads (attached patch no longer downloadable): Where can I privately send C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Logs\trace.log and latest C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Dumps\Local\*.dmp files, please? Edited December 22, 2021 by Ondrej Link to comment Share on other sites More sharing options...
ESET Staff Gonzalo Alvarez 66 Posted December 22, 2021 ESET Staff Share Posted December 22, 2021 Hi, This error usually is show while the services are still starting up (Virtual Appliance), but I guess you are on the installed version. Please confirm if you try KB7800... https://support.eset.com/en/kb7800-error-login-failed-connection-has-failed-with-state-not-connected-in-eset-protect-web-console Link to comment Share on other sites More sharing options...
ESET Staff MartinK 375 Posted December 23, 2021 ESET Staff Share Posted December 23, 2021 11 hours ago, Ondrej said: Where can I privately send C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Logs\trace.log and latest C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Dumps\Local\*.dmp files, please? Feel free to send me those via private message. I would also recommend to open support ticket in the meantime, in case it will require more details to be provided. Peter Randziak and Gonzalo Alvarez 2 Link to comment Share on other sites More sharing options...
Ondrej 4 Posted December 23, 2021 Author Share Posted December 23, 2021 Hi Gonzalo, thanks for your tip, I followed KB7800 yesterday, but without success. It covers connection between DB and PROTECT and functionality of Tomcat webserver. I face issue with PROCECT service itself. Hi Martin, unfortunately I am receiving error message "MartinK cannot receive messages." - can you please advice different method? Link to comment Share on other sites More sharing options...
Ondrej 4 Posted December 23, 2021 Author Share Posted December 23, 2021 Update: Support ticket including both logs raised with ID: NTO-794-10454 Gonzalo Alvarez 1 Link to comment Share on other sites More sharing options...
Ondrej 4 Posted December 23, 2021 Author Share Posted December 23, 2021 (edited) One more update: I just check another or our customers and I can see same issue is also there. Environment: Windows Server 2016 (build 1607) + MS SQL 2014 + PROTECT 8.1.1223.0 Both customers are isolated and all components are on different versions - Windows Update might be the clue? Edited December 23, 2021 by Ondrej Link to comment Share on other sites More sharing options...
ESET Support Solution tomasS 5 Posted December 23, 2021 ESET Support Solution Share Posted December 23, 2021 Dear Ondrej, you are most probably affected by the issue related to the "Translator" module. The solution might be repair of the PROTECT server. you can fix it by reverting to the previous build of the Translator module - this can be done by stopping the PROTECT/ESMC Server(I believe this is already done), create a backup of the following files/folder: Windows: C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Modules\em017_64\ Remove all folders/files which are in the following path(in case of Windows): "C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Modules\em017_64\" Execute the repair of the PROTECT server - it should re-create the "Translator" module file from the installation archive(it will be an older version of the Translator module which comes with the installers/is built in the installer) For MS Windows just execute the MSI installer which can be found at "C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Installer" and pick repair installation(you will be asked for DB credentials...) but please do not generate a new certificate, let them use the old ones(keep currently used certificates) When the installation will be done, the server should be able again to start... Peter Randziak 1 Link to comment Share on other sites More sharing options...
Ondrej 4 Posted December 23, 2021 Author Share Posted December 23, 2021 (edited) Dear Tomáš, thank you so much for your tip - it really was caused by Module em017_64 as it works now. Issue resolved in both mentioned environments. Happy Holidays, Ondřej Edited December 23, 2021 by Ondrej Peter Randziak and Gonzalo Alvarez 2 Link to comment Share on other sites More sharing options...
Recommended Posts