Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

EventCodeContextEventMessageDescription / Solution

Anchor
E0000
E0000
E0000

everywhereSeveralCode used for multi purposes: Mostly for debug messages below level warn, where no fixed message is needed.

Anchor
E9999
E9999
E9999

everywhereSeveralDefault code used for old error messages, which are not converted yet to the new error code system.

Anchor
E1014
E1014
E1014

everywhereLog HTTP RequestThe HTTP request to the server and its parameters are logged. Generally for debugging only.

Anchor
E1015
E1015
E1015

entitiesDuplicate KeyA database key for the entity to be saved does already exist.

Anchor
E1016
E1016
E1016

entitiesIntegrity Constraint Violation

An entity can not be added or updated since a referenced entity does not exist (anymore).

Or an entity can not be updated or deleted since it is referenced by other entities.

Anchor
E1019
E1019
E1019

everywhereHTTP Status 404The requested URL / page was not found, the API endpoint in the application does not exist.

Anchor
E1025
E1025
E1025

everywhereHTTP Status 422The PUT / POST request to that URL could not be processed due invalid given data.
The invalid fields are listed in the result from the server.

Anchor
E1026
E1026
E1026

everywhereHTTP Status 422

The File Upload did not succeed PUT / POST request to that URL could not be processed due invalid given data.

The invalid fields are listed in the result from the server.

Anchor
E1041
E1041
E1041

everywhereHTTP Status 409

The PUT / POST request to that URL could not be processed due the given data would produce an invalid state of the entity on the server.

If possible, the causing fields are listed in the result from the server, or the error message is self explaining.

Anchor
E1027
E1027
E1027

everywherePHP Fatal ErrorPHP Fatal error, see error message for details.

Anchor
E1029
E1029
E1029

everywherePHP WarningPHP Warning, see error message for details.

Anchor
E1030
E1030
E1030

everywherePHP InfoPHP Info, see error message for details.

Anchor
E1072
E1072
E1072

WorkerCan not trigger worker URL: {host}:{port} Error: {errorName} ({errorNumber})The triggered worker URL is technically not available. Local firewall problems? Is the configured "runtimeOptions.server.name" available and callable from the translate5 instance? If not, it can help to configure "runtimeOptions.worker.server" with the local host name or the localhost IP, basicly the server adress which points to the local server and is available for the translate5 instance.

Anchor
E1073
E1073
E1073

WorkerWorker URL result is no HTTP answer!: {host}:{port}This can only happen if the worker URL is not pointing to an translate5 instance, or if there is an error on the translate5 instance. In the latter case investigate the log for further errors.

Anchor
E1074
E1074
E1074

WorkerWorker HTTP response state was not 2XX but {state}.This should happen only if there is an error on the translate5 instance. In the latter case investigate the log for further errors.

Anchor
E1107
E1107
E1107

WorkerWorker HTTP response state was 404, the worker system requests probably the wrong server!

Check the server URL configuration values.

Either runtimeOptions.worker.server or runtimeOptions.server.protocol and runtimeOptions.server.name are pointing to a wrong server / translate5 installation!

This can also happen, if the server name is resolving to multiple IPs on the server it self (multiple entries in the /etc/hosts for example).

Anchor
E1219
E1219
E1219

WorkerWorker "{worker}" failed on initialisation.Check other errors , this message is just for debugging.

Anchor
E1201
E1201
E1201

DBStill producing a DB DeadLock after {retries} retries.

A transaction was repeated X times after a deadlock and it is still producing a deadlock.
The original dead lock exception is contained in this exception.

Anchor
E1202
E1202
E1202

DBA transaction could be completed after {retries} retries after a DB deadlock.This is just a info / debug message to track if a deadlock occured, an that it could be successfully executed after X retries.

Anchor
E1203
E1203
E1203

DBA transaction was rejected after a DB deadlock.This is just a info / debug message to track if a deadlock occured, an that it was intentionally rejected.

Anchor
E1220
E1220
E1220

API FilterErrors in parsing filters Filterstring: "{filter}"The given JSON filter string can not parsed. Is the given JSON valid?

Anchor
E1221
E1221
E1221

API FilterIllegal type "{type}" in filterThe given filter type does not exist.

Anchor
E1222
E1222
E1222

API FilterIllegal chars in field name "{field}"There were invalid characters in the field name. Only Alphanumeric characters and dash "-" and underscore "_" are allowed.

Anchor
E1223
E1223
E1223

API FilterIllegal field "{field}" requestedThe requested field does not exist.

Anchor
E1224
E1224
E1224

API FilterUnkown filter operator "{operator}" from ExtJS 5 Grid Filter!The given filter operator is invalid.

Anchor
E1225
E1225
E1225

API Filter JoinGiven tableClass "{tableClass}" is not a subclass of Zend_Db_Table_Abstract!The given tableClass in the join filter must be a sub class of Zend_Db_Table_Abstract

...