Search the Community

Hi, when I try to manually run a scheduled report, I get an error "ReportPrinter: ReportPrinterTool exited with: Unexpected fatal failure [code:31]" Other consoles that we support have the same reports and they work. I cant find a solution on the internet, please help

Hi Dears. We have Client with agent 7.2.1266.0 could not connect to ESMC. The Logs is attached . The error is : AUTHENTICATION_FAILED (Error description: unable to authenticate entity) Best Regards. Logs.zip

Just like I did 4 years ago I'm having trouble removing the Agent (~6.5) using SCCM and I can't just wipe all the computers like I did 4 years ago either, I need an actual solution to this frustrating problem that continues to suck the life from me. Please don't recommend the AV Uninstaller tool that requires safe mode, I need to automate this at scale using SCCM. ESET Endpoint Security 6.6 - 6.7 can be removed using an Uninstall Task from ERA6. The applied Agent Policy has "Password protected setup" not set" The applied Endpoint Security Policy has "Password protected settings" disabled and "Set Password" not set, for both <6.x and >7.0. The following don't work: SCCM Uninstall Step for Deployment Type As SYSTEM: msiexec /x {41F12F70-5FA9-43F5-94F4-53B54EB4EEC4} /q As Local Administrator: msiexec /x {41F12F70-5FA9-43F5-94F4-53B54EB4EEC4} No error code As Local Administrator: msiexec /x {41F12F70-5FA9-43F5-94F4-53B54EB4EEC4} /q /lvx* "C:\ProgramData\ESET\Uninstall.log" No error code Application remains listed as installed even after reboot. "Stop Managing (Uninstall ERA Agent)" Task from ERA6 Failure listed in ERA6, not further information The following does work: Manually uninstalling it from Add/Remove Programs (No Password) I've tested these scenarios, and combinations there of, on a number of systems now. Based on the Uninstall.log produced from above, it deletes the C:\ProgramData\ESET\RemoteAdministrator\ directory tree after an initial complaint that a number of binary files in C:\Program Files\ESET\RemoteAdministrator\Agent\ are being held in use by ERAAgent process, I'm assuming the service was still running at that point before it was stopped by the StopServices action. The C:\Program Files\ESET\ directory tree is removed by the end of the entire process and the log states "Product: ESET Remote Administrator Agent -- Removal completed successfully.",, "Windows Installer removed the product. Product Name: ESET Remote Administrator Agent." with an error code of 0 but the product isn't removed from the system program list, it still appears installed. Attempts to uninstall it again fail because the Configuration database is missing from C:\ProgramData\ESET\RemoteAdministrator\ What do I do here?

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

It seems that our new ESET Remote Administrator Linux appliance cannot deploy the agent on windows 7 machines which have the SMB1 protocol disabled for security reasons. The error I see in system logs is 'CIFS VFS: cifs_mount failed w/return code = -112' I suppose that this has to do with the fact that windows 7 machines cannot talk SMB1 any more. When i try to manually mount a remote windows 7 share using the parameter mount -t cifs -o vers=2.0 then the mount succeeds, but how to append this parameter to ESET remote administrator? Is there any solution to this problem?

Hi, Any ideas for remote deployment with elevate privileges for EraAgentInstaller.bat best

I have ERA 6.5 I had a number of windows servers with EFS 6.5 and an older agent. My understanding was that I can upgrade the agent via a client task: "Remote Administrator Components Upgrade" I set such a task and ERA console showed that the task was complete, however the version on the clients remained at 6.3 In the end at this site I ended up creating an update batch file, which I then ran by other means, this worked and the and ERA Agent is now at 6.5 I have 2 other customers with a similar scenario so before I start on them can you please advise: Am I correct that "Remote Administrator Components Upgrade" is meant to upgrade agent on clients, and if so why do you think it didn't work in this case? regards Roga