...
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 | 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 Resouce OpenTM2 | OpenTM2: could not add TMX data to TM | The uploaded TMX could not be added to the TM, see error details for more information. | ||||||
| Language Resouce OpenTM2 | OpenTM2: could not create prefilled TM | The uploaded TM could not be used as new TM, see error details for more information. | ||||||
| Language Resouce OpenTM2 | OpenTM2: could not create TM | The TM could not be created, see error details for more information. | ||||||
| Language Resouce OpenTM2 | OpenTM2: could not save segment to TM | A segment in the TM could not be updated, see error details for more information. | ||||||
| Language Resouce 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 Resouce Google Translate | Google Translate authorization failed. Please supply a valid API Key. | The configured API Key is not valid. | ||||||
| Language Resouce Google Translate | Google Translate quota exceeded. The character limit has been reached. | The usage quota of your Google Translate account is exceeded. | ||||||
| Language Resouce 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. |
Terminology
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. |
...