| EventCode | Context | EventMessage | Description / Solution |
|---|
| 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! |
| 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. |
| Terminology | Error in communication with TermTagger. |
|
| Terminology | TermTagger returns an error on tagging segments. |
|
| Terminology | TermTagger result could not be decoded. |
|
| 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 | One TermTagger DOWN: one or more configured TermTagger instances are not available. TermTagger server status: {serverStatusserverList}. | 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. |
|
|
|
|
|