Search Engine: Elastic

Article ID: 128713, created on Apr 21, 2016, last review on Apr 21, 2016

  • Applies to:
  • Operations Automation


An Open-Xchange "executing configuration" APS task fails during user provisioning with the following output:

Execution of configuration script for instance with id 10101 of service with id account of instance with id 1000 of application with id 101 failed - returned value: -1 output: '' errors: 'Creating OX mail account conetxt=10101 ''

user created

Update context aliases list

Failed to create OX mail account conetxt=10101 '': Error unmarshaling return; nested exception is:
java.lang.ClassNotFoundException: com.mysql.jdbc.MysqlDataTruncation (no security manager: RMI class loader disabled)

The following error is logged to /var/log/open-xchange/open-xchange-admin.log.0 on OX server during the task execution:

Apr 21, 2016 9:06:56 AM create
INFO: User 10 created!
Apr 21, 2016 9:06:56 AM change
com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'login_info' at row 1


The default column size of login2context.login_info column of configdb database is insufficient for the parameters passed by the OA task. The issue with the column size is recognized as an Open-Xchange issue, fixed in 7.6.1 version:

Open-Xchange 7.6.1 release notes

"Change#2166 Enhance length of column login_info to varchar(255).
Column login info for table login2context on configdb does not match size desired by the RFC.
The change was implemented based on a new framework announced with Change 2163."


Change the faulty column size manually in MySQL database server on the OX node and re-run the task:

# mysql configdb
mysql> alter table login2context modify login_info varchar(255) COLLATE utf8_unicode_ci NOT NULL;

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF