pps 4 Posted October 5, 2017 Posted October 5, 2017 (edited) Hello, I am experiencing the below problem: I used a Server Task to deploy the agent to about 20 Computers. This was successful for the first 7 PC's but now the status is Running for 2 hours and I see no progress in the Execution details. This is the second time in two days the same Task freeze occurs and it seems there is no way to stop the specific Server Task even If I reboot the server or stop the ESET Remote Administrator Server service. Even If the I delete the Task and make a new one the new one is in "stucked" mode. Is any workaround for this error/bug? Windows Server 2016 ESET Remote Administrator Server ESET, spol. s r.o. 6.5.522.0 Update: Task seems running until now (16 hours). Thanks, Peter Edited October 6, 2017 by pps update
pps 4 Posted October 11, 2017 Author Posted October 11, 2017 Hello, Same issue today out of 21 computers only 4 were successful. xxxxxxxxxx 2017 Oct 11 17:04:10 Windows network Task finished successfully xxxxxxx 2017 Oct 11 17:03:52 Windows network Task finished successfully xxxx 2017 Oct 11 17:03:42 Windows network Task finished successfully xx 2017 Oct 11 17:03:09 Windows network Task finished successfully anyone has any clue why this is happening? Thanks, Peter
Administrators Marcos 5,452 Posted October 11, 2017 Administrators Posted October 11, 2017 If you check client details, is the time of the last agent connection updating? If not,check status.html and trace.log on the client for details about possible issues.
pps 4 Posted October 12, 2017 Author Posted October 12, 2017 Hello Marcos, Thanks for the response, The only workaround that found to stop the never ending job is to delete the job row from tblf_task_server_status, but this is not solution. After that running again another duplicated job from the never ending job the agent installation went smoothly in all clents. So there is no way that a client is responsible for this behavior and if it was then the job should skip the client and move to the next one. Any ideas what to check next? Is there a way to check the database for errors and consistency? Thanks, Peter
Recommended Posts