jimmy09

Our issue now is that it works in Google Chrome and not in IE. Support seems to not be able to replicate the issue.

Has any one heard any updates from support? We can't get any response from USA support. They keep telling us that they are waiting on a response from their dev team.

Good luck with support on Monday. Update us as well. I'll be trying to contact them as well. We have trace logging turned on a couple of computers and the ESMC server. So hopefully they can find something.

@Marcos ESET Blocked both links. And I have contacted my local customer care. There is a case open on this already. But the only update I've gotten in the last 2 weeks is that the devs are looking at it. I just called in 2 days ago for an update and there wasn't one. Clearly I'm not the only one with this issue. ESET support is starting to become a joke. So slow are responding. Have to setup a time slot for a call back the next day. It just keeps getting worse and worse as far as ESET support goes in the US.

Anyone else notice this?

Still no response from ESET.

They had me change it to 20 min as well. That didn't help. Support is becoming a joke. Have to wait over 24 hours for a call back and such. I have multiple issues and have to wait 24 hours to talk to someone.

@Marcos Were you able to find anything out with the log that was sent?

If you turn off SSL/TLS filtering, then it won't filter HTTPS sites. Correct? We have to have it filtering HTTPS as well as HTTP.

@MartinK Dumps have been made. Contacted support. (Case #179128) Uploaded dumps to https://eset.sharefile.com/share/upload/rb04f28f47c84d658 Thanks

We have the same issue as well on a lot of our windows 10 clients.

A reboot fixes it for about 24/48 hours. I’ve had to reboot mine 3 times now.

@MarcosPM Sent

Web filtering was working fine back in V6. Once we upgraded to V7 we are noticing that web filtering is working in IE but not in Chrome. Then on other computers it seems to be working in Chrome but not in IE. But yet the computers are running the same policies in ERA. Has anyone else noticed this issue?

When looking at the status.html file, I noticed this error on the Last replication section. ERROR: InitializeConnection: Initiating replication connection to 'host: "**ServerName Removed**" port: 2222' failed with: Request: Era.Common.Services.Replication.CheckReplicationConsistencyRequest on connection: host: "**ServerName Removed**" port: 2222 with proxy set as: Proxy: Connection: :3128, Credentials: Name: , Password: ******, Enabled:0, EnabledFallback:1, failed with error code: 4, error message: Deadline Exceeded, and error details: Replication details: [Task: CReplicationConsistencyTask, Scenario: Automatic replication (REGULAR), Connection: **ServerName Removed**:2222, Connection established: false, Replication inconsistency detected: false, Server busy state detected: false, Realm change detected: false, Realm uuid: c4eccab2-b7d6-4dee-a92b-ac6fd4c8e1f4, Sent logs: 0, Cached static objects: 59, Cached static object groups: 9, Static objects to save: 0, Static objects to delete: 0, Modified static objects: 0] All replication attempts: 22

I have a decent amount of clients that agents are checking in. When I go to re-install or uninstall the agent, it gets stuck at "Stopping Service". Attached are the trace logs from a Windows 10 client. This is happening to both Windows 10 agents and Windows Server agents. Anyone else having these issues? trace.log

So there's no way to make it work?

We noticed this afternoon that if a standard user logs into safe mode, web control doesn't work. Is there any fix for this? We are running current ERA and Endpoint Security versions of 6.5 Is this a known issue? I have students that are rebooting the computers into safe mode to get around filtering. Hopefully there is a quick fix for this.

Where's the documentation showing that "ESET Shared Local Cache has no noticeable benefits and it's no longer needed unless you use many unpopular PE files (exe, dlls) on your VMs." I must have missed that while reading through the documentation.

What's the best way to update the Shared Local Cache Agent? Mine shows that the installed version is 6.4.293.0, but the current version is 6.5.417.0. I can't seem to find any documentation that shows how to upgrade it without having to download the new vhd from ESET.com. Which I did download, and received the same result. Thanks 6.5.417.07.0