Sander de Cocq 0 Posted November 13, 2019 Share Posted November 13, 2019 Hello, We have an agent that has not been reporting for a long time. I've reinstalled the agent, and it installed without errors, but it's still not replicating with our SMC. In ela.eset,com, it is reporting. The server in question can connect to era.ourdomain.com:2222 Collected log files attached. efsw_logs.zip Link to comment Share on other sites More sharing options...
Administrators Marcos 4,705 Posted November 13, 2019 Administrators Share Posted November 13, 2019 Are there any errors in C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html and trace.log on the client? Link to comment Share on other sites More sharing options...
ESET Staff MartinK 375 Posted November 13, 2019 ESET Staff Share Posted November 13, 2019 For more precise answer we will need AGENT trace logs. Without those we can just guess: similar error might be caused by fact that Administrator intervention in console is required: could you verify whether there are no open "Questions" for devices in ESMC? It could happen in case duplicate HW or cloning is detected. Link to comment Share on other sites More sharing options...
Sander de Cocq 0 Posted November 14, 2019 Author Share Posted November 14, 2019 20 hours ago, MartinK said: For more precise answer we will need AGENT trace logs. Without those we can just guess: similar error might be caused by fact that Administrator intervention in console is required: could you verify whether there are no open "Questions" for devices in ESMC? It could happen in case duplicate HW or cloning is detected. Thanks for the great response. Yes, I found the computer under Questions and resolved the apparently changed hardware (it is a cloud VPS, so I guess the provider changed something in the VM configuration. We were not aware of any such change.) Link to comment Share on other sites More sharing options...
Recommended Posts