jinlei801011

Members
  • Content count

    85
  • Joined

  • Last visited

  • Days Won

    1

jinlei801011 last won the day on November 18 2015

jinlei801011 had the most liked content!

About jinlei801011

  • Rank
    N/A

Recent Profile Visitors

782 profile views
  1. ESET micro update issue

    Hi Michal, We know EP6.6 doesn't support mirror updates. So we use EP6.5 also tried EP6.2, but same issue. We guess it is the micro update files issue. Thanks Jin
  2. ESET micro update issue

    We have few customers are using ESET micro update in the past few years and it is working fine. The steps we did is 1. Setup an ESET mirror server using EEA/EES or EFSW 2. Download ESET micro update file (Levels) and save it to local c:\ESETMicro 3. ESET mirror server update from ESET micro update file (Update URL: c:\ESETMicro) 4. Clients update from ESET mirror server (Update URL: hxxp://mirror server ip:2221) 5. Download ESET micro update file (nanos) on every Monday and overwirtes the files in c:\ESETMicro 6. Mirror server and clients will auto update. The above stpes are working fine. But we encountered issue when we use it for a new customer recently. Step 1 to 4 no problem, working fine. But when we apply the coming week update file "nanos", Only mirror server can update, clients cannot, no any error message shown. We checked this issue with our local support, they told us ESET mirror server will re-generate and replace the update.ver file for clients, that's why clients cannot get updates from mirror server. We need to off mirror feature in EEA, use share folder to store ESET micro update files and let all clients point to this folder to get updates. My question is why we can use the mirror function with ESET micro updates last time? Thanks Jin
  3. Tried to install ERA on Centos with MYSQL, encounter error 2017-12-07 05:22:18 Information: DbCheckConnection: Set output property: P_DB_CONNECTION_STATUS = 2017-12-07 05:22:18 Information: DbCheckConnection: Set output property: P_DB_STATUS = 2017-12-07 05:22:18 Information: DbCheckConnection: Set output property: P_DB_UPGRADE = 2017-12-07 05:22:18 Information: DbCheckConnection: Set output property: P_DB_USE_FIRST_USER = 2017-12-07 05:22:18 Information: DbCheckConnection: Set output property: P_DB_PORT = 3306 2017-12-07 05:22:18 Information: GetDatabaseServerConnectionStringWithoutEscape: Created connection string: 'Driver=MySQL;Server=127.0.0.1;Port=3306;User=******;Password={******};CharSet=utf8;NO_LOCALE=1;' 2017-12-07 05:22:18 Information: Entering function: void Era::Setup::Common::CustomActions::CDatabaseReader::TestConnection(const string&, bool) 2017-12-07 05:22:18 Information: Leaving function: void Era::Setup::Common::CustomActions::CDatabaseReader::TestConnection(const string&, bool) 2017-12-07 05:22:18 Information: Exception thrown while connecting to the specific database as a user.. Error code: 0, DB specific error code: 0, error message: [unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_HENV failed 2017-12-07 05:22:18 Information: DbCheckConnection: Set output property: P_DB_CONNECTION_STATUS = 0 2017-12-07 05:22:18 Information: DbCheckConnection: Return code: 0 2017-12-07 05:22:18 Information: Installer: Unknown database driver or data source name (DSN) 2017-12-07 05:22:18 Information: Installer: Error: Unknown database driver or data source name (DSN)
  4. About false positive

    My ESET detected some files are viruses, the action is "Cleaned by deleting (after next restart)". However I am sure these files are safe, how to prevent the files from being deleted? If exclude these files from real-time scan, after restart, will ESET still delete it?