...
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Plug-In InstantTranslate | InstantTranslate: Response status "{status}" in indicates failure in communication with the API. | Check the error log for further information. | ||||||
| Plug-In InstantTranslate | InstantTranslate: parse error in JSON response, the error was: "{msg}" | Check the error log for further information. | ||||||
| Plug-In InstantTranslate | InstantTranslate: empty JSON response. | Check the error log for further information. | ||||||
| Plug-In InstantTranslate | InstantTranslate: Filetranslation failed. "{msg}" | Check the error log for further information. | ||||||
| Plug-In InstantTranslate | InstantTranslate: Parameter is not valid. "{msg}" | Check the error log for further information. | ||||||
| Plug-In InstantTranslate | InstantTranslate: Error in config or roles. "{msg}" | Throws an error due to configuration-issues. Check the error log for further information. | ||||||
| Plug-In InstantTranslate | InstantTranslate: Please check your configuration for pretranslationTaskLifetimeDays. " | Adds an entry in the error-log due to configuration-issues, but doesn't stop the application. Solution: Check if pretranslationTaskLifetimeDays is set in the configuration. | ||||||
| Plug-In InstantTranslate | InstantTranslate: "0" as upload field name is deprecated. Use "file" as upload field name instead. | Temporary warning for "0" the file upload api field name. The correct file upload field name for files pre-translations should be "file". | ||||||
| Plug-In InstantTranslate | InstantTranslate: Not all required parameters are provided when writing to instant-translate memory | Missing parameters where found in the write to instant translate memory request. | ||||||
| Plug-In InstantTranslate | InstantTranslate: The submitted Markup is invalid | The User submitted invalid markup that therefore could not be translated |
Plug-In MatchAnalysis
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Plug-In MatchAnalysis | Multi Purpose Code logging in the context of MatchAnalysis | Multi Purpose Code logging in the context of MatchAnalysis. | ||||||
| Plug-In MatchAnalysis | Disabled a Language Resource for analysing and pretranslation due too much errors. | Check the details and also the logs for more information. | ||||||
| Plug-In MatchAnalysis | Internal Fuzzy language resource could not be created. Check log for previous errors. | Check the details and also the logs for more information. | ||||||
| Plug-In MatchAnalysis | Unable to use connector from Language Resource "{name}". Error was: "{msg}". | Check the details and also the logs for more information. | ||||||
| Plug-In MatchAnalysis | MatchAnalysis Plug-In: tried to load analysis data without providing a valid taskGuid | A valid taskGuid must be provided here as parameter, to load only the analysis data for one task. | ||||||
| Plug-In MatchAnalysis | MatchAnalysis Plug-In: task can not be locked for analysis and pre-translation. | The task was locked by another process, so no analysis and pre-translation is possible. | ||||||
| Plug-In MatchAnalysis | MatchAnalysis Plug-In: TermTagger worker for pre-translation can not be initialized. | |||||||
| Plug-In MatchAnalysis | MatchAnalysis Plug-In: Language resource "{name}" has status "{status}" and is not available for match analysis and pre-translations. | There is a problem with the associated language resource to be used for analysis and pre-translation. Please check status and details of the problem. |
...