Jump to content

technika

Members
 View Profile  See their activity

  • Posts

    4

  • Joined

  • Last visited

 Content Type 

Posts posted by technika

    Not happy with ERA 6

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by technika

    Installing
    Getting "It is not possible to store big blocks of data in the database. Please configure the database server first." No difference it's All-in-one install or only Server install.
    Windows 10 x64
    MySQL server 5.6 x64
    MySQL ODBC connector 5.3 x64
    I've found my.ini under "C:\ProgramData\MySQL\MySQL Server 5.6". By MySQL documentation these settings should be red first. I've added max_allowed_packet=33M under the [mysqld] tag. Also tried 60M 128M and restarted computer every time. It's the same error on Windows 7 x64 on VMware Player.

    Gave up and went with built-in Microsoft SQL server.

     

    Adding computers

    By this documentation Rogue sensor only detected server itself. Although server can see, ping and use file sharing with every workstation in the network. So only manual entering workstation name/IP works.

     

    Deploying products using push install

    To upgrade clients ESET software I use Install by direct package URL. After ESET Remote Administrator Push Installation Requirements and Checklist and documentation in Client tasks --> Executions I'm still getting 3 rows in the end:

    ESET Remote Administrator Agent - Starting - Starting task

    Operating system - Running - Task started

    Operating system - Failed - Task failed

    with no further information.

    trace.log does not indicate anything on this case.

     

    I'm spending hours trying to fix one or another issue ESET left. It's bad to test products on your customers.

    ERA 6.1 clients not updating from server

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by technika

    I'm still getting "It is not possible to store big blocks of data in the database. Please configure the database server first." No difference it's All-in-one install or only Server install.
    I'm trying to install clean version of ERA 6 x64 on
    Windows 10 x64
    MySQL server 5.6 x64
    MySQL ODBC connector 5.3 x64
    I've found my.ini under "C:\ProgramData\MySQL\MySQL Server 5.6". By documentation MySQL should read these settings first. I've added max_allowed_packet=33M under the [mysqld] tag. Also tried 60M 128M and restartet computer everytime. What else could be wrong?

     

    [Edited]

    It's the same error on Windows 7 x64.

    Critical error (executing database script)

    in ESET PROTECT On-prem (Remote Management)

    Posted

    I'm having a similar problem. Using Windows Server 2012 R2 with MySQL Server 5.6 all english.

    ...
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\MySQL\CreateScripts\3_create_views.sql
MSI (s) (F4!8C) [19:35:36:925]: Closing MSIHANDLE (676) of type 790531 for thread 2188
MSI (s) (F4!8C) [19:35:36:925]: Creating MSIHANDLE (677) of type 790531 for thread 2188
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\MySQL\CreateScripts\4_init_data.sql
MSI (s) (F4!8C) [19:35:36:925]: Closing MSIHANDLE (677) of type 790531 for thread 2188
MSI (s) (F4!8C) [19:35:38:926]: Creating MSIHANDLE (678) of type 790531 for thread 2188
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\MySQL\CreateScripts\5_reports_interface.sql
MSI (s) (F4!8C) [19:35:38:927]: Closing MSIHANDLE (678) of type 790531 for thread 2188
MSI (s) (F4!8C) [19:35:40:119]: Creating MSIHANDLE (679) of type 790531 for thread 2188
ERROR: (DbCreate) Statement execution failed. Error: This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable). File: C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\MySQL\CreateScripts\5_reports_interface.sql. Statement: 
CREATE FUNCTION `ufn_create_hour_interval`(`timeParam` DATETIME)
    RETURNS TIMESTAMP
    LANGUAGE SQL
    NOT DETERMINISTIC
    CONTAINS SQL
    SQL SECURITY INVOKER
BEGIN
    return FROM_UNIXTIME(UNIX_TIMESTAMP(timeParam)- UNIX_TIMESTAMP(timeParam)%%(60*60));
END;
MSI (s) (F4!8C) [19:35:40:119]: Closing MSIHANDLE (679) of type 790531 for thread 2188
MSI (s) (F4!8C) [19:35:40:122]: Creating MSIHANDLE (680) of type 790531 for thread 2188
INFO: Successful GET property 'P_SILENT' with value - 
MSI (s) (F4!8C) [19:35:40:123]: Closing MSIHANDLE (680) of type 790531 for thread 2188
MSI (s) (F4!8C) [19:35:40:123]: Creating MSIHANDLE (681) of type 790531 for thread 2188
Error 30000. A critical error occurred. Please see the installation log for more information. Enabling the log is described at the ESET knowledge base website:
kb.eset.com

Issue ID: SOLN406
    
MSI (s) (F4!8C) [19:35:43:521]: Product: ESET Remote Administrator Server -- Error 30000. A critical error occurred. Please see the installation log for more information. Enabling the log is described at the ESET knowledge base website:
kb.eset.com

Issue ID: SOLN406
...

    Is there a workaround for this too?

×
×
  • Create New...