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!


Authentication

EventCodeContextEventMessageDescription / Solution

Anchor
E1156
E1156
E1156

AuthenticationTried to authenticate via hashAuthentication, but feature is disabled in the config!

Please set runtimeOptions.hashAuthentication in the configuration to one of the following values:

disabled: the feature is disabled and produces this error.
dynamic: use a dynamic auth hash.
static: use a static auth hash.

See Single Click Authentication.

Users & Customers

EventCodeContextEventMessageDescription / Solution

Anchor
E1047
E1047
E1047

CustomerA client cannot be deleted as long as tasks are assigned to this client.Remove all tasks first from that customer.

Anchor
E1063
E1063
E1063

CustomerThe given client-number is already in use.There exists already a customer with that client-number.

Anchor
E1048
E1048
E1048

User

The user can not be deleted, he is PM in one or more tasks.

Change the PMs in the affected tasks.

Anchor
E1094
E1094
E1094

User

User can not be saved: the chosen login does already exist.

Use a different login.

Anchor
E1095
E1095
E1095

UserUser can not be saved: the chosen userGuid does already exist.Use a different userGuid, if no userGuid was provided explicitly, just save again to generate a new one.

Anchor
E1104
E1104
E1104

CustomerThe given domain is already in use.The given domain is already defined for one of the customers.

...

EventCodeContextEventMessageDescription / Solution

Anchor
E1065
E1065
E1065

SegmentThe data of the saved segment is not valid.The data of the saved segment contains invalid data, see error details for more information.

Anchor
E1066
E1066
E1066

SegmentThe data of the saved segment is not valid.See E1065, in addition that the validations contain at least an error where the segment is either to long or to short. This error is separate since it should produce an warning instead just a debug level entry.

Anchor
E1155
E1155
E1155

SegmentUnable to save the segment. The segment model tried to save to the materialized view directly.Programming error: The writeable table of the segment is set to the materialized view. This is wrong, since the way is: write to the LEK_segments table, write to the data table, then update the view with the data from there.

Anchor
E1081
E1081
E1081

Segment Pixellength

Textlength by pixel failed; most probably data about the pixelWidth is missing: fontFamily: "{fontFamily} fontSize: "{fontSize}".

Same as E1082 below, but no default width is available for that font and font size.

Anchor
E1082
E1082
E1082

Segment PixellengthSegment length calculation: missing pixel width for several characters.

On of the characters in the segment has no pixel length defined, the default pixel width is used.

This error happens in most cases on the export of a task, where the length of the segments is finally checked. Also it happens on saving a segment.





Excel Ex-Import

EventCodeContextEventMessageDescription / Solution

Anchor
E1137
E1137

E1137

Task

Task can not be exported as Excel-file.


Anchor
E1141
E1141

E1141

Task

Excel Reimport: upload failed.

error on writing file to /data/editorImportedTasks/{takGuid}/excelReimport

Anchor
E1138
E1138

E1138

Task

Excel Reimport: Formal check failed: task-guid differs in task compared to the excel.


Anchor
E1139
E1139

E1139

Task

Excel Reimport: Formal check failed: number of segments differ in task compared to the excel.


Anchor
E1140
E1140

E1140

Task

Excel Reimport: Formal check failed: segment #{segmentNr} is empty in excel while there was content in the the original task.


Anchor
E1142
E1142

E1142

Segment

Excel Reimport: at least one segment needs to be controlled.

This is actually a warning. You have to control all segments in the given list. They may have an invalid tag-structure (eg. open a tag but not closing it) or something similar. This can lead to problems on further workflow steps.

Anchor
E1148
E1148

E1148

TaskTask can not be locked for excel export, no excel export could be created.

That means the task is currently in use by another user / process.

This is logged as info, since this can happen if another proofreader is editing while another proofreader is finishing the task.

Plug-Ins

Plug-In Okapi

EventCodeContextEventMessageDescription / Solution

Anchor
E1055
E1055
E1055

Plug-In Okapi

Okapi Plug-In: Bconf not given or not found: {bconfFile}

Either there was no bconf given, or the default bconf could not be found.
Default for import should be: ./application/modules/editor/Plugins/Okapi/data/okapi_default_import.bconf
Default for export should be: ./application/modules/editor/Plugins/Okapi/data/okapi_default_export.bconf

Anchor
E1056
E1056
E1056

Plug-In OkapiOkapi Plug-In: tikal fallback can not be used, workfile does not contain the XLF suffix: {workfile}In seldom scenarios tikal is used for export, if tikal receives an non XLIFF file this error is thrown.

Anchor
E1057
E1057
E1057

Plug-In Okapi

Okapi Plug-In: Data dir not writeable: {okapiDataDir}

Solution: change filesystem rights so that the apache user can write into
./application/modules/editor/Plugins/Okapi/data

Anchor
E1058
E1058
E1058

Plug-In OkapiOkapi Plug-In: Error in converting file {file} on import. See log details for more information.An error described in message happend on converting the file.
Check the message, since the error could be independent from the given file, for example if some Okapi configuration was wrong, or the Okapi server is not available.
A full log of the happened exception is available in the log (level debug).

Anchor
E1059
E1059
E1059

Plug-In OkapiOkapi Plug-In: Configuration error - no Okapi server URL is configured!Set a correct Okapi server URL in the configuration:

Anchor
E1150
E1150
E1150

Plug-In OkapiOkapi Plug-In: The exported XLIFF contains empty targets, the Okapi process will probably fail then.If the Okapi export failed investigate the XLIFF to find out the empty segments and why they are empty.

Anchor
E1151
E1151
E1151

Plug-In OkapiOkapi Plug-In: Error in converting file {file} on export. See log details for more information.

An error described in message happend on converting the file.

Check the message, since the error could be independent from the given file, for example if some Okapi configuration was wrong, or the Okapi server is not available.

A full log of the happened exception is available in the log (level debug).

...

EventCodeContextEventMessageDescription / Solution

Anchor
E1100
E1100
E1100

Plug-In MatchAnalysis

Multi Purpose Code logging in the context of MatchAnalysis

Multi Purpose Code logging in the context of MatchAnalysis.

Anchor
E1101
E1101
E1101

Plug-In MatchAnalysisDisabled a Language Resource for analysing and pretranslation due too much errors.

Check the details and also the logs for more information.
Enable debugging for domain "plugin.matchanalysis" to get more info about the problems of the disabled language resources.

Anchor
E1102
E1102
E1102

Plug-In MatchAnalysisUnable to use connector from Language Resource "{name}". Error was: "{msg}".

Check the details and also the logs for more information.
Enable debugging for domain "plugin.matchanalysis" to get more info about the problems of the disabled language resources.

Anchor
E1103
E1103
E1103

Plug-In MatchAnalysisMatchAnalysis Plug-In: tried to load analysis data without providing a valid taskGuidA valid taskGuid must be provided here as parameter, to load only the analysis data for one task.

Plug-In NecTm

EventCodeContextEventMessageDescription / Solution

Anchor
E1162
E1162
E1162

Plug-In NecTm

NecTm Plug-In: Synchronize of NEC-TM-Tags with our categories failed

NecTm Plug-In: Synchronize of NEC-TM-Tags with our categories failed. Check if the api-server of NEC-TM is running!








EventCode Design rules / decisions

  • Prefixed with "E" so that a search for the error code through the code is more reliable than just searching for a number
  • No structure in the numbering to prevent discussions is it an error E12XX or E45XX
  • Do not start at 1 and don't use leading zeros.
  • Each usage of an error in the code should get separate code. Even if the error message / reason is the same. Reason is that the help desk might need to do different things in different cases.
    • Information about the error here in the list should not be copied, but errors can point to another errors: "E 4321: See E 1234". Thats work to maintain, but better as confusing the client by giving wrong hints.
    • if it makes sense for the support / help desk to split up an error in different errorcodes because of different reasons, than this should be done in the code so far
  • Never forget the purpose of event codes: make life easier for support / help desk.