Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 229 Next »

E1106

Convienient 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

E0000

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

E9999

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

E1014

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

E1015

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

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.

E1019

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

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.

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.

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.

E1027

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

E1029

everywherePHP WarningPHP Warning, see error message for details.

E1030

everywherePHP InfoPHP Info, see error message for details.

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.

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.

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.

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

E1219

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

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.

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.

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.

E1220

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

E1221

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

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.

E1223

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

E1224

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

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

DataProvider


Authentication

EventCodeContextEventMessageDescription / Solution

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.

Categories

EventCodeContextEventMessageDescription / Solution

E1179

Category AssocsSave category assocs: categories could not be JSON-decoded with message: {msg}

The given data for the categories is wrong; check this first.

Users & Customers

EventCodeContextEventMessageDescription / Solution

E1047

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

E1063

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

E1048

User

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

Change the PMs in the affected tasks.

E1094

User

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

Use a different login.

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.

E1104

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

Task & Workflow

EventCodeContextEventMessageDescription / Solution

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.

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.

E1013

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

Multi Purpose Code logging in the context of workflow processing

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.

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.

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.

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.

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.

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.

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.

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.

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.

E1172

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

E1205

Workflow User PreferencesMissing workflow step in given data.Missing workflow step in given data.

E1206

Workflow User PreferencesMissing workflow step in given data.Missing workflow step in given data.

E1210

Task; WorkflowThe targetDeliveryDate for the task is deprecated. Use the LEK_taskUserAssoc deadlineDate instead.

Temporary warning for the task targetDeliveryDate (delivery date) api field. Deadline date should be defined on user- task-assoc level.

E1216

Task reference filesA non existent reference file "{file}" was requested.The requested file does not exist on the disk. Either this was a malicious file request, or some one deleted the files on the disk manually.

E1217

TaskTaskType not valid.Check the parameter given as taskType.

E1251

Workflow Manager

Workflow to class "{className}" not found!

In the application a not existent worfklow class was requested. This is probably a programming error.

E1252

Workflow ManagerWorkflow with ID "{workflowId}" not found!There is a task configured with a not (anymore) existent workflow.

E1253

Workflow Manager{className}::$labels has to much / or missing labels!The translatable labels of the the requested workflow do not cover all or to much strings of the workflow.

E1258

Project/TaskMissing projectId parameter in the delete project request.In the delete project request the project id was not provided.

E1280

Task/UserThe segmentrange that is assigned to the user is not valid.Check input for the editable segments; must be like: "2-4,6,7-10".

Jobs (Association between Tasks and Users)

EventCodeContextEventMessageDescription / Solution

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.

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.

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.

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.

E1163

Job

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

Refresh the task overview.

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.

E1232

JobJob creation: role "lector" is deprecated, use "reviewer" instead!Please use the role "reviewer" instead!

Import

EventCodeContextEventMessageDescription / Solution

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.

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.

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.

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.

E1002

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

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.

E1004

SdlXliff Fileparser

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

Invalid SDLXIFF according to our reverse engineering.

E1005

SdlXliff Fileparser

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

Invalid SDLXIFF according to our reverse engineering.

E1006

SdlXliff Fileparser

Loading the tag information from the SDLXLIFF header has failed!

Check if SDLXLIFF header content is valid XML.

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.

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.

E1009

SdlXliff Fileparser

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

Invalid SDLXIFF according to our reverse engineering.

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.

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.

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.

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.

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.

E1077

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

E1078

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

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.

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.

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.

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.

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.

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.

E1071

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

E1194

XLF 1.2 Fileparser

The file "{file}" contains "{tag}" tags, which are currently not supported! Stop Import.

Contact the support to implement the import of the new tags.

E1195

XLF 1.2 Fileparser

A trans-unit of file "{file}" contains MRK tags other than type=seg, which are currently not supported! Stop Import.

Contact the support to implement the import of the other mrk tags.

E1196

XLF 1.2 FileparserWhitespace in text content of file "{file}" can not be cleaned by preg_replace. Error Message: "{pregMsg}". Stop Import.Check the file content for validity.

E1232

XLF 1.2 FileparserXLF Parser supports only XLIFF Version 1.1 and 1.2, but the imported xliff tag does not match that criteria: {tag}Check the file content for validity.

E1273

DisplayText XML Fileparser

The XML of the DisplayText XML file "{fileName} (id {fileId})" is invalid!

The internal XML parser can not parse the structure of the uploaded XML file, probably it is not well formed.

E1274

DisplayText XML FileparserThe DisplayText XML file "{fileName} (id {fileId})" does not contain any translation relevant segments.The uploaded XML could be parsed, but there were no Displaymessage tags containing any data.

E1275

DisplayText XML FileparserElement "Inset" with ID {id} has the invalid type {type}, only type "pixel" is supported!In "Inset" tag elements the attribute type must contain the value "pixel".

E1276

DisplayText XML FileparserElement "Len" with ID {id} has the invalid type {type}, only type "pixel" is supported!In "Len" tag elements the attribute type must contain the value "pixel".

E1277

DisplayText XML FileparserUnknown XML tags "{tag}" discovered in file "{fileName} (id {fileId})"!There were some unknown tags in the uploaded XML. This may not be a problem, but should be checked.

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.

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.

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 EventCodes#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!

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.

E1023

TBX

Parser

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

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.

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.

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.

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.

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.

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.

E1035

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

E1036

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

E1037

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

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.

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.

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.

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.

E1053

Task Import; Pixel-Mapping MetaData

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


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.

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.

E1278

Task Import; Pixel-Mapping MetaData

Segment length calculation: No pixel-width set for several characters.
Default width is used. See affected characters in extra data.


For the listed characters no width was defined, so the configured default value as fallback is used.

The missing characters are listed as unicode charpoints and the real character in parathensis.

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.

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.

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.

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.

E1190

XLF 1.2 FileparserThe XML of the XLF file "{fileName} (id {fileId})" is invalid!

The provided XLF file contains no valid XML.
See the task log, the concrete XML error should be logged there too.

E1191

XLF 1.2 FileparserThe XLF file "{fileName} (id {fileId})" does not contain any translation relevant segments.Since there are no importable segments in the file, omit the file in import.

E1193

Imported Matchrate TypeFile "{file}" contains unknown matchrate types. See details.In the mentioned file there are matchrate types not known to translate5.

E1241

DataProvider Zip

DataProvider Zip: zip file could not be opened: "{zip}"

Check if the uploaded file is a valid ZIP file.

E1242

DataProvider ZipDataProvider Zip: content from zip file could not be extracted: "{zip}"Check if the uploaded file is a valid ZIP file.

E1243

DataProvider ZipDataProvider Zip: TaskData Import Archive Zip already exists: "{target}"Remove the Archive ZIP manually.

E1244

DataProvider SingleUploadDataProvider SingleUpload: Uploaded file "{file}" cannot be moved to "{target}"Please contact the support.

E1245

DataProviderDataProvider: Could not create folder "{path}"Please contact the support.

E1246

DataProviderDataProvider: Temporary directory does already exist - path: "{path}"Remove the already existing path manually.

E1247

DataProvider DirectoryDataProvider Directory: Could not create archive-zipPlease contact the support.

E1248

DataProvider DirectoryDataProvider Directory: The importRootFolder "{importRoot}" does not exist!Create the import root folder manually.

E1249

DataProvider ZippedUrlDataProvider ZippedUrl: fetched file can not be saved to path "{path}"Check the fetched URL and the location where the file should be saved to.

E1250

DataProvider ZippedUrlDataProvider ZippedUrl: ZIP file could not be fetched from URL "{url}"Check the fetched URL.

E1265

DataProvider FactoryDataProvider Factory: The task to be cloned does not have a import archive zip! Path: {path}The task to be cloned does not have a import archive zip.

Export

EventCodeContextEventMessageDescription / Solution

E1085

Task Export

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

This is a developer issue, contact the developers.

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.

E1087

Task ExportSee E1086

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.

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.

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.

E1091

Task Export with DiffSee E1089

E1092

Task Export with DiffSee E1090

E1093

Task Export with DiffSee E1090

E1143

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

E1144

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

E1145

Task ExportCould not create export-zip.

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.

E1147

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

E1149

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

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.

E1170

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

Language Resources

EventCodeContextEventMessageDescription / Solution

E1257

Language Resources; Service

The LanguageResource-Service "{serviceType}" is not configured. Please check this confluence-page for more details: "{url}"

When adding a LanguageResource, trasnalte5 shows all LanguageResource-Services that translate5 can handle, no matter if they are already configured or not. If an unconfigured service is chosen, the user gets the info that more action is needed, including a link to a confluence-page with further details regarding that service.

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.

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.

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

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.

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

E1152

Terminology

Missing mandatory collectionId for term creation.


E1153

TerminologyMissing mandatory language (ID) for term creation.

E1154

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

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.

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.

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.

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.

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.

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.

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.

E1115

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

E1116

Terminology

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

There was probably an error on the TBX generation before.

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.

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.

E1119

TerminologyTermTagger communication Error.

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.

E1120

TerminologyTermTagger returns an error on tagging segments.

E1121

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

E1122

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

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.

E1124

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

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.

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.

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.

E1128

TerminologySee E1122.

E1240

TerminologyTermTagger TIMEOUT: The configured TermTagger "{termTaggerUrl}" did not respond in an appropriate time.

Normally everything should be OK, the considered termtagger is probably just doing its work and can not respond to another request in an appropriate time frame.

Only if this error is logged multiple times further investigations should be done.

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:

DELETE FROM `Zf_memcache` WHERE `id` = 'TermTaggerDownList';

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.

E1132

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

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.

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

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.

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.

E1259

SegmentThe data of the saved segment is not valid.See E1065, in addition that the validations contain at least an error where the lines in the segment are either too many or (at least one of them is) too long. This error is separate since it should produce an warning instead just a debug level entry.

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.

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.

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.





Segment: Search and replace

EventCodeContextEventMessageDescription / Solution

E1192

Search and replaceReplace all can not be used for task with usageMode "simultaneous"The replace all is disabled for the tasks where the task usage mode is simultaneous.

Excel Ex-Import

EventCodeContextEventMessageDescription / Solution

E1137

Task

Task can not be exported as Excel-file.


E1141

Task

Excel Reimport: upload failed.

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

E1138

Task

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


E1139

Task

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


E1140

Task

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


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.

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 reviewer is editing while another reviewer is finishing the task.

Plug-Ins

EventCodeContextEventMessageDescription / Solution

E1218

Plug-In Manager

The PHP class for the activated plug-in "{plugin}" does not exist.

Either there is a typo in the class name of the activated plug-in class, or the class does relly not exist (anymore). Perhaps it was deleted. Or the wrong translate5 package without such a plug-in was installed.

E1234

Plug-In ManagerMultiple Plugin Classes found to key {key}if some one ever traps here: search key ordered by "_" in the plugin class list (or implement something like a search tree)

E1235

Plug-InNo Plugin Configuration found!No general plug-in configuration runtimeOptions→plugins exists.

E1236

Plug-InA Plugin is missing or not active - plugin: {plugin}The mentioned plug-in is needed for another plug-in and must be activated therefore.

E1237

Plug-InThe following Plugins are not allowed to be active simultaneously: {current} and {blocked}The mentioned plug-in is needed for another plug-in and must be activated therefore.

E1238

Plug-InNo Plugin Configuration found for plugin {plugin}No specific plug-in configuration was found under runtimeOptions→plugins.

Plug-In DeepL

EventCodeContextEventMessageDescription / Solution

E1198

Plug-In DeepL

DeepL Plug-In: No config given.

Make sure that config-data for the DeepL-Plugin exists.

E1199

Plug-In DeepLDeepL Plug-In: API-Server is not defined.Make sure that DeepL's API-Server is set in the config.

E1200

Plug-In DeepLDeepL Plug-In: Authentication key is not defined.Make sure that the authentication-key from the DeepL-Account is set in the config.

Plug-In Groupshare

EventCodeContextEventMessageDescription / Solution

E1097

Plug-In GroupShare

Multi Purpose Code logging in the context of Groupshare

Multi Purpose Code logging in the context of Groupshare.

E1098

Plug-In GroupShareGroupshare Plug-In: ExceptionGeneral Purpose Exception

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.

E1214

Plug-In GroupShareNo connection to Groupshare Server: {message}There is no connection to the Groupshare Server, check added message which should contain the raw error message.

E1215

Plug-In GroupShareNo connection to Groupshare Server: {message}See E1214 above.

E1264

Plug-In GroupShareGroupShare Plug-In: retrieved data is missing or wrong.Check the result from the request.

Plug-In InstantTranslate

EventCodeContextEventMessageDescription / Solution

E1207

Plug-In InstantTranslate

InstantTranslate: Response status "{status}" in indicates failure in communication with the API.

Check the error log for further information.

E1208

Plug-In InstantTranslateInstantTranslate: parse error in JSON response, the error was: "{msg}"Check the error log for further information.

E1209

Plug-In InstantTranslateInstantTranslate: empty JSON response.Check the error log for further information.

E1211

Plug-In InstantTranslateInstantTranslate: Filetranslation failed. "{msg}"Check the error log for further information.

E1212

Plug-In InstantTranslateInstantTranslate: Parameter is not valid. "{msg}"Check the error log for further information.

E1213

Plug-In InstantTranslateInstantTranslate: Error in config or roles. "{msg}"Throws an error due to configuration-issues. Check the error log for further information.

E1233

Plug-In InstantTranslateInstantTranslate: Please check your configuration for pretranslationTaskLifetimeDays. "Adds an entry in the error-log due to configuration-issues, but doesn't stop the application. Solution: Check if pretranslationTaskLifetimeDays is set in the configuration.

Plug-In MatchAnalysis

EventCodeContextEventMessageDescription / Solution

E1100

Plug-In MatchAnalysis

Multi Purpose Code logging in the context of MatchAnalysis

Multi Purpose Code logging in the context of MatchAnalysis.

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.

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.

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.

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.

E1167

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

E1239

Plug-In MatchAnalysisMatchAnalysis Plug-In: The associated language resource "{name}" is not available for match analysis and pre-translations.The associated language resources has status different than unavailable.

Plug-In NecTm

EventCodeContextEventMessageDescription / Solution

E1162

Plug-In NecTm

NEC-TM Plug-In: Exception



E1180

Plug-In NecTm

NEC-TM Plug-In: Error



E1181

Plug-In NecTm

NEC-TM 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.

E1256

Plug-In NecTm

NEC-TM Plug-In: A new NEC-TM-LanguageResource must have at least one category assigned.

NecTm Plug-In: We should always use tags in the data uploaded, if not, the data can't be searched by users (only by admin).

E1182

Plug-In NecTm

NEC-TM Plug-In: The languages for the Nec-TM-LanguageResource differ from the languages of the segment.



E1183

Plug-In NecTm

NEC-TM Plug-In: Could not save segment to TM



Plug-In Okapi

EventCodeContextEventMessageDescription / Solution

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

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.

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

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

E1059

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

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.

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 PangeaMt

E1270

Plug-In PangeaMt

PangeaMt Plug-In: No config given.

Make sure that config-data for the PangeaMt-Plugin exists.

E1271

Plug-In PangeaMtPangeaMt Plug-In: API-Server is not defined.Make sure that PangeaMt's API-Server is set in the config.

E1272

Plug-In PangeaMtPangeaMt Plug-In: Apikey is not defined.Make sure that the apikey for your PangeaMt-access is set in the config.

Openid connect

EventCodeContextEventMessageDescription / Solution

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

E1173

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

E1174

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.

E1204

OpenidUnable to fetch the userInfo from the defined userinfo_endpoint.The userinfo_endpoint request to the openid provider is not possible or the request was empty.

FrontEndMessageBus

EventCodeContextEventMessageDescription / Solution

E1175

Plug-In FrontEndMessageBus

FrontEndMessageBus: Missing configuration - runtimeOptions.plugins.FrontEndMessageBus.messageBusURI must be set in configuration.

Set the missing messageBusURI configuration:
Message Bus URI, change default value according to your needs (as configured in config.php of used FrontEndMessageBus). Unix sockets are also possible, example: unix:///tmp/translate5MessageBus

E1176

Plug-In FrontEndMessageBus

FrontEndMessageBus: Response status "{status}" in indicates failure in communication with message bus.

Check the error log of the Message Bus server for further information.

E1177

Plug-In FrontEndMessageBusFrontEndMessageBus: parse error in JSON response, the error was: "{msg}"Check the error log of the Message Bus server for further information.

E1178

Plug-In FrontEndMessageBusFrontEndMessageBus: empty JSON response.Check the error log of the Message Bus server for further information.

Plug-In VisualReview 

EventCodeContextEventMessageDescription / Solution

E1184

Plug-In VisualReview

VisualReview Plug-In: Missing visual review resource. {resources}

Required resource executable does not exist on the current installation. The event message will log the missing config. check the error log for more information.

E1185

Plug-In VisualReviewVisualReview Plug-In: Fail on merging the submitted pdf file(s). Command {command}; Output: {shellOutput}The command line tool for pdf merge (currently pdfunite) was not able to merge the given pdf file(s).

E1186

Plug-In VisualReviewPlugin Visual Review failed on transforming the pdf to a html fileFail on transform the merged PDF-file to a html file. This job will be done by pdf2htmlEX.

E1187

Plug-In VisualReviewCant find config variable (or variable is empty): runtimeOptions.plugins.VisualReview.shellCommandPdfMergeThe configured path to the command line tool "pdfMerge" (currently pdfunite) is not valid/provided.

E1188

Plug-In VisualReviewCant find config variable (or variable is empty): runtimeOptions.plugins.VisualReview.shellCommandPdf2HtmlThe configured path to the command line tool "pdf2htmlEx" is not valid/provided.

E1189

Plug-In VisualReviewVisualReview Plug-In: Fail on segmentation of the html fileThe segmentation of the html file failed. For more info check the error log.

E1197

Plug-In VisualReviewVisualReview Plug-In: segmentation result: {percentage}% ({segmentFoundCount} / {segmentCount})Just a info about the percentage how many segments could be found in the PDF.

E1226

Plug-In VisualReviewCant find config variable (or variable is empty): runtimeOptions.plugins.VisualReview.shellCommandPdfOptimizerThe shell command for the PDF-Optimizer is not defined or empty

E1227

Plug-In VisualReviewCant find config variable (or variable is empty): runtimeOptions.plugins.VisualReview.shellCommandGoogleChromeThe shell command for Google Chrome is not defined or empty

E1228

Plug-In VisualReviewUnable to optimize the pdf using the {command} shell commandThe optimization of the PDF failed

E1229

Plug-In VisualReviewVisual Review Worker Initialization failed: {reason}

The Initialization of the specified Worker failed

E1230

Plug-In VisualReviewVisual Review Text-Reflow: Transformation of HTML generated with pdf2htmlEx failed: {reason}The Text-Reflow of the pdf2htmlEx output failed (so the output is used without Live-Editing)

E1231

Plug-In VisualReviewVisual Review Text-Reflow: Transformation of HTML generated with pdf2htmlEx had problems: {reason}The Text-Reflow of the pdf2htmlEx output had problems (though it's output is used as review ignoring the problems)

E1254

Plug-In VisualReviewVisual Review Font-Replacing: The replacing of fonts in the HTML generated with pdf2htmlEx failed: {reason}The Font-Replacing in the pdf2htmlEx output failed and no fonts have been replaced. The Live-Editing for this task now may has unsolvable problems with mis-styled or even missing characters when translating

E1255

Plug-In VisualReviewVisual Review Font-Replacing: Some fonts were not found and need to be added: {list}The Font-Replacing in the pdf2htmlEx output found fonts that are not present in the Font-admnistration and need to be added there

E1260

Plug-In VisualReviewVisualReview: No review files have been imported successfully, the visual review is disabledThe Import contained sources for a visual review but none of them could successfully be transformed to a review HTML

E1261

Plug-In VisualReviewVisualReview Download: The submitted URL could not be fetched: {reason}The User submitted a syntactically correct URL as review source but it could not be downloaded with wget

E1262

Plug-In VisualReviewVisualReview Download: An error occurred downloading the submitted URL: {reason}The URL submitted by the User could not be downloaded with wget

E1263

Plug-In VisualReviewVisualReview Download: An error occurred processing the submitted URL: {reason}The URL submitted by the User could not be processed

E1279

Plug-In VisualReviewVisualReview XML/XSL Import: An error occurred processing the imported XML/XSL: {reason}The imported XML/XSLT file had errors while processing them to create the visual review

Plug-In ModelFront 

EventCodeContextEventMessageDescription / Solution

E1266

ModelFront

ModelFront Plug-In: authentication parametars are not defined.

The apiUpr or apiToken zf_configuration parameters are not defined or empty.

E1267

ModelFrontModelFront Plug-In: source or target languages are not defined.The source or target languages are not set.

E1268

ModelFrontModelFront Plug-In: Error on ModelFront api request. The error was: {message}.Error happen on model front api request. For more info see the error log.

E1269

ModelFrontModelFront Plug-In: Error on processing the segments. Segment list with errors: {errors}.ModelFront api responds with error for the requested segment. For more info about the error check the error log.

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.

  • No labels