KAMIRAN Support 0 Posted May 21, 2017 Share Posted May 21, 2017 Hi dears, In these days we have problems with ERA 6.4 and we must upgrade all our customers to 6.5 and in most cases it will be fixed. In ERA console 6.4 last connected date in incorrect while every thing is OK , Agent is connecting , Policies will apply , Even last connected time is updated but with wrong date ( about 3 month difference ) For example right now it show that last connect time is in 2017 Aug !!! Server And Client time is right . is it a Bug in 6.4 ? Link to comment Share on other sites More sharing options...
KAMIRAN Support 0 Posted May 27, 2017 Author Share Posted May 27, 2017 No idea ? Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted May 28, 2017 ESET Staff Share Posted May 28, 2017 I would suggest upgrading to 6.5 (both server & agents). Also, please let us know on which OS (Windows / Linux / Appliance) you have deployed your ERA Server). Link to comment Share on other sites More sharing options...
KAMIRAN Support 0 Posted May 28, 2017 Author Share Posted May 28, 2017 Dear Michal, Yes after upgrade to 6.5 it will be solved but we have over 300-400 Customers because we are an ESET partner, So we want to know is it a bug or s.th els ? These cases are on Windows platform. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted May 28, 2017 ESET Staff Share Posted May 28, 2017 I don't think this has been reported as a bug. To localize cause of this issue, please: check UTC time/date of your server machine as time of connection is reported as UTC time. Please check also date/timestamps in ERA trace log on server machine, whether they are correct. check local time & date of you browser (= machine where you are running browser with ERA Webconsole). As all times are stored internaly in UTC format, they are automatically re-calculated to local time reported by browser (this behavioir may be slightly modified in User Settings). Link to comment Share on other sites More sharing options...
KAMIRAN Support 0 Posted May 28, 2017 Author Share Posted May 28, 2017 34 minutes ago, MartinK said: I don't think this has been reported as a bug. To localize cause of this issue, please: check UTC time/date of your server machine as time of connection is reported as UTC time. Please check also date/timestamps in ERA trace log on server machine, whether they are correct. check local time & date of you browser (= machine where you are running browser with ERA Webconsole). As all times are stored internaly in UTC format, they are automatically re-calculated to local time reported by browser (this behavioir may be slightly modified in User Settings). We check these all and all were correct but the problem is not 12H or 1 day , it is about 3 months difference !!! And not 3 month ago ! 3 month later , Also ERA did not show any error that it seems it did not feel any problems, just last connected date is 3 month later. in one case it was AUG 2017. Right now upgrading to v6.5 solved the problem. Link to comment Share on other sites More sharing options...
Recommended Posts