ORC2019 0 Posted April 25, 2019 Share Posted April 25, 2019 Hello, I face the problem mentioned on the Title with Agent installation from Windows Server 2012r2. My ERA Server it's also Windows Server 2012r2. You can also see the attach files (log_agent_installation and Agent_error) Pleas help me to solved this issue. Thanks in advance for assistance. Log_agent_installation.log Link to comment Share on other sites More sharing options...
Administrators Marcos 5,278 Posted April 25, 2019 Administrators Share Posted April 25, 2019 Couldn't it be that a firewall running on the host 10.0.0.233 is blocking the connection attempt? Link to comment Share on other sites More sharing options...
ORC2019 0 Posted April 25, 2019 Author Share Posted April 25, 2019 (edited) Thanks for prompt react. I already turn off the firewall on the both host (same issue). Please could you also check the log file that attached?? Edited April 25, 2019 by ORC2019 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,278 Posted April 25, 2019 Administrators Share Posted April 25, 2019 There's nothing special in the log, it's obviously a connection issue: Property(C): P_BAD_USER_INPUT = It is not possible to connect to the ESET Remote Administrator Server. Property(C): P_SERVER_CONNECTION_STATUS = CONNECTION_ERROR Please provide Procmon pcap logs, one from the client and one from the server, created during installation of the ERA Agent on the client. Also I would highly recommend upgrading ERA to ESMC as soon as possible. If you don't use ERA Proxy and agent connects to the ERA Server directly, just back up the db, ERA configuration and certificates and then send an ERA component upgrade task to the server and clients. For detailed instructions, please read https://support.eset.com/kb6819/. Link to comment Share on other sites More sharing options...
ORC2019 0 Posted April 25, 2019 Author Share Posted April 25, 2019 Thanks for the reply. I Things the Upgrade will solved this issue. I will read the KB that you mentioned. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 384 Posted April 26, 2019 ESET Staff Share Posted April 26, 2019 Relevant error installation log is: The semaphore timeout period has expired which indicates some network issues - it is actually system error, not installers. Have you tried to reboot device where you are installing AGENT? Link to comment Share on other sites More sharing options...
Recommended Posts