Mra

I have no idea but it eventually fixed itself (overnight). It had like 330+ attempts accumulated over the course of a week. Nothing I could do could fix this problematic computer. But somehow, overnight it fixed itself. Who knows. If you're still interested, happy to send through logs if it is private here.

rebooted into safe mode, uninstalled using the esetuninstall tool. When reinstalling the agent, it worked for about a minute, registered on Eset Cloud Protect. However back to this same error message; ERROR: InitializeConnection: Initiating replication connection to 'host: "***randomstringofnumbers***.a.ecaserver.eset.com" port: 443' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "***randomstringofnumbers***.a.ecaserver.eset.com" port: 443 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 14, error message: upstream connect error or disconnect/reset before headers. reset reason: remote reset, and error details: . Request Id: 4ffb8ae8-874f-4742-8f41-7a84b24a346a Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: ***randomstringofnumbers***.a.ecaserver.eset.com:443, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: 00000000-0000-0000-0000-000000000000, Sent logs: 0, Cached static objects: 0, Cached static object groups: 0, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0] All replication attempts: 12 20 other machines on the same network work, so I can't see it being a firewall issue or DNS issue?

We had a machine lose it's policies during an upgrade Policies 2021-Dec-20 00:47:39 Device has no policies assigned It is no longer connecting. How do we get policies back onto it? Exporting from ESET PRotect cloud results in a useless DAT file, endpoint security takes an XML file. Any help would be appreciated. Thanks Oh and tried creating a live installer, but this didn't work

I've applied the "Enable product auto-update" policy to my workstations. In the actual eset software policy, I've also enabled automatic updates. However weeks later, my machines are still on 8x Endpoint Security. I read somewhere it might be activated in 2022? I'm so confused.

Hi, How does one set ESET Endpoint Security from scanning a USB or external drive everytime it's plugged in? I can't find any reference to this in the current policy templates. All the old help files and tutorials show a setting that no longer exists. ESET slaughters the transfer rates and speed of our drives and USB sticks. Using ESET Cloud Protect to manage the policies.

Hi, followed this guide https://help.eset.com/protect_cloud/en-US/cloud_migration.html#migrate_agents We have the migration policy applied to the group....but nothing happens. Nothing appears in the cloud and everything is running locally as per normal. Is there somehow a way I can easily figure out why? Is there a log or something? Thanks

Hi, How do I change policy order from Eset Security Management Centre? We have one policy that wants to be #1 always and want to make a single policy #1 for one particular computer.

So after bruteforcing the activation, it looks like it has gone through finally. This is weeks after battling upgrade issues because of the ESET servers which took months to fix - it seems there are still issues with the servers.

GREAT! Monday morning, I login and now I find several weeks after upgrading to version 7, our entire organization is reporting that our products are not activated?? ie they've deactivated themselves. What is going on with ESET version 7?

Hi Marcos, Yes, there is no proxy being used. It's only the one computer out of 20 that is not activating. It has internet access and can connect to the test xml file. (We also have license to spare, so we're not reaching a limit either) - the error occured after upgrading to version 7.1

Thanks, yes that's the same. The client can also reach the eset test website that has the xml file. I do wonder, we had massive issues with ESET the last couple of months because their servers had connection problems in Australia and if it's related?

Manually, this error appears ecp.200009 No proxy is being used and obviously all our other machines activate ok.

Of course there are no more details than this.

Thats the only error it gives?

also tried activating manually but ESET licenses keys do not exist? Step 2? https://support.eset.com/kb3615/?locale=en_US&viewlocale=en_US All we got was a ERA-Endpoint.zip which containts a Era-Endpoint.lic file....not a license key?

Oh sorry, I forgot to mention - it's activated from remote administrator. This link works on problematic client and we do not use any proxys https://edf.eset.com/edf

Hi, We have one workstation that refuses to do a product activation. I normally find solutions in the knoweldgebase but this particular workstaion is just not cooperating. Even reinstalling does not fix the issue. All other workstations in our office are fine. Is there anything I can do ? ESET is then causing a few issues with this machine.

Thanks, appreciate it. First option didn't work but re-deploying resolved the issue.

Hi, How does one change all workstations so that they use the new peer certificate? There are a multitude of help files explaining how to create new certs but not how to change exisiting clients so that they use these new certs.

*version : 7.0.413.0* *locale : en_US* *user.agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 (gecko1_8)* *document : https://servername.local/era/webconsole/72DE1EC48605863BC38EB354AD8C6F15.cache.html* *url : https://servername.local/era/webconsole/#id=NOTIFICATIONS:id=NOTIFICATION_WIZARD;nu=00000000-0000-0000-7016-00000000000f;p=3* An uncaught exception has ocurred! (com.google.gwt.core.client.JavaScriptException: (TypeError) : a.c is null) @Unknown.Wao(Unknown Source:177)@ @Unknown.Xao(Unknown Source:403)@ @Unknown.ico(Unknown Source:251)@ @Unknown.Dco(Unknown Source:90)@ @Unknown.Cdo(Unknown Source:231)@ @Unknown.Fdo(Unknown Source:220)@ @Unknown.jOd(Unknown Source:232)@ @Unknown.tE(Unknown Source:250)@ @Unknown.QE(Unknown Source:412)@ @Unknown.anonymous(Unknown Source:329)@ @Unknown.Nn(Unknown Source:239)@ @Unknown.Qn(Unknown Source:291)@ @Unknown.anonymous(Unknown Source:77)@ Javascript cause: @TypeError: a.c is null@ This happens when viewing email notifications

Thanks, I requested this thread be deleted. When reinstalling apache tomcat, the original files were overwritten. I merely didn't place the original configuration files back in the location as per the tutorial. After doing this, it all worked as per normal. Thanks. Edit: (and yes, I did mean // - good catch).

It still seems there is an issue, over two weeks later trying to upgrade agents this appears: UpgradeInfrastructure: Task failed: GetFile: Error reading HTTP response data (0x4e33) As honest feedback after using ESET for the last 12 years this has been by far the most painful upgrade process unfortunately.

No proxy is in use.

Hi, I upgraded 6.5 to Security Management Center Server 7, it seems to work because the AV's are updating and we're getting emails from Server 7. However we cannot connect at all to the https:\\x\era\webconsole. Are there any tutorials for this? I tried a few but haven't been able to resolve why it's not possible to connect to the interface even though the server is running.

Thanks @MartinK