Page tree

Versions Compared

Key

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

...

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

EventCodeContextErrorMessageDescription / 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.


Users & Customers

EventCodeContextErrorMessageDescription / 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.




Task & Workflow

EventCodeContextErrorMessageDescription / 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.

Jobs (Association between Tasks and Users)

EventCodeContextErrorMessageDescription / 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.

Import

ErrorCodeContextErrorMessageDescription / Solution

Anchor
E1000
E1000
E1000

SdlXliff FileparserThe file "{filename}" contains SDL comments which are currently not supported!

Since "{filename}" can not be imported, 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}"!
Please clear them first and then try to check in the file again.

SDLXLIFF change markup is not supported.

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
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 Error- and EventCodes ErrorCodes, 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
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 exception/info produced while the tbx parser is running.

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

Language Resources

EventCodeContextErrorMessageDescription / 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.

Segment

EventCodeContextErrorMessageDescription / 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.

Plug-Ins

Plug-In Okapi

EventCodeContextErrorMessageDescription / 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}. 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.

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:

ErrorCode 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 error codes: make life easier for support / help desk.