...
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Task; Workflow | Multi Purpose Code logging in the context of a task | Multi Purpose code for several info logs around a task. Also important in Context of workflow. | ||||||
| Job; Workflow | Multi Purpose Code logging in the context of jobs (task user association) | Multi Purpose Code logging in the context of jobs (task user association) | ||||||
| Workflow only | Multi Purpose Code logging in the context of pure workflow processing | Multi Purpose Code logging in the context of workflow processing | ||||||
| Task | The 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. | ||||||
| Task | The 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. | ||||||
| Task | The 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. | ||||||
| Task; ManualStatusCheck Plug-In | The 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. | ||||||
| Task | The current task status does not allow that action. | This error occurs if the current status of the task does not allow the triggering action. | ||||||
| Task; ArchiveTaskBeforeDelete Plug-In | Task 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. | ||||||
| Task | The 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. | ||||||
| Task | Task 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. | ||||||
| Workflow only | Workflow 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. | ||||||
| Workflow User Preferences | The referenced user is not associated to the task or does event not exist anymore. | Reload the task properties. | ||||||
| Workflow User Preferences | Missing workflow step in given data. | Missing workflow step in given data. | ||||||
| Workflow User Preferences | Missing workflow step in given data. | Missing workflow step in given data. | ||||||
| Task; Workflow | The 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. | ||||||
| Task reference files | A 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. | ||||||
| Task | TaskType not valid. | Check the parameter given as taskType. | ||||||
| Workflow Manager | Workflow to class "{className}" not found! | In the application a not existent worfklow class was requested. This is probably a programming error. | ||||||
| Workflow Manager | Workflow with ID "{workflowId}" not found! | There is a task configured with a not (anymore) existent workflow. | ||||||
| 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. | ||||||
| Project/Task | Missing projectId parameter in the delete project request. | In the delete project request the project id was not provided. | ||||||
| Task/User | The format of the segmentrange that is assigned to the user is not valid. Example: 1-3,5,8-9 | Check the input for the editable segments; must be like: "1-3,5,8-9". | ||||||
| Task/User | The 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). | ||||||
| Task | Missing mandatory parameter taskGuid. | The taskGuid is not provided as request parameter. | ||||||
| Task | You 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. | ||||||
| Task materialized view | The tasks materialized view was created. | Debugging information to trace the creation of a tasks materialiazed view. | ||||||
| Task materialized view | The tasks materialized view was dropped. | Debugging information to trace the deletion of a tasks materialiazed view. | ||||||
| Current Task | Access 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. | ||||||
| Current Task | Access 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. | ||||||
| Task-Operation | The 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 | ||||||
| Task-Operation | The Task-Operation "{operation}" can not be started, there is already an operation running | Another 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
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Project | Projects are not editable. | For task with task-type project the task put action is not allowed. |
...
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Fileparser | The 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. | ||||||
| Fileparser | Given 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. | ||||||
| SdlXliff Fileparser | The 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. | ||||||
| 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. | ||||||
| SdlXliff Fileparser | Found a closing tag without an opening one. Segment MID: "{mid}". | Invalid XML structure in the mentioned SDLXLIFF file. | ||||||
| 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. | ||||||
| SdlXliff Fileparser | Locked-tag-content was requested but tag does not contain a xid attribute. | Invalid SDLXIFF according to our reverse engineering. | ||||||
| SdlXliff Fileparser | <sdl:seg-defs was not found in the current transunit: "{transunit}" | Invalid SDLXIFF according to our reverse engineering. | ||||||
| SdlXliff Fileparser | Loading the tag information from the SDLXLIFF header has failed! | Check if SDLXLIFF header content is valid XML. | ||||||
| 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. | ||||||
| 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. | ||||||
| SdlXliff Fileparser | The source and target segment count does not match in transunit: "{transunit}". | Invalid SDLXIFF according to our reverse engineering. | ||||||
| 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. | ||||||
| SdlXliff Fileparser | The 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. | ||||||
| SdlXliff Fileparser | A 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'. | ||||||
| SdlXliff Fileparser | The 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. | ||||||
| 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. | ||||||
| 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. | ||||||
| CSV Fileparser | Error 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. | ||||||
| CSV Fileparser | In 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. | ||||||
| CSV Fileparser | No linebreak found in CSV: {file} | No valid line break(s) were found in the CSV, does it contain only one line? | ||||||
| CSV Fileparser | No header column found in CSV: "{file}" | No header columns could be found, check the CSV content. | ||||||
| CSV Fileparser | In 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. | ||||||
| CSV Fileparser | Source 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. | ||||||
| XLF 1.2 Fileparser | MRK/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. | ||||||
| XLF 1.2 Fileparser | MRK/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. | ||||||
| XLF 1.2 Fileparser | There 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. | ||||||
| XLF 1.2 Fileparser | SUB 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. | ||||||
| XLF 1.2 Fileparser | MRK tag of {field} has no MID attribute. | The given MRK tag does not contain a MID attribute. | ||||||
| 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. | ||||||
| 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. | ||||||
| XLF 1.2 Fileparser | Whitespace in text content of file "{file}" can not be cleaned by preg_replace. Error Message: "{pregMsg}". Stop Import. | Check the file content for validity. | ||||||
| XLF 1.2 Fileparser | XLF 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. | ||||||
| XLF 1.2 Fileparser | Unknown 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. | ||||||
| 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. | ||||||
| DisplayText XML Fileparser | The 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. | ||||||
| DisplayText XML Fileparser | Element "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". | ||||||
| DisplayText XML Fileparser | Element "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". | ||||||
| DisplayText XML Fileparser | Unknown 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. | ||||||
| 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. | ||||||
| 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. | ||||||
| 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! | ||||||
| Relais Import | Task 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. | ||||||
| TBX Parser | Unable to read the provided tbx file {filename} | The provided file for parsing can is not readable. | ||||||
| XML Parser | Invalid XML: expected closing "{closingTag}" tag, but got tag "{receivedTag}". Opening tag was: {openingTag} | Invalid xml chunk found while parsing xml file. | ||||||
| TBX Parser | {message}. \n Term collection name: {name} | Log the term collection exception/info produced while the tbx parser is running for the term. | ||||||
| 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. | ||||||
| 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. | ||||||
| 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. | ||||||
| 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. | ||||||
| Task Import | The given taskGuid "{taskGuid}" was not valid GUID. | Please provide a valid GUID. | ||||||
| Task Import | The given userGuid "{userGuid}" was not valid GUID. | Please provide a valid GUID. | ||||||
| Task Import | The given userName "{userName}" was not valid user name. | Please provide a valid username. | ||||||
| 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. | ||||||
| Task Import | The 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. | ||||||
| Task Import | The 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. | ||||||
| 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. | ||||||
| Task Import; Task-config template | Something 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 | ||||||
| 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 | ||||||
| Task Import; Pixel-Mapping MetaData | Pixel-Mapping: Import failed due not found customer specified by customer number in excel - client nr: {lastClientNr} | |||||||
| 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. | ||||||
| Task Import; Pixel-Mapping MetaData | Pixel-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. | ||||||
| Task Import; Pixel-Mapping MetaData | Segment length calculation: No pixel-width set for several characters. | 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. | ||||||
| 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. | ||||||
| Task Import | There 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. | ||||||
| Task Import | Some 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. | ||||||
| Task Import | Although 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. | ||||||
| XLF 1.2 Fileparser | The XML of the XLF file "{fileName} (id {fileId})" is invalid! | The provided XLF file contains no valid XML. | ||||||
| XLF 1.2 Fileparser | The 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. | ||||||
| Imported Matchrate Type | File "{file}" contains unknown matchrate types. See details. | In the mentioned file there are matchrate types not known to translate5. | ||||||
| DataProvider Zip | DataProvider Zip: zip file could not be opened: "{zip}" | Check if the uploaded file is a valid ZIP file. | ||||||
| DataProvider Zip | DataProvider Zip: content from zip file could not be extracted: "{zip}" | Check if the uploaded file is a valid ZIP file. | ||||||
| DataProvider Zip | DataProvider Zip: TaskData Import Archive Zip already exists: "{target}" | Remove the Archive ZIP manually. | ||||||
| DataProvider SingleUpload | DataProvider SingleUpload: Uploaded file "{file}" cannot be moved to "{target}" | Please contact the support. | ||||||
| DataProvider | DataProvider: Could not create folder "{path}" | Please contact the support. | ||||||
| DataProvider | DataProvider: Temporary directory does already exist - path: "{path}" | Remove the already existing path manually. | ||||||
| DataProvider Directory | DataProvider Directory: Could not create archive-zip | Please contact the support. | ||||||
| DataProvider Directory | DataProvider Directory: The importRootFolder "{importRoot}" does not exist! | Create the import root folder manually. | ||||||
| DataProvider ZippedUrl | DataProvider ZippedUrl: fetched file can not be saved to path "{path}" | Check the fetched URL and the location where the file should be saved to. | ||||||
| DataProvider ZippedUrl | DataProvider ZippedUrl: ZIP file could not be fetched from URL "{url}" | Check the fetched URL. | ||||||
| DataProvider Factory | DataProvider 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. | ||||||
| Task Import | IMPORTANT: 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. | ||||||
| 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. | ||||||
| DataProvider Zip | DataProvider Zip: Uploaded zip file "{file}" cannot be moved to "{target} | Unable to copy the zip file to the target location. | ||||||
| Task Import Callback | The task import callback HTTP status code is {code} instead 200. | See extra data for complete result. | ||||||
| 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. | ||||||
| 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. |
...
|
|
|
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
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Task Export | this->_classNameDifftagger must be defined in the child class. | This is a developer issue, contact the developers. | ||||||
| Tsk Export | Error 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. | ||||||
| Task Export | See E1086 | |||||||
| Task Export | Error 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. | ||||||
| Task Export with Diff | Tag 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. | ||||||
| Task Export with Diff | The number of opening and closing g-Tags had not been the same! The Segment had been: "{segment}" | Similar to E1089. | ||||||
| Task Export with Diff | See E1089 | |||||||
| Task Export with Diff | See E1090 | |||||||
| Task Export with Diff | See E1090 | |||||||
| Task Export | ExportedWorker: No Parameter "zipFile" given for worker. | This is an implementantion error. | ||||||
| Task Export | ExportedWorker: No Parameter "folderToBeZipped" given for worker. | This is an implementantion error. | ||||||
| Task Export | Could not create export-zip. | |||||||
| Task Export | The 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. | ||||||
| Task Export | The task export folder does not exist or is not writeable, no export ZIP file can be created. | See E1146. | ||||||
| Task Export | Export: Some segments contains tag errors. | See error details for affected segments and details. | ||||||
| Task Export | Export: the file "{file}" could not be exported, since had possibly already errors on import. | See error details for affected file and details. | ||||||
| Task Metadata Export | The Metadata of the currently filtered tasks can not be exported as Excel-file. |
...
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| 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. | ||||||
| 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. | ||||||
| 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. | ||||||
| Language Resources; Task | Cannot 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. | ||||||
| Language Resources | Given 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). | ||||||
| Language Resources | A Language Resources cannot be deleted as long as tasks are assigned to this Language Resource. | Remove all tasks first from that resource. | ||||||
| Language Resources | The task is in use and cannot be reimported into the associated language resources. | Check who or what process is locking the task | ||||||
| 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, | ||||||
| Language Resources | Could not connect to language resource {service}: server not reachable | The 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. | ||||||
| Language Resources | Could not connect to language resource {service}: timeout on connection to server | The 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. | ||||||
| Language Resources | The queried language resource {service} returns an error. | See the error log for more details about the error. | ||||||
| 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. | ||||||
| Language Resources | JSON decode error: {errorMsg} | The result of the language resource was invalid. | ||||||
| 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. | ||||||
| Language Resources | The 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. | ||||||
| Language Resources | The 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. | ||||||
| Language Resources | The 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. | ||||||
| Language Resources: pivot pre-translation | Pivot 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. | ||||||
| Language Resource OpenTM2 | OpenTM2: could not add TMX data to TMThe uploaded TMX could not be added to the TM, see error details for more information. | |||||||
| Language Resource OpenTM2 | OpenTM2: could not create prefilled TM | The uploaded TM could not be used as new TM, see error details for more information. | ||||||
| Language Resource OpenTM2 | OpenTM2: could not create TM | The TM could not be created, see error details for more information. | ||||||
| Language Resource OpenTM2 | OpenTM2: could not save segment to TM | A segment in the TM could not be updated, see error details for more information. | ||||||
| Language Resource OpenTM2 | The 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. | ||||||
| Language Resource OpenTM2 | The 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. | ||||||
| Language Resource OpenTM2 | OpenTM2: 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. | ||||||
| Language Resource Google Translate | Google Translate authorization failed. Please supply a valid API Key. | The configured API Key is not valid. | ||||||
| Language Resource Google Translate | Google Translate quota exceeded. The character limit has been reached. | The usage quota of your Google Translate account is exceeded. | ||||||
| Language Resource Term Collection | Term Collection Import: Errors on parsing the TBX, the file could not be imported. | See the log for additional errors on importing the TBX file. | ||||||
| Language resource: resources usage export | Unable to create export zip archive {path}. | Unable to create export zip archive. For more info see the error log. | ||||||
| Language resource: resources usage export | Unable to close the export zip archive {path}. | Unable to close export zip archive. For more info see the error log. | ||||||
| Language Resource Microsoft Translator | Microsoft Translator returns an error: {errorNr} - {message} | See the error message from Microsoft Translator to find out what is wrong. | ||||||
| Language Resource Microsoft Translator | Could 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. | ||||||
| Language Resource Microsoft Translator | Microsoft Translator quota exceeded. A limit has been reached. | See the error log for details. | ||||||
E1358 | Language Resource Term Collection | Term Collection Import: Unable to open zip file from file-path: {filePath} | See the error log for details. | ||||||
| Language Resource Term Collection | Term Collection Import: Content from zip file could not be extracted. | See the error log for details. |
...
| EventCode | Context | EventMessage | Description / Solution | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Terminology | Missing mandatory collectionId for term creation. | ||||||||||||
| Terminology | Missing mandatory language (ID) for term creation. | ||||||||||||
| Terminology | GroupId was set explicitly, this is not allowed. Must be set implicit via a given termEntryId. | ||||||||||||
| 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. | |||||||||||
| Terminology | There 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. | |||||||||||
| 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. | |||||||||||
| Terminology | There 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. | |||||||||||
| Terminology | The 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. | |||||||||||
| Terminology | No 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. | |||||||||||
| 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. | |||||||||||
| Terminology | Collected terms could not be converted to XML. | Internal SimpleXML error. | |||||||||||
| Terminology | Could not load TBX into TermTagger: TBX hash is empty. | There was probably an error on the TBX generation before. | |||||||||||
| Terminology | Could 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. | |||||||||||
| Terminology | Could 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. | |||||||||||
| Terminology | TermTagger communication Error. | ||||||||||||
| Terminology | TermTagger 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. | |||||||||||
| Terminology | TermTagger returns an error on tagging segments. | ||||||||||||
| Terminology | TermTagger result could not be decoded. | Look also for a directly following E1133 or E1134 in the log. | |||||||||||
| Terminology | TermTaggerImport Worker can not be initialized! | Some error happened on worker initialization, check logged parameters. | |||||||||||
| Terminology | Some 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. | |||||||||||
| Terminology | Parameter validation failed, missing serverCommunication object. | Happens on live termtagging on segment editing only. | |||||||||||
| Terminology | TermTagger 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. | |||||||||||
| 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. | |||||||||||
| 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. | |||||||||||
| Terminology | See E1122. | ||||||||||||
| Terminology | TermTagger 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. | |||||||||||
| Terminology | TermTagger 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:
| |||||||||||
| Terminology | TermTagger 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. | |||||||||||
| Terminology | Conflict in merging terminology and track changes: "{type}". | Merging track changes and terminology was producing and error. See log details for more information. | |||||||||||
| Terminology | TermTagger 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. | |||||||||||
| Terminology | TermTagger 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. | |||||||||||
| Terminology | TermTagger 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. | |||||||||||
| Terminology | TBX 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. | |||||||||||
| Terminology | TBX 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. | |||||||||||
| Terminology | TBX Import: Import error - {msg} | Very unusual that this error happens, see the msg and extra data. | |||||||||||
| Terminology | TBX Import: Could not import due unknown attribute level | Very unusual that this error happens, see the msg and extra data. | |||||||||||
| Terminology | TBX 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. | |||||||||||
| Terminology | TBX 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. | |||||||||||
| Terminology | TBX 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. | |||||||||||
| Terminology | TermTagger overall run done - {segmentCounts} | Reports that the whole task was tagged with the termtagger and shows the segment status counts. |
...
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Quality processing on Task Import or Segment editing | Setting the FieldTags tags by text led to a changed text-content presumably because the encoded tags have been improperly processed | Create a ticket for this issue with the event added. | ||||||
| Quality processing on Task Import or Segment editing | Two non-splittable tags interleave each other. | Create a ticket for this issue with the event added. | ||||||
| Quality processing on Task Import or Segment editing | SNC lib (which stands behind AutoQA Numbers Check) detected an error of a kind previously unknown to translate5 app | Create a ticket for this issue with the event added. |
Excel Ex-Import
...