oshitha 0 Posted September 10, 2015 Share Posted September 10, 2015 (edited) Dear all, Please heip to me, what is this error? Edited September 10, 2015 by oshitha Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted September 10, 2015 Administrators Share Posted September 10, 2015 Do you update from a mirror created by ERA v5? I see that you have pre-release updates installed even though EFSW 4.5 doesn't allow for switching between regular and pre-release updates. If possible, could you try uninstalling and installing EFSW from scratch to see if update from ESET's servers works? Link to comment Share on other sites More sharing options...
PiT 0 Posted September 22, 2015 Share Posted September 22, 2015 Now, since last windows update, I've the same problem with EFS connected to local ERA 5. ERA 5 // 20 EEA 5 clients - all connected and communicating = OK // 1 EMS client - connected and communicating = OK // 9 EFS clients - one on 32bit W2008R2 - connected and communicating = OK // 8 on 64bit W2012R2 - all 8 throw this same error. I've tried to reinstall them (and also tried luck with uninstalling all applied windows updates on one windows server). After reinstall they work to the next reboot. After reboot they stop to communicate and throw "error opening socket" again. Link to comment Share on other sites More sharing options...
erlend_oyen 2 Posted September 22, 2015 Share Posted September 22, 2015 This is not a solution for many clients, but running sysinspector once, resolved the problem for me on 10+ clients Link to comment Share on other sites More sharing options...
PatrickHoban 1 Posted September 23, 2015 Share Posted September 23, 2015 Looks like A LOT of people are having this issue (myself included). Keep an eye on https://forum.eset.com/topic/6052-eset-file-security-not-reporting-in-to-era-server/. Link to comment Share on other sites More sharing options...
chadleeper1 0 Posted September 24, 2015 Share Posted September 24, 2015 Has anyone found a solution to the "error opening socket" error? I have three servers with the same issue. One of the server is an RDS server as well. Thanks Link to comment Share on other sites More sharing options...
jerry808 0 Posted September 25, 2015 Share Posted September 25, 2015 I just had this same exact error today 9-24-15 on the eset server itself but everything else including workstations and other servers working just fine..Eset server console is connecting and seems to be getting the updates just fine, message stating last update was 17hrs ago..?? Link to comment Share on other sites More sharing options...
leonhedding 0 Posted September 25, 2015 Share Posted September 25, 2015 We are also seeing this on our EFSW 4.5 servers getting mirror updates from an ERA 5. Uninstalling and reinstall AV on dozens of servers is hardly a workable solution. What is with this? Link to comment Share on other sites More sharing options...
ARQEROS 2 Posted September 25, 2015 Share Posted September 25, 2015 Check here: https://forum.eset.com/topic/6063-eset-file-security-not-reporting-in-to-era-server/ Link to comment Share on other sites More sharing options...
Recommended Posts