Page tree

Versions Compared

Key

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

...

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.

Anchor
E1205
E1205
E1205

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

Anchor
E1206
E1206
E1206

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

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

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

Anchor
E1217
E1217
E1217

TaskTaskType not valid.Check the parameter given as taskType.

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

Anchor
E1252
E1252
E1252

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

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

Anchor
E1258
E1258
E1258

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

Anchor
E1280
E1280
E1280

Task/UserThe format of the segmentrange that is assigned to the user is not valid. Example: 1-3,5,8-9Check the input for the editable segments; must be like: "1-3,5,8-9".

Anchor
E1281
E1281
E1281

Task/UserThe content of the segmentrange that is assigned to the user is not valid.Make sure that the values are not reverse and do not overlap (neither in itself nor with other users of the same role).

Anchor
E1339
E1339
E1339

TaskMissing mandatory parameter taskGuid.The taskGuid is not provided as request parameter.

Anchor
E1341
E1341
E1341

TaskYou tried to open or edit another task, but you have already opened another one in another window. Please press F5 to open the previous one here, or close this message to stay in the Taskoverview.Only one task can be opened for editing per user. If if the user has already opened a task for editing, he/she is not able to modify tasks in task overview with different browser tab. In short words, please use only one browser tab.

Anchor
E1348
E1348
E1348

Task materialized viewThe tasks materialized view was created.Debugging information to trace the creation of a tasks materialiazed view.

Anchor
E1349
E1349
E1349

Task materialized viewThe tasks materialized view was dropped.Debugging information to trace the deletion of a tasks materialiazed view.

Anchor
E1381
E1381
E1381

Current TaskAccess to CurrentTask was requested but no task ID was given in the URL.Development error: Some PHP code tried to load the currently opened task (identified by the taskid given in the URL) but no task ID was provided in the URL. So either the URL producing the request is wrongly created (no Editor.data.restpath prefix), or its just the wrong context where the CurrentTask was accessed.

Anchor
E1382
E1382
E1382

Current TaskAccess to CurrentTask was requested but it was NOT initialized yet.Development error: Some PHP code tried to access the currently opened task but it was not loaded yet. This can be done calling TaskContextTrait::initCurrentTask.

Anchor
E1395
E1395
E1395

Task-OperationThe Task-Operation "{operation}" can not be started when the task is in state "{taskstate}"The Task-Operation can not be started if the task is in the given state

Anchor
E1396
E1396
E1396

Task-OperationThe Task-Operation "{operation}" can not be started, there is already an operation runningAnother User may already started an operation for the task and therefore this operation has to be finished before another operation is started. Try again after the running operation has finished.

Project

EventCodeContextEventMessageDescription / Solution

Anchor
E1284
E1284
E1284

Project

Projects are not editable.

For task with task-type project the task put action is not allowed.

...

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

SdlXliff FileparserThe file "{filename}" did not contain any translation relevant content. Either all segments are set to translate="no" or the file was not segmented.Either all segments in the SDLXLIFF are set to translate=no or no trans-unit contains segmented content.
Studio is segmenting the source content only if the pre-translation was used or at least one segment was opened, edited and saved there.

Anchor
E1322
E1322
E1322

SdlXliff FileparserA CXT tag type x-tm-length-info with a unknown prop type "{propType}" was found.The provided CXT tag of type x-tm-length-info did contain an unknown value in the prop > value tag with attribtute key = 'length_type'.

Anchor
E1323
E1323
E1323

SdlXliff FileparserThe transUnit contains sdl:cxt tags, but we assume that tags only in the group tag!According to our reverse engineering we have seen the sdl:cxt tag only in the group tag surrounding a transUnit tag but never in the transUnit tag directly. If that ever happen we have to implement that usage form.

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

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

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

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

Anchor
E1363
E1363
E1363

XLF 1.2 FileparserUnknown XLF tag found: {tag} - can not import that.The listed tag is not known in XLF, therefore it can not be imported. Get in contact with the support.

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

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

Anchor
E1275
E1275
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".

Anchor
E1276
E1276
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".

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

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 "{workfiles}" folder.

The uploaded ZIP package did not contain a "workfiles" 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 "{workfiles}" folder.The "workfiles" 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
E1325
E1325
E1325

Task Import; Task-config templateSomething went wrong when loading task config template with name: {filename}. The error was:{errorMessage}Error happened when the config template is being parsed or the parsed configs are saved as task specific configs

Anchor
E1327
E1327
E1327

Task Import; Task-config template

The config value {name} given in the task-config.ini does not exist in the main configuration and is ignored therefore.


Check the config name, change it or remove it from the task-config.ini

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

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.

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

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

Anchor
E1193
E1193
E1193

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

Anchor
E1241
E1241
E1241

DataProvider Zip

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

Check if the uploaded file is a valid ZIP file.

Anchor
E1242
E1242
E1242

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

Anchor
E1243
E1243
E1243

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

Anchor
E1244
E1244
E1244

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

Anchor
E1245
E1245
E1245

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

Anchor
E1246
E1246
E1246

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

Anchor
E1247
E1247
E1247

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

Anchor
E1248
E1248
E1248

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

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

Anchor
E1250
E1250
E1250

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

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

Anchor
E1338
E1338
E1338

Task ImportIMPORTANT: The "proofRead" folder in the zip import package is deprecated from now on. In the future please always use the new folder "workfiles" instead. All files that need to be reviewed or translated will have to be placed in the new folder "workfiles" from now on. In some future version of translate5 the support for "proofRead" folder will be completely removed. Currently it still is supported, but will write a "deprecated" message to the php error-log.The proofRead folder name in the task import zip package should be no longer used. Please use workfiles instead.

Anchor
E1369
E1369
E1369

DataProvider Project
DataProvider Project: No matching work-files where found for the task.
No matching work files were found for the currently processed task upload. This can happen when for the current task there is no matching language or filetype provided in the request parameters.

Anchor
E1372
E1372
E1372

DataProvider Zip
DataProvider Zip: Uploaded zip file "{file}" cannot be moved to "{target}
Unable to copy the zip file to the target location.

Anchor
E1378
E1378
E1378

Task Import Callback

The task import callback HTTP status code is {code} instead 200.


See extra data for complete result.

Anchor
E1379
E1379
E1379

Task Import

The task import was cancelled after {hours} hours.


Normally this happens only if the import it self was either crashed in a very unusal way or the server was restarted while import.

Anchor
E1384
E1384
E1384

DataProvider Project

DataProvider Project: Maximum number of allowable file uploads has been exceeded.


The number of uploaded files is over the defined limit in php. Increase max_file_uploads php configuration to allow more files to be uploaded.

...

Anchor

EventCode

E1394

Context

E1394

EventMessageDescription / Solution AnchorE1085E1085E1085

E1394

All finish of a role Callback

All finish of a role callback HTTP status code is {code} instead 200.


The configured callback when all users are finishing the role does return different HTTP status then 200. See extra data for more info.

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.

...

EventCodeContextEventMessageDescription / Solution

Anchor
E1257
E1257
E1257

Language Resources; Service

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

When adding a LanguageResource, translate5 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.

Anchor
E1316
E1316
E1316

Language Resources; Service

The previously configured LanguageResource-Service "{service}" is not available anymore.


This errors happens, if a language resource was configured and associated to a task, and after that the configuration (the URL to the server) was removed again.

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

Anchor
E1282
E1282
E1282

Language Resources; Service;

Connector

Language resource communication error.General language resources error. It can happend when segment pre-translation is requested, general task pre-translation or instant-translate search. For more info check the error log,

Anchor
E1311
E1311
E1311

Language ResourcesCould not connect to language resource {service}: server not reachableThe server of the language resource is not reachable. This means that the server/service is not running, there is a network problem, or the service is not configured properly.

Anchor
E1312
E1312
E1312

Language ResourcesCould not connect to language resource {service}: timeout on connection to serverThe server of the language resource is not reachable in a determined time span. This means that the server/service may be running but is not able to accept new connections.

Anchor
E1313
E1313
E1313

Language Resources

The queried language resource {service} returns an error.

See the error log for more details about the error.

Anchor
E1370
E1370
E1370

Language Resources

Empty response from language resource {service}

The service could be queried but returns an empty response, there is probably an error with the service.

Anchor
E1315
E1315
E1315

Language ResourcesJSON decode error: {errorMsg}The result of the language resource was invalid.

Anchor
E1288
E1288
E1288

Language Resources; Resource languages;

The language code [{languageCode}] from resource [{resourceName}] is not valid or does not exist in the translate5 language code collection.

The language code received from the remote resource was not found(does not exist) in translate5 languages code collection.

Anchor
E1300
E1300
E1300

Language ResourcesThe LanguageResource answer did contain additional tags which were added to the segment, starting with Tag Nr {nr}.The answer of the language resource did contain more tags as available in the source text.

Anchor
E1301
E1301
E1301

Language ResourcesThe LanguageResource answer did contain it|ph|ept|bpt tags, which are removed since they can not be handled.The language resource returned some <it> <ph> <ept> or <bpt> tag, which can not be handled here. So the tag with its content was removed.

Anchor
E1302
E1302
E1302

Language ResourcesThe LanguageResource did contain invalid XML, all tags are getting removed. See also previous InvalidXMLException in Log.

The language resource returned invalid XML, all tags were removed. The user has to add the missing source tags manually on reviewing the pretranslated content.

Anchor
E1397
E1397
E1397

Language Resources: pivot pre-translationPivot pre-translation: task can not be locked for pivot pre-translation.The task was locked by another process, so no pivot pre-translation is possible.

Anchor
E1303
E1303
E1303

Language Resource OpenTM2OpenTM2: could not add TMX data to TMThe uploaded TMX could not be added to the TM, see error details for more information.

Anchor
E1304
E1304
E1304

Language Resource OpenTM2OpenTM2: could not create prefilled TMThe uploaded TM could not be used as new TM, see error details for more information.

Anchor
E1305
E1305
E1305

Language Resource OpenTM2OpenTM2: could not create TMThe TM could not be created, see error details for more information.

Anchor
E1306
E1306
E1306

Language Resource OpenTM2OpenTM2: could not save segment to TMA segment in the TM could not be updated, see error details for more information.

Anchor
E1314
E1314
E1314

Language Resource OpenTM2The queried OpenTM2 TM "{tm}" is corrupt and must be reorganized before usage!The mentioned TM must be reorganized via the OpenTM2 GUI. See the error log details for the affected server and the TM ID used on the server.

Anchor
E1333
E1333
E1333

Language Resource OpenTM2The queried OpenTM2 server has to many open TMs.

Something was going wrong with the internal garbage cleaning and TM closing of OpenTM2.

If this error persists, the OpenTM2 service should be restarted.

Anchor
E1377
E1377
E1377

Language Resource OpenTM2OpenTM2: Unable to use the memory because of the memory status {status}. After 20 seconds of waiting, the memory status is still not "available" which makes this memory not usable.

Anchor
E1319
E1319
E1319

Language Resource Google TranslateGoogle Translate authorization failed. Please supply a valid API Key.The configured API Key is not valid.

Anchor
E1320
E1320
E1320

Language Resource Google TranslateGoogle Translate quota exceeded. The character limit has been reached.The usage quota of your Google Translate account is exceeded.

Anchor
E1321
E1321
E1321

Language Resource Term CollectionTerm Collection Import: Errors on parsing the TBX, the file could not be imported.See the log for additional errors on importing the TBX file.

Anchor
E1335
E1335
E1335

Language resource: resources usage exportUnable to create export zip archive {path}.Unable to create export zip archive. For more info see the error log.

Anchor
E1335
E1335
E1336

Language resource: resources usage exportUnable to close the export zip archive {path}.Unable to close export zip archive. For more info see the error log.

Anchor
E1344
E1344
E1344

Language Resource Microsoft Translator

Microsoft Translator returns an error: {errorNr} - {message}


See the error message from Microsoft Translator to find out what is wrong.

Anchor
E1345
E1345
E1345

Language Resource Microsoft TranslatorCould not authorize to Microsoft Translator, check your configured credentials.Validate your Microsoft Translator API configuration. Ensure that apiUrl, apiKey and apiLocation are configured to the same values as in your azure configuration.

Anchor
E1346
E1346
E1346

Language Resource Microsoft TranslatorMicrosoft Translator quota exceeded. A limit has been reached.See the error log for details.

Anchor
E1358
E1358

E1358

Language Resource Term CollectionTerm Collection Import: Unable to open zip file from file-path: {filePath}See the error log for details.

Anchor
E1359
E1359
E1359

Language Resource Term CollectionTerm Collection Import: Content from zip file could not be extracted.See the error log for details.

...

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

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.

Anchor
E1326
E1326
E1326

TerminologyTermTagger can not work when source and target language are equal.The task's source and target language are equal. This makes it impossible to use the TermTagger causing a hang otherwise.

Anchor
E1353
E1353
E1353

TerminologyTBX Import: Folder to save images does not exist or is not writable!
See details to get the folder which was tried to be used. This folder does either not exist or is not writable by the apache.

Anchor
E1354
E1354
E1354

TerminologyTBX Import: Folder to save termcollection images could not be created!See details to get the folder which was tried to be used. This folder does either not exist or is not writable by the apache.

Anchor
E1356
E1356
E1356

TerminologyTBX Import: Import error - {msg}Very unusual that this error happens, see the msg and extra data.

Anchor
E1357
E1357
E1357

TerminologyTBX Import: Could not import due unknown attribute levelVery unusual that this error happens, see the msg and extra data.

Anchor
E1393
E1393
E1393

TerminologyTBX Import: The XML structure of the TBX file is invalid: {message}In this case the XML of the given TBX file is invalid and can not be parsed.

Anchor
E1360
E1360
E1360

TerminologyTBX Import: The TBX contains terms with unknown administrative / normative states. See details for a list of states.

The listed states are unknown and can not be mapped to the usual administrative status values.

Please configure them in the runtimeOptions.tbx.termImportMap configuration.

Anchor
E1361
E1361
E1361

TerminologyTBX Import: Unable to import terms due invalid Rfc5646 language code "{code}"The listed language code is invalid / not configured in translate5, the corresponding terms could not be imported.

Anchor
E1364
E1364
E1364

Terminology

TermTagger overall run done - {segmentCounts}


Reports that the whole task was tagged with the termtagger and shows the segment status counts.

...

EventCodeContextEventMessageDescription / Solution

Anchor
E1343
E1343
E1343

Quality processing on Task Import or Segment editingSetting the FieldTags tags by text led to a changed text-content presumably because the encoded tags have been improperly processedCreate a ticket for this issue with the event added.

Anchor
E1391
E1391
E1391

Quality processing on Task Import or Segment editingTwo non-splittable tags interleave each other.Create a ticket for this issue with the event added.

Anchor
E1392
E1392
E1392

Quality processing on Task Import or Segment editingSNC lib (which stands behind AutoQA Numbers Check) detected an error of a kind previously unknown to translate5 appCreate a ticket for this issue with the event added.

Excel Ex-Import

...