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