BDeep

Some screenshots.

No, that was a recommendation on another post I made about a month ago and that option was (and is) not enabled. Also, I've exported my policies (I guess you can get them?) under the GPC ticket (or PM me). It is definitely the firewall module killing the update.

In the update module, error 0x1606, 0x3FFF, Compile Error, "Undocumented Serious Error", "Error Allocating Memory". The Firewall is in automatic mode without any custom rules (I duplicated the built in policy for troubleshooting). I don't have screenshots (we've submitted everything under ticket #[BDeep removed] over the last few months but communications have been slow). Update: removed ticket number. Also, got off the phone with ESET. Was asked to let you know I'm working under a GPC ticket. PM me for more info if you need.

Running ESET Endpoint Security 6.5.2107.1 (and 2094.0) we've had multiple update errors. We've disabled the ESET Endpoint Security firewall and the updates download and apply without issue. Any ideas?

We have to enterprise support tickets open: 42735 & 42736.

"other - log all objects" is, and has not, been enabled for any scanning method. Other ideas?

We are seeing many computers (right now about 10% of our fleet) with various ESET update errors after upgrading to ESET 6.5. These are all Windows Endpoint Security products (Macintosh computers are not reporting errors, thank gawd). Most of the time it is "General Compile Error" followed by "Out of Memory" error on these machines. I'm on my administrator workbook (Elitebook 840 G3 16GB RAM (12 GB free) and 4 CPUs) and am getting General Compile Error. Clearing the update cache from ERA (and confirming the task was successfully run) does nothing at all. Occasionally a reboot fixes the issue but we are finding the need to temporarily disable the GUI protection settings profile, manually clear the cache, re-enable the profile, and run updates. This will work for a day before crapping out again. Today I moved the entire enterprise from using the local cache servers (HTTP proxy 3128 for updates) and set every computer globally in our enterprise to go out to the ESET servers for updates hoping this would resolve the issue (which it didn't). I'm sitting at my house having ESET update errors. We can provide logs (or open up a support ticket) if needed.Frankly I just want to get this resolved so us in Tier III will stop getting escalated tickets Update: Logs attached from client "Events" log. Logs 07June20172144.txt

We excluded the Skype for Business executable (which is lync.exe (before being rebranded)). There are four different directories that Skype for Business can be installed in: "C:\Program Files\Microsoft Office\root\Office16\lync.exe" "C:\Program Files\Microsoft Office\Office16\lync.exe" "C:\Program Files (x86)\Microsoft Office\root\Office16\lync.exe" "C:\Program Files (x86)\Microsoft Office\root\Office16\lync.exe"

Clam 0.99.2 of the engine on OwnCloud. Message is "Virus Eicar-Test-Signature is detected in the file. Upload cannot be completed.” SHA1: 3a48636ada6b92ae1b245af06c59ae9567bcc482 https://download.eset.com/com/eset/apps/business/era/agent/latest/agent-macosx-i386.dmg

We're trying to share the ESET Agent for Macintosh .dmg file and ClamAV (addon AV module in Linux and also for OwnCloud) is popping it as containing the "EICAR" test virus. Who do we raise the issue with?

Install log on a client that keeps uninstalling ESET after ESET is installed. ESET.install.log

On my Windows and Macintosh clients, I kept re-running and re-running the task until it finally took. Windows workstation clients down to 98 out of 181. Macintosh at 24. Windows server still at 347. Unfortunately I can't reboot the servers as they are all production. For the HTTP errors: every one was coming out of Africa or Asia (probably with terrible bandwidth and crappy connections).

Tried pushing the upgrade task to 200 Macintosh devices. 6 devices so far are showing this: 2016 Sep 29 17:02:32 ESET Remote Administrator Agent Failed Task failed GetFile: Error reading HTTP response data (0x4e2a) and 2016 Sep 29 20:49:24 ESET Remote Administrator Agent Failed Task failed ReadUpgradeStatus: Upgrade of Agent from version '6.3.110.0' to '6.4.232.0' failed. Current version is '6.3.110.0' and 2016 Sep 29 23:05:20 ESET Remote Administrator Agent Failed Task failed File already exists 'C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Data\upgrade.json'. Cannot continue with agent upgrade

Wow! That's a lot to take in. I'll break it down. What is version of those windows AGENTs? Of all the ones I checked: 6.3.136.0. What operating systems are they using - are they all the same?Almost all Windows 7 Professional, about a dozen Windows 10 Enterprise This has actually happened for all your windows machines?Of the 1,282 Windows computers, 183 have outdated Agent and are thrown into an "outdated agent dynamic group. The Agent policy is configured to auto-upgrade components (so is the ESET program policy too so that clients auto update their software). is there any special configuration of temporary directories in this machines?C:\Windows\Temp which is the system default Windows that could possibly have system paths containing non-latin characters?14 are in Asia (not sure the language they picked for the OS). The rest are Europe or America as English locale.

Could you please provide error message (or even better trace message) you see in task execution history -> in one of failing client's details view. There may be configuration problem on our servers and maybe it was only temporary outage. From ERA status of the client(s): Remote Administrator Components Upgrade Failed boost::filesystem::unique_path: (0x8009000f), Object already exists From client trace.log: 2016-09-29 18:41:03 Error: CSystemConnectorModule [Thread 9b0]: UpgradeInfrastructure: Task failed: boost::filesystem::unique_path: (0x8009000f), Object already exists 2016-09-29 18:41:03 Error: CReplicationModule [Thread e40]: CReplicationManager: Failed to start replication, replication link '00000000-0000-0000-7007-000000000001' (Automatic replication (OUT_OF_ORDER)) is already in use 2016-09-29 19:41:53 Error: CSystemConnectorModule [Thread 9b0]: UpgradeInfrastructure: Task failed: boost::filesystem::unique_path: (0x8009000f), Object already exists 2016-09-29 19:41:53 Error: CReplicationModule [Thread a4c]: CReplicationManager: Failed to start replication, replication link '00000000-0000-0000-7007-000000000001' (Automatic replication (OUT_OF_ORDER)) is already in use

Well . I gotta figure out how to get this working.

Just FYI: I dove into the ERA 6 task for "Remote Admin Components Upgrade" and it references Linux-only operating systems. I have 183 Windows clients that this task consistently fails on either automatically or if I launch it manually. If I run this task against Linux computers it works flawlessly. Am I interpreting this wrong? If so, why aren't hundreds of Windows computers updating their Agent and why is the task consistently failing?

1) Maybe last 10 used (that is Microsoft default list of last used)? Perhaps a spot for 10 tasks with the ability to "pin" the task (same as MS). I think the ability customize the feature to pin what the administrator wants would take precedence over ERA determining what the administrator should want. 2) Install OS Update with auto-reboot Install OS update with NO reboot Display Message to end user to contact security Deploy new software package install (ESET File Security) Deploy new software package install (Windows Desktop) Deploy new software package install (Macintosh) SysInspector log request. Kickstart Linux ESETS service (custom terminal command)

I use ERA 6 to accomplish MANY tasks on clients/servers that are out of the "normal' scope for ESET such as kicking off OS updates, displaying messages to end users, running custom scripts, etc. Can the DEV team consider adding a customizable "Quick Tasks" option in ERA? Instead of the need to click on the client, select "Run task", click "Add Tasks", click "okay", then click "Finish" for each task, an additional drop down/expandable window could be had under "Run Task" called "Quick Tasks" that would allow for n number of frequently used tasks to be selected. This would significantly cut down on task execution times. Thanks

Second set of images (uploads are capped).

ESET with AV remover, if installed manually, flags FireFox for removal. In ERA, running an OPSWAT "third party AV remover" removes FireFox automatically. OPSWAT task in ERA removes ESET if ESET is installed manually. See screenshots of what is flagged. Also see the before screenshots where we did not remove FireFox automatically and after the OPSWAT task is run on ERA where FireFox gets auto removed and ESET gets auto-removed (no screenshots of the ESET removal). In ERA the OPSWAT task shows "failure". I have logs and can upload securely on demand.

This is what our end users see for notifications. Instead of running in circles, what I think you are saying is that PUPs restored from ERA are going to get popped regardless of whether the "restore and exclude" option is selected in ERA.

Thanks Marcos. I also found this. Looks like something related (but not exactly as I posted) is in the works: https://forum.eset.com/topic/8813-threat-exclusion/

Our enterprise endpoints are locked down and they do not have that option. Restoring and excluding from ERA just causes the file to get popped again.

hxxp://support.eset.com/kb5949/ Using the ESET Remote Administrator Agent Component Upgrade task with ESET Shared Local Cache (ESLC) and ESET Virtualization Security (EVS) will upgrade the ERA Agent but the appliance will show a red Malfunction status (“Product is installed but it is not running”) in the ERA Web Console. The appliance will continue to function but will not be manageable using the ERA Web Console. Solution: Do not upgrade ERA Agent in ESLC and EVS until the upcoming service release of ELSC and EVS and then replace the entire appliance. If you have already upgraded, redeploy the appliance with the previous ERA Agent to restore functionality.