| ErrorCode | Context | ErrorMessage | Description / Solution |
|---|
 E1000
| SdlXliff Fileparser | The 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. |
 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 Fileparser | Found 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}"!
Please clear them first and then try to check in the file again. | SDLXLIFF change markup is not supported. |
 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 Fileparser | The 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 Fileparser | The 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. |
 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 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! |
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 exception/info produced while the tbx parser is running. |
 E1031
| Task Import - File Upload | A 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 Import | The 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 Import | The 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 Import | The given taskGuid "{taskGuid}" was not valid GUID. | Please provide a valid GUID. |
 E1036
| Task Import | The given userGuid "{userGuid}" was not valid GUID. | Please provide a valid GUID. |
 E1037
| Task Import | The given userName "{userName}" was not valid user name. | Please provide a valid username. |
 E1038
| Task Import | The 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 Import | The 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 Import | The 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 Import | TODO 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 MetaData | Pixel-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. |
 E1060
| Task Import | For 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. |