MartinK

ESET Staff
  • Content count

    1,038
  • Joined

  • Last visited

  • Days Won

    30

MartinK last won the day on October 2

MartinK had the most liked content!

1 Follower

About MartinK

  • Rank
    N/A

Profile Information

  • Gender
    Male
  1. Please check SERVER'strace.log located in: C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Logs for more detailed error.
  2. Install ERA on Linux with MYSQL failed

    It seems like problem with MySQL ODBC driver. What version of MySQL driver you are using? How did you installed it? We were using official MySQL drivers in our ERA appliances based on CentOS6/CentOS7. Could you verify that MySQL drivers is installed correctly in /etc/odbcinst.ini -> it should be defined in section [MySQL] as you defined this in installation parameters.
  3. Could you be more specific of package selections. i.e. which product you selected (type, version, language) and what ERA version are you using. Could you also check SERVER's trace.log for more detailed error?
  4. Reg. Microsoft SQL Server

    Fist of all, I would recommend to check, whether database data/configuration was also removed during installation. If it is still present, installing the same version of SQL Server should be enough to make it work. If previous steps won't work and you have full backup of ERA database, follow migration steps described in ERA documentation. Technically you will have to install SQL server of your choice (but must be supported by ERA), restore database from backup, configure accounts that will be used by ERA instance to access data, and re-configure ERA so that it can access data (i.e. adaptation of connection string to new database configuration).
  5. At least one successful connection of AGENT after you made last modification of dynamic group template is required. Maybe you made those changes after business hours? Also be aware that once you modify dynamic group template (any modification, even not related to rules) will result in empty list in console, until AGENT are reporting results for matching new version of template. EDIT: and for future reference, dynamic group with requested parameters is also described in ERA documentation examples.
  6. Errors like following: 2017-12-01 14:09:04 Error: CReplicationModule [Thread 2734]: CReplicationManager: Replication (network) connection to 'host: "localhost" port: 2222' failed with: (0x274d), No connection could be made because the target machine actively refused it means that AGENT is configured to connect to ERA at hostname "localhost". Not sure whether this AGENT is installed in the same host as is ERA, but if not, this is sign of its miss-configuration. I would recommend to request configuration of this AGENT (client details -> configuration) and check configuration of connection to ERA. Be aware that this configuration parameter is crucial, and wrong configuration may result in AGENT not able to connect to ERA -> you won't be able to fix this issue remotely once this happens.
  7. Certificate is used to identify AGENT when connecting to your ERA. Whoever owns this certificate can install AGENT so that it will be connecting to your ERA. Password is protecting certificate exported as file, so it makes sense to have it password protected in case it is back-up somewhere outside of ERA.
  8. ERA Cetificated SSL

    Please check documentation for Apache Tomcat upgrade. It mentions those files during backup procedure.
  9. I have yet again checked and mentioned package seems to be correctly configured. Could you please provide error output from client's trace.log (AGENT)? It should contain both expected, and computed checksum of package. From those two, we will at leas know whether installer or metadata are not correct.
  10. Seems to be a problem with AGENT certificate password. I am not sure what deployment scenario you used, but I don't think generated certificate has any password -> have you actually used empty password field for this certificate?
  11. I would try to use: package_app_id="com.eset.apps.business.eea.windows" package_os="windows" but that is just guessing - please provide trace log error in case it will fail.
  12. I can check log files for obvious problems, but nothing is guaranteed
  13. Could you provide details of package you are actually installing? Version, language, platform (x64/x32). Please provide also version of ERA Agent - we had a bug in older version (6.4) which resulted in similar failure.
  14. Just to let you know, even the old URL should be working now.
  15. What version of EES/EAV are you actually updating? I would recommend to check installation logs located in %temp%\eset\ directory on client machine. Full verbosity msiexec log should be present there, which may help. Have you tried to reboot machine and re-run installer? It is possible installation failed because of pending operating system updates.