TN LMG

I tested today from a fresh copy of the old CentOS VA and can run an Agent Deployment Server Task to run successfully. Using identical settings on the Rocky VA the task fails. Will raise a support request to have the bug investigated.

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.

+ net -i -k rpc service delete eset-remote-installer -W ******** -U *********** -S ************** WARNING: The option -k|--kerberos is deprecated! Could not connect to server *************** Connection failed: NT_STATUS_INVALID_PARAMETER * [Exit code = 255] This is what I have in /var/log/eset/RemoteAdministrator/Server/trace.log if anyone has insight (domain -W, username -U and target machine FQDN -S have been replaced with stars for security)

Since migrating to the new Rocky VA, I've been unable to get an Agent Deployment Server Task to run successfully. I realise there are many factors involved here and it may not be related to the new device or migration at all, but wondered if anyone else has had issues or is able to verify whether this still works. I used to run them routinely from the old CentOS server, so I'm confident I have the right settings/permissions. There have been several bugs already with the new VA, so I'm wondering if this is another kink still to be worked out.

https://support.eset.com/en/kb7859-cannot-connect-to-the-eset-protect-web-console-after-linux-mysql-update I rolled back yesterday and have applied the version lock as instructed in the above article. This has resolved this issue for me.

https://support.eset.com/en/kb7859-cannot-connect-to-the-eset-protect-web-console-after-linux-mysql-update

Just tested and the MySQL issue Pan reported is different to mine, but I just tried the update for MySQL and this also borked my production server. Rolling back again. This has been a very Rocky road so far!

This sounds very similar to the issues I've been asking about here https://forum.eset.com/topic/40471-migrated-va-to-rocky-linux-but-cannot-create-new-client-task/ and have reported in a Support Case (#00750793) last week (24th April). I'm 5 messages in so far and they seem unwilling or unable to test for the bug. In my case at least, 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. Rolling back to a backup was my only way to get things running again.

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.

I had a little time today and have been experimenting more with the issue of Login failed: Connection has failed with state "loginConnectionStateNotConnected" after an ESET PROTECT Components Upgrade task is run on the server. I have created a test copy of the virtual appliance, reset it to factory (to eliminate the issue being my database or settings), then ran the ESET PROTECT Components Upgrade task on the server. I get the same error Login failed: Connection has failed with state "loginConnectionStateNotConnected" I therefore believe this is a bug with the new appliance and have started a support case.

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"

Same problem here. Looking forward to the patch.

I fought the same communication error for the last two days. Thank you for the solution. Now on to the next issue ...

The issue appears to have been resolved for us in ESET Endpoint Security 9.1.2060.0

The issue appears to have been resolved for us in ESET Endpoint Security 9.1.2060.0

We don't have KuTools. We tested with all add-ins disabled except for ESET and the crashes still occured. Disabling ESET Outlook integration stopped the crashes, as does rolling back to Endpoint Security 9.0.2046.0

Our users are still reporting crashes with the latest version (ESET Endpoint Security 9.1.2057.0) I have submitted a support ticket and sent the requested log files. Further logs were then requested.

I also have some users reporting intermittent Outlook crashes. Disabling Outlook Integration or rolling back to Endpoint Security 9.0.2046.0 have both worked as temporary mitigations for me while I was trying to trace/prove the bug.

I also have some users reporting intermittent Outlook crashes and we are not alone Disabling Outlook Integration or rolling back to Endpoint Security 9.0.2046.0 have both worked as temporary mitigations for me while I was trying to trace/prove the bug.