OpenEMM Technical Support Forum

Hi.
After the first login in OpenEMM 2019, the URL /dashboard.action dump an error in the catalina.out log file.

[SELECT mailing.mailing_id mailingid, mailing.work_status workstatus, MAX(cmp.component_id) preview_component, MIN(maildrop.senddate) senddate, mailing.shortname shortname, mediatype.param subject, COALESCE(SUM(account.no_of_mailings), 0) mailssent, MAX(maildrop.genstatus) genstatus, 'W' statusField FROM mailing_tbl mailing LEFT JOIN maildrop_status_tbl maildrop ON mailing.mailing_id = maildrop.mailing_id LEFT JOIN mailing_mt_tbl mediatype ON maildrop.mailing_id = mediatype.mailing_id LEFT JOIN mailing_account_tbl account ON (maildrop.mailing_id = account.mailing_id AND account.status_field = 'W') LEFT JOIN component_tbl cmp ON (maildrop.mailing_id = cmp.mailing_id AND cmp.comptype = ?) WHERE mailing.company_id = ? AND mailing.deleted = 0 AND maildrop.status_field = 'W' AND mediatype.mediatype = 0 AND maildrop.senddate > ? AND maildrop.senddate < ? GROUP BY mailing.mailing_id, mailing.shortname, mediatype.param, mailing.work_status ORDER BY ISNULL(senddate), senddate DESC];

nested exception is com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of ORDER BY clause is not in
GROUP BY clause and contains nonaggregated column 'emm.maildrop.senddate' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by

Any ideas?

Thank you.

Which version of MySQL or MariaDB do you use?

Mysql 5.7 (rh-mysql57)

This is a bug with MySQL - MariaDB works fine. We will provide a bug fix soon and announce its availability in the OpenEMM Wiki. What happens in the GUI when you access the dashboard?

Thank you for the answer.

When I access to the dashoard OpenEMM show this spanish message:

"Sorry, something went wrong
Se ha producido un error grave. Por favor, póngase en contacto con nuestro equipo de asistencia."

Thank you.

OK, that's really bad!

A fix is now available. Please use OpenEMMInstaller to update the frontend to version 19.04.000.482, and please tell us if it works for you now!