jbc 1 Posted March 17, 2015 Share Posted March 17, 2015 Hi, Just migrated from ERA 5.x to 6.x and I'm trying to get a handle on things. Previously when you would push an AV package to a client computer and it would fail you could examine the task in detail and see the exact error codes and failure reason. How do I do this in ERA 6.0? As far as I can tell, on the 'Client Task Detail' windows all it says is 'Failed' under executions. How can I get more information without having to login to every single computer I'm trying to deploy to? Thanks! Link to comment Share on other sites More sharing options...
Administrators Marcos 5,235 Posted March 17, 2015 Administrators Share Posted March 17, 2015 Check ERA server trace.log for possible reasons why an agent push install failed. For some hints, please refer to hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3630. Link to comment Share on other sites More sharing options...
Alf 2 Posted March 18, 2015 Share Posted March 18, 2015 Hi, why cannot be details of the failed task shown directly in "Client Task Detail"? It would be more comfortable. Link to comment Share on other sites More sharing options...
bbraunstein 27 Posted March 18, 2015 Share Posted March 18, 2015 Check ERA server trace.log for possible reasons why an agent push install failed. For some hints, please refer to hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3630. It always kind of irked me how the Web Console is supposed to be the interface between the Administrator and the Server, but whenever there is an error, we need to log into the server and look at the logs. Why not just make the logs accessible through the Web Console? Link to comment Share on other sites More sharing options...
jbc 1 Posted March 18, 2015 Author Share Posted March 18, 2015 Check ERA server trace.log for possible reasons why an agent push install failed. For some hints, please refer to hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3630. It always kind of irked me how the Web Console is supposed to be the interface between the Administrator and the Server, but whenever there is an error, we need to log into the server and look at the logs. Why not just make the logs accessible through the Web Console? I agree. You used to be able to just check the failure reason right there in the console in 5.x. It was so easy. No hoops to jump through. Link to comment Share on other sites More sharing options...
ESET Moderators Solution Peter Randziak 1,160 Posted March 19, 2015 ESET Moderators Solution Share Posted March 19, 2015 Hello, the logs are not fetched by the server so that is the reason why they cannot be viewed. I will create an improvement request for it. Thank you. P.R. Link to comment Share on other sites More sharing options...
glsb 1 Posted June 15, 2015 Share Posted June 15, 2015 I agree; task failure details being reported are also a feature that we miss from v5. When you're deploying to tens or hundreds of computers, it's nice to know why installations are failing so that resolutions can be just as easily implemented. Thanks Link to comment Share on other sites More sharing options...
pgh 0 Posted August 11, 2015 Share Posted August 11, 2015 Hello, the logs are not fetched by the server so that is the reason why they cannot be viewed. I will create an improvement request for it. Thank you. P.R. This is extremely important for us as well. Is there an ETA for this, Peter? Link to comment Share on other sites More sharing options...
Recommended Posts