baran 0 Posted May 2 Share Posted May 2 hi guys what's this problem? Why is this problem not solved even though it has received the full update? Link to comment Share on other sites More sharing options...
Administrators Marcos 4,919 Posted May 2 Administrators Share Posted May 2 Do you mean that whenever you click "Check for update" it will end with the "Failed to copy file" error? Link to comment Share on other sites More sharing options...
baran 0 Posted May 2 Author Share Posted May 2 (edited) hi marcos Yes, exactly How can I solve this message? Edited May 2 by baran Link to comment Share on other sites More sharing options...
Administrators Marcos 4,919 Posted May 2 Administrators Share Posted May 2 Strange that the event log doesn't contain any record related to the error. Please carry on as follows: Enable advanced logging under Help and support -> Technical support Run update and reproduce the issue Stop logging Collect logs with ESET Log Collector and upload the generated archive here. Link to comment Share on other sites More sharing options...
baran 0 Posted May 3 Author Share Posted May 3 hi marcos This log is from the desired server. efsw_logs.zip Link to comment Share on other sites More sharing options...
Administrators Marcos 4,919 Posted May 3 Administrators Share Posted May 3 The update server is set to a custom server http://172.16.X.X:2221. Socket connect to address 172.16.X.X port 2221 failed 3. 5. 2023 9:25:46 Update Could not connect to server. SYSTEM 3. 5. 2023 9:23:34 Update Could not connect to server. SYSTEM 3. 5. 2023 9:22:03 Update Could not connect to server. SYSTEM 3. 5. 2023 9:12:48 Update Could not connect to server. SYSTEM Connection via a proxy server is enabled, the proxy is set to the same server 172.16.X.X. Link to comment Share on other sites More sharing options...
baran 0 Posted May 8 Author Share Posted May 8 This log is from the desired server. This problem is spreading to other clients and servers like an epidemic. I checked all the policies from the beginning, but there is still a problem. please check it efsw_logs.zip Link to comment Share on other sites More sharing options...
Administrators Marcos 4,919 Posted May 8 Administrators Share Posted May 8 I don't see any update errors in the last logs: 8. 5. 2023 5:26:36 ESET Kernel Anonymous statistical information was sent to ESET. SYSTEM 8. 5. 2023 5:14:28 ESET Kernel Anonymous statistical information was sent to ESET. SYSTEM 8. 5. 2023 5:14:24 ESET Kernel Detection Engine was successfully updated to version 27197 (20230508). SYSTEM 7. 5. 2023 23:14:28 ESET Kernel Anonymous statistical information was sent to ESET. SYSTEM 7. 5. 2023 23:14:25 ESET Kernel Detection Engine was successfully updated to version 27196 (20230507). SYSTEM Link to comment Share on other sites More sharing options...
baran 0 Posted May 8 Author Share Posted May 8 Dear marcos The update is done, but this message is not resolved. Today's update number is 27197. This message can be displayed for clients Link to comment Share on other sites More sharing options...
Administrators Marcos 4,919 Posted May 8 Administrators Share Posted May 8 24 minutes ago, baran said: This message can be displayed for clients The logs were taken from the server, not from clients. If the error appears on clients, we'll need advanced logs collected by ELC from such client. Link to comment Share on other sites More sharing options...
baran 0 Posted May 8 Author Share Posted May 8 how can i do this ?(we'll need advanced logs collected by ESET Log Collector from such client.) Link to comment Share on other sites More sharing options...
Recommended Posts