Jump to content

BDeep

ESET Insiders
  • Posts

    111
  • Joined

  • Last visited

  • Days Won

    1

BDeep last won the day on January 29 2016

BDeep had the most liked content!

About BDeep

  • Rank
    Newbie
    Newbie

Profile Information

  • Gender
    Male
  • Location
    USA
  • Interests
    Interesting things.

Recent Profile Visitors

1,329 profile views
  1. 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.
  2. 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.
  3. 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?
  4. We have to enterprise support tickets open: 42735 & 42736.
  5. "other - log all objects" is, and has not, been enabled for any scanning method. Other ideas?
  6. 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
  7. 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"
  8. 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
  9. 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?
  10. Install log on a client that keeps uninstalling ESET after ESET is installed. ESET.install.log
  11. 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).
  12. 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
  13. 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.
  14. 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
×
×
  • Create New...