Vaneet Singla

Exactly! First, we couldn't select the server for components upgrade. Once they fixed it, now the eraservice is gone. I agree with ODBC and SHA1 as i tried both and still not able to login to web console. Please let me know if you get a meaningful response from support. I might end up opening up a support ticket too. 

Exactly! First, we couldn't select the server for components upgrade. Once they fixed it, now the eraservice is gone. I agree with ODBC and SHA1 as i tried both and still not able to login to web console. Please let me know if you get a meaningful response from support. I might end up opening up a support ticket too. 

Hi @Vaneet Singla
It's eraserver.service
Did this happen after you ran a ESET PROTECT Components Upgrade task? This seems to remove the service if run on the server.
I've had a support ticket open reporting this bug to ESET support for 2 weeks now but so far, they have just repeatedly responded giving links to solutions for the ODBC & SHA1 bugs. It's not the same issue.

The only solution for me was to roll back to a backup.

I'm curious, has anyone else tested this? @JimChev3 You said you didn't have the issue, but that your agents were up to date, so did you actually run the task and was the server itself targeted?
For anyone testing on your production environment, please take a snapshot or backup first, rolling back was my only way to get things running again.
I can consistently reproduce the issue on a fresh install of the new VA as detailed below.
Steps to reproduce the issue:
Deploy as per https://help.eset.com/protect_deploy_va/11.0/en-US/deployment_on_vsphere_esxi.html Config with name, password, domain & DC as per https://help.eset.com/protect_deploy_va/11.0/en-US/config_va.html Log-in to the web console. Run ESET PROTECT Components Upgrade task targeting the All group. Then try to log-in to the web console. The problem appears to be that the ESET PROTECT Server service is not running. In Webmin, it is no longer available in the System > Bootup and Shutdown list after the ESET PROTECT Components Upgrade task is run.

Can confirm that running the task is now possible.
However, after running the ESET PROTECT Components Upgrade task I'm now unable to log in to ESET PROTECT again.
Login failed: Connection has failed with state "loginConnectionStateNotConnected"

Any update on when this fix will be available for the on-prem VMWare appliance?
 

We expect the problem to be fixed tomorrow. In particular, you should be able to finish creation of the task without the need to select a referenced server.