OpenEMM Technical Support Forum

What version of MySQL do you use?

Seems like your database does not support the syntax:
ALTER TABLE prevent_table_drop DROP KEY IF EXISTS lock$cust_ban_tbl;

If so, just execute the statements of this script "one by one" manually"

Problem is fixed in OpenEMM Runtime version 20.10.039, which is now available.

This bug was already fixed.
To repair your DB and prevent this from happening again, please execute this SQL on your DB:

INSERT INTO agn_dbversioninfo_tbl (version_number, updating_user, update_timestamp)
VALUES ('20.07.020', CURRENT_USER, CURRENT_TIMESTAMP);

Bugfix is backported in Runtime 20.04.000.047 an available at Update Site

In LTS 20.04 all relevant configuration properties are migrated from emm.properties in db config_tbl for later use in LTS 20.10.
This happens on EMM startup. SO if the values are included in emm.peroperties an you (re-)start up your EMM the values should pop up in config_tbl.

This bug is fixed in LTS 20.10
Will be backported in LTS 20.04 quite soon (maybe tomorrow)

Is the following file available in your CATALINA_HOME ?: ${CATALINA_HOME}/lib/catalina.jar Can you execute: ${JAVA_HOME}/bin/java -cp ${CATALINA_HOME}/lib/catalina.jar org.apache.catalina.util.ServerInfo This should return your available Tomcat Version Info. The Data in our shipped folder "/hom...

Can you please restart the Program "OpenEMMInstaller.sh" with parameter "-debug".
It will print the stacktrace of the problem.
Please post it here.

Hi, Seems like there have been duplicates in some older OpenEMM version which were migrated. When there are duplicates the first entry returned by database will be used. To fix this just remove the unwanted configuration entries from database table "config_tbl". Next OpenEMM version 20.10 ...

Please try our new released Version 20.04.000.155.
It is available via the standard update process and should fix this problem.

Didn't you write you tried to install "frontend 20.04.000.143" in your first post?
Does the error happen in version 20.04 or 19.10?
In 19.10 this permission did not exist.
It is new in 20.04.

Line 18 means the permission "campaign.autoopt". Maybe this permission entry vanished somehow in your database. Please try this statement and re-execute the userrights.sql. INSERT INTO permission_tbl (permission_name, category, sub_category, sort_order, feature_package) VALUES ('campaign.a...

Hello, It seems like something went wrong in the initial migration to the new version. Please execute the following SQL Statement once on your database. Then restart the OpenEMM. This will execute the migration for the layout logos again. This should fix the Logo problem once for all. After the Rest...

Hello, I also checked the currently available online Version of the OpenEMM Runtime (19.10.009.016). - It copies server.xml.template to server.xml if there is no server.xml yet - It backups and restores an existing server.xml As far as I can see there is no problem with the current version. Does the...

Problem ist that the property value "dbms" in your "dbcfg"-file is missing. Default location of that file is "/opt/agnitas.com/etc/dbcfg". Other locations may be: - "/home/openemm/etc/dbcfg" - "/opt/openemm/dbcfg" It should contain one of the followi...