Page tree

Versions Compared

Key

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

Table of Contents

Info
titleConvienient way to get highest ErrorCode

Just call the following command to get the currently highest value of E1XXX codes here in the doc. E1XXX only, because the E4321 is used as example below.
php -r '$text = file_get_contents("https://confluence.translate5.net/display/TAD/EventCodes"); preg_match_all("/(E1[0-9]{3})/", $text, $codes); print_r(max(array_unique($codes[0])));echo "\n";'

or to get a whole list sorted from lowest to highest:
php -r '$text = file_get_contents("https://confluence.translate5.net/display/TAD/EventCodes"); preg_match_all("/(E[0-9]{4})/", $text, $codes); $codes = array_unique($codes[0]); sort($codes); print_r($codes);echo "\n";'

In the future each error or event in translate5 should have an own event code to improve support / make live for help desk easier.

List of Error- and EventCodes

General

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.

Task & Workflow

EventCodeContextEventMessageDescription / Solution

Anchor
E1011
E1011
E1011

Task; WorkflowMulti Purpose Code logging in the context of a taskMulti Purpose code for several info logs around a task.
Also important in Context of workflow.

Anchor
E1012
E1012
E1012

Job; WorkflowMulti Purpose Code logging in the context of jobs (task user association)

Multi Purpose Code logging in the context of jobs (task user association)
Also important in Context of workflow.

Anchor
E1013
E1013
E1013

Workflow onlyMulti Purpose Code logging in the context of pure workflow processing

Multi Purpose Code logging in the context of workflow processing

Anchor
E1042
E1042
E1042

TaskThe task can not be removed due it is used by a user.One user has opened the task for reading or editing the task. Therefore this task can not be deleted.

Anchor
E1043
E1043
E1043

TaskThe task can not be removed due it is locked by a user.One user has opened the task for editing the task, or some other action has locked the task.
Therefore this task can not be deleted.

Anchor
E1044
E1044
E1044

TaskThe task can not be locked for deletion.The task must be locked by the deleting user, before it can be deleted. This lock could not be set.

Anchor
E1045
E1045
E1045

Task; ManualStatusCheck Plug-InThe Task can not be set to finished, since not all segments have a set status.Each segment must have set a status in order to finish the task.

Anchor
E1046
E1046
E1046

TaskThe current task status does not allow that action.This error occurs if the current status of the task does not allow the triggering action.

Anchor
E1049
E1049
E1049

Task; ArchiveTaskBeforeDelete Plug-InTask could not be locked for archiving, stopping therefore the delete call.The task must be locked by the deleting user, before it can be deleted. This lock could not be set.

Anchor
E1064
E1064
E1064

TaskThe referenced customer does not exist (anymore).The user tried to add a non existence client to a task. Probably the customer was deleted in the mean time.

Anchor
E1159
E1159
E1159

TaskTask usageMode can only be modified, if no user is assigned to the task.Remove first all assigned users from the task, change the usage mode and reassign the users again.

Anchor
E1171
E1171
E1171

Workflow onlyWorkflow Action: JSON Parameters for workflow action call could not be parsed with message: {msg}Check the parameters field of the mentioned action in the additional log data, it can not be parsed as JSON.

Anchor
E1172
E1172
E1172

Workflow User PreferencesThe referenced user is not associated to the task or does event not exist anymore.Reload the task properties.

Jobs (Association between Tasks and Users)

EventCodeContextEventMessageDescription / Solution

Anchor
E1061
E1061
E1061

JobThe job can not be removed, since the user is using the task.The user of the job has opened the associated task for reading or editing. Therefore this job can not be deleted.

Anchor
E1062
E1062
E1062

Job

The job can not be removed, since the task is locked by the user.

The user of the job has opened the associated task for editing.

Therefore this job can not be deleted.

Anchor
E1160
E1160
E1160

JobThe competitive users can not be removed, probably some other user was faster and you are not assigned anymore to that task.Leave the task and try to reopen it again.

Anchor
E1161
E1161
E1161

JobThe job can not be modified, since the user has already opened the task for editing. You are to late.Advice the user to leave the task, so that you can edit the Job again.

Anchor
E1163
E1163
E1163

Job

Your job was removed, therefore you are not allowed to access that task anymore.

Refresh the task overview.

Anchor
E1164
E1164
E1164

JobYou tried to open the task for editing, but in the meantime you are not allowed to edit the task anymore.Refresh the task overview.

Import

EventCodeContextEventMessageDescription / Solution

Anchor
E1083
E1083
E1083

FileparserThe encoding of the file "{fileName}" is none of the encodings utf-8, iso-8859-1 and win-1252.The named file is not encoded in one of the three supported types.

Anchor
E1084
E1084
E1084

FileparserGiven MID was to long (max 1000 chars), MID: "{mid}".One of the MIDs in the uploaded file is too long. Maximal 1000 bytes are allowed.

Anchor
E1000
E1000
E1000

SdlXliff FileparserThe file "{filename}" has contained SDL comments, but comment import is disabled: the comments were removed!

Enable comment import (see SDLXLIFF), or omit that file, or remove SDL comments for a successful import.

Anchor
E1001
E1001
E1001

SdlXliff Fileparser

The opening tag "{tagName}" contains the tagId "{tagId}" which is not SDLXLIFF conform!

That "{tagName}" contains the tagId "{tagId}" is not valid SDLXLIFF according to our reverse engineering of the SDLXLIFF format. Probably the parse has to be extended here.

Anchor
E1002
E1002
E1002

SdlXliff FileparserFound a closing tag without an opening one. Segment MID: "{mid}".Invalid XML structure in the mentioned SDLXLIFF file.

Anchor
E1003
E1003
E1003

SdlXliff Fileparser

There are change-markers in the sdlxliff-file "{filename}", but the import of change-markers is disabled.

Enable change-markers import (see SDLXLIFF), or omit that file, or remove change-markers for a successful import.

Anchor
E1004
E1004
E1004

SdlXliff Fileparser

Locked-tag-content was requested but tag does not contain a xid attribute.

Invalid SDLXIFF according to our reverse engineering.

Anchor
E1005
E1005
E1005

SdlXliff Fileparser

<sdl:seg-defs was not found in the current transunit: "{transunit}"

Invalid SDLXIFF according to our reverse engineering.

Anchor
E1006
E1006
E1006

SdlXliff Fileparser

Loading the tag information from the SDLXLIFF header has failed!

Check if SDLXLIFF header content is valid XML.

Anchor
E1007
E1007
E1007

SdlXliff Fileparser

The tag "{tagname}" is not defined in the "_tagDefMapping" list.

Invalid SDLXIFF according to our reverse engineering. The used tags are either not contained in the tag definition list in the header, or the parser did not parse the header completely.

Anchor
E1008
E1008
E1008

SdlXliff Fileparser

The tag ID "{tagId}" contains a dash "-" which is not allowed!

Dashes are not allowed, since this may interfere with the GUI where dashes are used as delimiter in the IDs.

Anchor
E1009
E1009
E1009

SdlXliff Fileparser

The source and target segment count does not match in transunit: "{transunit}".

Invalid SDLXIFF according to our reverse engineering.

Anchor
E1010
E1010
E1010

SdlXliff Fileparser

The tag "{tagname}" was used in the segment but is not defined in the "_tagDefMapping" list!

Invalid SDLXIFF according to our reverse engineering. The used tags are either not contained in the tag definition list in the header, or the parser did not parse the header completely.

Anchor
E1017
E1017
E1017

CSV FileparserThe regex {regex} matches the placeholderCSV string {placeholder} that is used in the editor_Models_Import_FileParser_Csv class to manage the protection loop.It is not allowed to use a regular expression to protect CSV content which matches the internally used placeholder.
Please find another solution to protect what you need to protect in your CSV via Regular Expression.

Anchor
E1018
E1018
E1018

CSV FileparserThe string $this->placeholderCSV ({placeholder}) had been present in the segment before parsing it. This is not allowed.The mentioned placeholder string is used for internally replacement, therefore it may not occur in the real CSV content.

Anchor
E1075
E1075
E1075

CSV FileparserError on parsing a line of CSV. Current line is: "{line}". Error could also be in previous line!The mentioned line could not be parsed as CSV line. Check the CSV content.

Anchor
E1076
E1076
E1076

CSV FileparserIn the line "{line}" there is no third column.Each line must contain at least 3 columns: mid, source and target column. Check the CSV content.

Anchor
E1077
E1077
E1077

CSV FileparserNo linebreak found in CSV: {file}No valid line break(s) were found in the CSV, does it contain only one line?

Anchor
E1078
E1078
E1078

CSV FileparserNo header column found in CSV: "{file}"No header columns could be found, check the CSV content.

Anchor
E1079
E1079
E1079

CSV FileparserIn application.ini configured column-header(s) "{headers}" not found in CSV: "{file}"The header column names of the CSV do not match to the configured header column names in "runtimeOptions.import.csv.fields".  The missing fields according to the configuration are shown in the error message.

Anchor
E1080
E1080
E1080

CSV FileparserSource and mid given but no more data columns found in CSV: "{file}"Each line must contain at least 3 columns: mid, source and target column. Check the CSV content.

Anchor
E1067
E1067
E1067

XLF 1.2 FileparserMRK/SUB tag of source not found in target with Mid: "{mid}"In the XLF a MRK or SUB tag was referenced in the source, but the referenced segment with the given mid was not found.

Anchor
E1068
E1068
E1068

XLF 1.2 FileparserMRK/SUB tag of target not found in source with Mid(s): "{mids}"In the XLF a MRK or SUB tag was referenced in the target, but the referenced segment with the given mid was not found.

Anchor
E1069
E1069
E1069

XLF 1.2 FileparserThere is other content as whitespace outside of the mrk tags. Found content: {content}Translate5 interprets the XLIFF 1.2 specification in a way that in a segmented segment there may not be any other content as whitespace outside between the <mrk type="seg"> tags. If this is the case translate5 can not import the XLF file.

Anchor
E1070
E1070
E1070

XLF 1.2 FileparserSUB tag of {field} is not unique due missing ID in the parent node and is ignored as separate segment therefore.The XML node surrounding a <sub> tag must contain an id in order to identfy that sub tag.

Anchor
E1071
E1071
E1071

XLF 1.2 FileparserMRK tag of {field} has no MID attribute.The given MRK tag does not contain a MID attribute.

Anchor
E1020
E1020
E1020

Relais Import

Errors in processing relais files: The following MIDs are present in the relais file "{fileName}" but could not be found in the source file, the relais segment(s) was/were ignored. MIDs: {midList}

For the listed MIDs the source segment was not found to the MID in the relais file, the Relais segment was ignored on import. The affected file is also logged.

Anchor
E1021
E1021
E1021

Relais Import

Errors in processing relais files: Source-content of relais file "{fileName}" is not identical with source of translated file. Relais target is left empty. Segments: {segments} 

For the listed segments the source content in the source file and in the relais file was different, therefore no relais target content was saved to the segment.

Anchor
E1022
E1022
E1022

Relais Import

Errors in adding relais segment: Source-content of relais file "{fileName}" is identical with source of translated file, but still original segment not found in the database: {segments}

This issue is similar to E1021, first a matching source segment was found to the relais segment, the source content equals, but the relais target data could not be saved. Investigate additional debug content!

Anchor
E1112
E1112
E1112

Relais ImportTask was configured with relais language, but some relais file were not found. See Details.Some of the work files do not have a corresponding file in the relais folder. In the details of the error the work files without a relais file are listed. Compare them with the files in the imported task.

Anchor
E1022
E1022
E1023

TBX

Parser

Unable to read the provided tbx file {filename}The provided file for parsing can is not readable.

Anchor
E1024
E1024
E1024

XML

Parser

Invalid XML: expected closing "{closingTag}" tag, but got tag "{receivedTag}". Opening tag was: {openingTag}Invalid xml chunk found while parsing xml file.

Anchor
E1028
E1028
E1028

TBX

Parser

{message}. \n Term collection name: {name}Log the term collection exception/info produced while the tbx parser is running for the term.

Anchor
E1031
E1031
E1031

Task Import - File UploadA file "{filename}" with an unknown file extension "{ext}" was tried to be imported.The uploaded file type is currently not supported.

Anchor
E1032
E1032
E1032

Task Import

The passed source language "{language}" is not valid.

The source language given for the new task is invalid or not found in the languages table of the application.

Anchor
E1033
E1033
E1033

Task ImportThe passed target language "{language}" is not valid.The target language given for the new task is invalid or not found in the languages table of the application.

Anchor
E1034
E1034
E1034

Task ImportThe import did not contain files for the relais language "{language}".No importable data was found in the import package for the chosen relais language.

Anchor
E1035
E1035
E1035

Task ImportThe given taskGuid "{taskGuid}" was not valid GUID.Please provide a valid GUID.

Anchor
E1036
E1036
E1036

Task ImportThe given userGuid "{userGuid}" was not valid GUID.Please provide a valid GUID.

Anchor
E1037
E1037
E1037

Task ImportThe given userName "{userName}" was not valid user name.Please provide a valid username.

Anchor
E1038
E1038
E1038

Task ImportThe import root folder does not exist. Path "{folder}".The provided ZIP package is unzipped on the server for further processing. That unzipped folder can not be found. This is probably a problem of permissions on the server.

Anchor
E1039
E1039
E1039

Task ImportThe imported package did not contain a valid "{proofRead}" folder.

The uploaded ZIP package did not contain a "proofRead" folder, which contains the data to be imported. See ZIP import package format.

Anchor
E1040
E1040
E1040

Task ImportThe imported package did not contain any files in the "{proofRead}" folder.The "proofRead" Folder in the imported ZIP package was empty, so there is nothing to be imported.

Anchor
E1052
E1052
E1052

Task ImportTODO Some of the tasks metaData can not be imported. See previous exception.Some of the tasks metaData can not be imported. See previous exception.

Anchor
E1053
E1053
E1053

Task Import; Pixel-Mapping MetaData

Pixel-Mapping: Import failed due not found customer specified by customer number in excel - client nr: {lastClientNr}


Anchor
E1054
E1054
E1054

Task Import; Pixel-Mapping MetaDataPixel-Mapping: missing default-values for pixel-width for font-size {fontSize}. Add the missing values to the config.Add the missing value in your defaultPixelWidths-settings in the task template config.

Anchor
E1096
E1096
E1096

Task Import; Pixel-Mapping MetaDataPixel-Mapping: ignored one ore more lines of the excel due one or more empty columns.Check the imported pixel-mapping.xlsx some of the needed columns were empty, see also error details for the collected lines with empty columns.

Anchor
E1060
E1060
E1060

Task ImportFor the fileextension "{extension}" no parser is registered. For available parsers see log details.

The user tried to import a file which can not be imported by the native import converters. See the log details for the available native importable file formats.

Otherwise consider to enable Okapi to convert the uploaded file into a native importable XLF format.

Anchor
E1135
E1135
E1135

Task ImportThere are no importable files in the Task. The following file extensions can be imported: {extensions}There is no file in the import package which can be imported. Neither native by translate5, nor via a converter plug-in like Okapi.

Anchor
E1136
E1136
E1136

Task ImportSome files could not be imported, since there is no parser available. For affected files see log details.

The user tried to import one or more files which can not be imported. Neither native by translate5, nor via a converter plug-in like Okapi. See the log details for the affected files.

Anchor
E1166
E1166
E1166

Task ImportAlthough there were importable files in the task, no files were imported. Investigate the log for preceeding errors.There was at least one importable file in the package which can be imported, but the import process did not import any file. Probably there was another error before, for example with a file converter plug-in like Okapi.

Export

EventCodeContextEventMessageDescription / Solution

Anchor
E1085
E1085
E1085

Task Export

this->_classNameDifftagger must be defined in the child class.

This is a developer issue, contact the developers.

Anchor
E1086
E1086
E1086

Tsk ExportError in Export-Fileparsing. instead of a id="INT" and a optional field="STRING" attribute the following content was extracted: "{content}"The parsing of the internal <lekTargetSeg/> placeholders in the skeleton data failed.

Anchor
E1087
E1087
E1087

Task ExportSee E1086

Anchor
E1088
E1088
E1088

Task ExportError in diff tagging of export. For details see the previous exception.The export with enabled automatic diff of the content fails. The original message of the export should be attached.

Anchor
E1089
E1089
E1089

Task Export with DiffTag syntax error in the segment content. No diff export is possible. The segment had been: "{segment}"In this segment for one closing tag no corresponding opening tag exists - or the tagorder had been syntactically incorrect already before the import in the editor. Therefore it is not possible to create an export with sdl-change-marks in it. Try to export without change-marks.

Anchor
E1090
E1090
E1090

Task Export with DiffThe number of opening and closing g-Tags had not been the same! The Segment had been: "{segment}"Similar to E1089.

Anchor
E1091
E1091
E1091

Task Export with DiffSee E1089

Anchor
E1092
E1092
E1092

Task Export with DiffSee E1090

Anchor
E1093
E1093
E1093

Task Export with DiffSee E1090

Anchor
E1143
E1143
E1143

Task ExportExportedWorker: No Parameter "zipFile" given for worker.This is an implementantion error.

Anchor
E1144
E1144
E1144

Task ExportExportedWorker: No Parameter "folderToBeZipped" given for worker.This is an implementantion error.

Anchor
E1145
E1145
E1145

Task ExportCould not create export-zip.

Anchor
E1146
E1146
E1146

Task ExportThe task export folder does not exist, no export ZIP file can be created.The user has probably clicked multiple times on the export button while the first export was still running.

Anchor
E1147
E1147
E1147

Task ExportThe task export folder does not exist or is not writeable, no export ZIP file can be created.See E1146.

Anchor
E1149
E1149
E1149

Task ExportExport: Some segments contains tag errors.See error details for affected segments and details.

Anchor
E1157
E1157
E1157

Task ExportExport: the file "{file}" could not be exported, since had possibly already errors on import.See error details for affected file and details.

Anchor
E1170
E1170
E1170

Task Metadata ExportThe Metadata of the currently filtered tasks can not be exported as Excel-file.

Language Resources

EventCodeContextEventMessageDescription / Solution

Anchor
E1050
E1050
E1050

Language Resources; Task

Referenced language resource not found.

This error can happen on the association of language resources to tasks, if the a chosen language resource was deleted in the meantime.

Anchor
E1051
E1051
E1051

Language Resources; TaskCannot remove language resource from task, since task is used at the moment.The association of a language resource to a task can not removed, since the affected task is used by a user at the moment.

Anchor
E1106
E1106
E1106

Language ResourcesGiven Language-Resource-Service "{serviceType}." is not registered in the Language-Resource-Service-Manager!This happens if a task has associated a language resource, which has completly deactivated (for example by deactivating the plug-in).

Anchor
E1158
E1158
E1158

Language ResourcesA Language Resources cannot be deleted as long as tasks are assigned to this Language Resource.Remove all tasks first from that resource.

Anchor
E1169
E1169
E1169

Language ResourcesThe task is in use and cannot be reimported into the associated language resources.Check who or what process is locking the task

Terminology

EventCodeContextEventMessageDescription / Solution

Anchor
E1152
E1152
E1152

Terminology

Missing mandatory collectionId for term creation.


Anchor
E1153
E1153
E1153

TerminologyMissing mandatory language (ID) for term creation.

Anchor
E1154
E1154
E1154

TerminologyGroupId was set explicitly, this is not allowed. Must be set implicit via a given termEntryId.

Anchor
E1105
E1105
E1105

Terminology

There is no proposal which can be confirmed.

The user tried to confirm a term proposal on a term which does not have any proposal to be confirmed.

Anchor
E1108
E1108
E1108

TerminologyThere is no attribute proposal which can be confirmed.The user tried to confirm a term attribute proposal on a attribute which does not have any proposal to be confirmed.

Anchor
E1109
E1109
E1109

Terminology

There is no proposal which can be deleted.

The user tried to deleted a term proposal on a term which does not have any proposal.

Anchor
E1110
E1110
E1110

TerminologyThere is no attribute proposal which can be deleted.The user tried to deleted a term attribute proposal on a attribute which does not have any proposal.

Anchor
E1111
E1111
E1111

TerminologyThe made term proposal does already exist as different term in the same language in the current term collection.Search for the proposed term in the collection.

Anchor
E1113
E1113
E1113

TerminologyNo term collection assigned to task although tasks terminology flag is true.This indicates a new programming error or manual change of the data in the DB. If associations between TermCollections and task are maintained via API the "terminlogy" flag of the task entity should be maintained correctly.

Anchor
E1114
E1114
E1114

Terminology

The associated collections don't contain terms in the languages of the task.

Could happen when all terms of a language are removed from a TermCollection via term import after associating that term collection to a task.

Anchor
E1115
E1115
E1115

TerminologyCollected terms could not be converted to XML.Internal SimpleXML error.

Anchor
E1116
E1116
E1116

Terminology

Could not load TBX into TermTagger: TBX hash is empty.

There was probably an error on the TBX generation before.

Anchor
E1117
E1117
E1117

TerminologyCould not load TBX into TermTagger: TermTagger HTTP result was not successful!

Loading terminology (TBX generated by translate5) into a termtagger instance has failed!

Look also for a directly following E1133 or E1134 in the log.

Anchor
E1118
E1118
E1118

TerminologyCould not load TBX into TermTagger: TermTagger HTTP result could not be decoded!

Loading terminology (TBX generated by translate5) into a termtagger instance has probably failed. Since the answer can not be decoded this could mean that the request has failed, or it was successful without answering correctly.

Look also for a directly following E1133 or E1134 in the log.

Anchor
E1119
E1119
E1119

TerminologyTermTagger communication Error.

Anchor
E1130
E1130
E1130

TerminologyTermTagger communication Error, probably crashing the TermTagger instance.See Details for the transferred segments to find out which content led to the crash. Probably other errors before or after that error could contain usable information too.

Anchor
E1120
E1120
E1120

TerminologyTermTagger returns an error on tagging segments.

Anchor
E1121
E1121
E1121

TerminologyTermTagger result could not be decoded.Look also for a directly following E1133 or E1134 in the log.

Anchor
E1122
E1122
E1122

TerminologyTermTaggerImport Worker can not be initialized!Some error happened on worker initialization, check logged parameters.

Anchor
E1123
E1123
E1123

TerminologySome segments could not be tagged by the TermTagger.Happens on termtagging while importing a task. See the error details to get a list of affected, non tagged segments.

Anchor
E1124
E1124
E1124

TerminologyParameter validation failed, missing serverCommunication object.Happens on live termtagging on segment editing only.

Anchor
E1125
E1125
E1125

TerminologyTermTagger DOWN: one or more configured TermTagger instances are not available: {serverList}One or more TermTagger instances are not available. All TermTagger instances are listed with their status. Please check them manually and restart them if needed.

Anchor
E1126
E1126
E1126

Terminology

Plugin TermTagger URL config default, import or gui not defined (check config runtimeOptions.termTagger.url)

One of the required config-settings default, import or gui under runtimeOptions.termTagger.url is not defined in configuration.

Anchor
E1127
E1127
E1127

Terminology

Plugin TermTagger default server not configured: configuration is empty.

The required config-setting runtimeOptions.termTagger.url.default is not set in configuration. Value is empty.

Anchor
E1128
E1128
E1128

TerminologySee E1122.

Anchor
E1129
E1129
E1129

TerminologyTermTagger DOWN: The configured TermTagger "{termTaggerUrl}" is not reachable and is deactivated in translate5 temporary.

The termTagger server as specified in the error message is deactivated automatically. On each periodical cron call (normally all 15 minutes) all termtaggers are checked for availability. If a previously deactivated TermTagger is available again, it is reactivated automatically.

To reactivate the TermTagger servers manually just call the following SQL statement in the Database:

Code Block
languagesql
DELETE FROM `Zf_memcache` WHERE `id` = 'TermTaggerDownList';


Anchor
E1131
E1131
E1131

TerminologyTermTagger DOWN: No TermTagger instances are available, please enable them and reimport this task.

Start the TermTagger(s) if not already done.

If the TermTaggers were started and crashed then, see E1129 how to reactivate the TermTaggers marked as offline in translate5. After reactivation, reimport the task. The task clone functionality can be used to reimport the task.

Anchor
E1132
E1132
E1132

TerminologyConflict in merging terminology and track changes: "{type}".Merging track changes and terminology was producing and error. See log details for more information.

Anchor
E1133
E1133
E1133

TerminologyTermTagger reports error "{error}".

There was an error on the side of the termtagger, the error message was displayed.

Attaching more log data to that error is not possible, but in the log there should be another error (E1117, E1118, E1121) directly after that error.

Anchor
E1134
E1134
E1134

TerminologyTermTagger produces invalid JSON: "{jsonError}".

The JSON produced by the TermTagger was invalid, see the JSON decode error message.

Attaching more log data to that error is not possible, but in the log there should be another error (E1117, E1118, E1121) directly after that error.

Segment

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).

Plug-In Groupshare

EventCodeContextEventMessageDescription / Solution

Anchor
E1097
E1097
E1097

Plug-In GroupShare

Multi Purpose Code logging in the context of Groupshare

Multi Purpose Code logging in the context of Groupshare.

Anchor
E1098
E1098
E1098

Plug-In GroupShareGroupshare Plug-In: ExceptionGeneral Purpose Exception

Anchor
E1099
E1099
E1099

Plug-In GroupShareGroupshare Plug-In: No valid license token in cache for current userThere is no valid license token in the cache for the current user. The license token creation for this user was probably done before, but the token does not exist anymore.

Plug-In MatchAnalysis

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.

Anchor
E1167
E1167
E1167

Plug-In MatchAnalysisMatchAnalysis Plug-In: analysis and pre-translation cannot be run.The task was locked by another process, so no analysis and pre-translation is possible.

Anchor
E1168
E1168
E1167

Plug-In MatchAnalysisMatchAnalysis Plug-In: TermTagger worker for pre-translation can not be initialized.

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!








Openid connect

EventCodeContextEventMessageDescription / Solution

Anchor
E1165
E1165
E1165

Openid

Error on openid authentication: {message} \n Request params: {request} \n Session: {session} \n Openid params: {openid}

Openid connect client exception. The error is thrown by the openidconnect library. This will output the original error message and some additional debug info

Anchor
E1172
E1172
E1172

OpenidThe OpenIdUserData attribute {attribute} was not set by the requested OpenID server.Make sure, that your IDP (identity provider) server provides the relevant attribute.

Anchor
E1173
E1173
E1173

OpenidNo roles are provided by the OpenID Server to translate5. The default roles that are set in the configuration for the customer are used.If you want to set the roles of the user through your IDP server, provide the role or roles attribute there.

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.