tomasS

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...

Dear Mrac, in case your server is still not operable, 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\ Linux /var/opt/eset/RemoteAdministrator/Server/Modules/em017_64.dat Remove all folders which are in the following path(in case of Windows): "C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Modules\em017_64\" In case of Linux remove the "em017_64.dat" file Execute the repair of the PROTECT server - it should re-create the "Translator" module file from the installation archive(it will be older version of the Translator module which comes with the installers/is build in the installer) 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...) Linux: execute the installation script: opt/eset/RemoteAdministrator/Server/setup/installer_backup.sh It will automatically execute the "repair" and create deleted files...

We would like to kindly ask you which options/details you want to see in the "Computer Preview" tab. Now, there is an option to pick "3" statuses: Overview/Status/Users - and we are curious which statuses are preferred by you/which should be available to show.

thanks for the provided log files, we are going to investigate what is happening there. We will keep you posted...

is there any chance to provide "ra-upgrade-agent.log"(It should be located at "C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs") or even better if someone can provide the ESET Log Collector log from the affected machine.

Hello, Hmm, thank you very much for sharing this info and test. If you are still willing to continue I would like to kindly ask you for the following procedure(as I assume some of the previous outputs have been cropped and the important information might be there). So if possible: 1. please execute the "kdestroy" 2. execute the kinit "KRB5_TRACE=/dev/stdout kinit eset.esmc" 3. please execute the "klist -f" there should be visible only one TGT with flags 4. please execute ldapsearch "KRB5_TRACE=/dev/stdout ldapsearch -LLL -Y GSSAPI -h dc.test.local -b 'DC=test,DC=local' '(&(objectCategory=computer))' 'distinguishedName' 'dNSHostName'" 5. please execute again "klist -f" If possible please provide us with full ouput all of these commands

Hello, could you please try to clear the Kerberos cache by "kdestroy". Afterwards, please try to obtain the TGT(by "kinit") and use the same command just replace the "ldaphost" with the IP: KRB5_TRACE=/dev/stderr ldapsearch -LLL -Y GSSAPI -h 10.123.123.1 -b 'DC=test,DC=local' '(&(objectCategory=computer))' 'distinguishedName' 'dNSHostName' Is there any chance to provide us with the "krb5.conf" and settings of user "eset.esmc" from the AD >> I mean "Account options" from "AD Users and Computers" >> particular user >> "Properties" >> "Account"

The PROXY setting you have mentioned is used for replication, not for downloading the installer(msi) package. The batch file has to be modified, please add the following lines into it: set http_proxy_hostname= set http_proxy_port=

Dear Camilo, is there any chance to provide log files from the ESMC Server? If possible please try to replicate the situation with enabled "trace" verbosity (https://help.eset.com/esmc_admin/70/en-US/admin_server_settings.html?admin_server_settings.html) and please provide us with logs - we are curious about the "trace.log" from the ESMC Server. Logs can be collected by ESET Log Collector (https://support.eset.com/kb3466/?locale=en_US&viewlocale=en_US)