...
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| everywhere | Several | Code used for multi purposes: Mostly for debug messages below level warn, where no fixed message is needed. | ||||||
| everywhere | Several | Default code used for old error messages, which are not converted yet to the new error code system. | ||||||
| everywhere | Log HTTP Request | The HTTP request to the server and its parameters are logged. Generally for debugging only. | ||||||
| entities | Duplicate Key | A database key for the entity to be saved does already exist. | ||||||
| entities | Integrity Constraint Violation | An entity can not be added or updated since a referenced entity does not exist (anymore). Or an entity can not be updated or deleted since it is referenced by other entities. | ||||||
| everywhere | HTTP Status 404 | The requested URL / page was not found, the API endpoint in the application does not exist. | ||||||
| everywhere | HTTP Status 422 | The PUT / POST request to that URL could not be processed due invalid given data. The invalid fields are listed in the result from the server. | ||||||
| everywhere | HTTP Status 422 | The File Upload did not succeed PUT / POST request to that URL could not be processed due invalid given data. The invalid fields are listed in the result from the server. | ||||||
| everywhere | HTTP Status 409 | The PUT / POST request to that URL could not be processed due the given data would produce an invalid state of the entity on the server. If possible, the causing fields are listed in the result from the server, or the error message is self explaining. | ||||||
| everywhere | PHP Fatal Error | PHP Fatal error, see error message for details. | ||||||
| everywhere | PHP Warning | PHP Warning, see error message for details. | ||||||
| everywhere | PHP Info | PHP Info, see error message for details. | ||||||
| Worker | Can not trigger worker URL: {host}:{port} Error: {errorName} ({errorNumber}) | The triggered worker URL is technically not available. Local firewall problems? Is the configured "runtimeOptions.server.name" available and callable from the translate5 instance? If not, it can help to configure "runtimeOptions.worker.server" with the local host name or the localhost IP, basicly the server adress which points to the local server and is available for the translate5 instance. | ||||||
| Worker | Worker URL result is no HTTP answer!: {host}:{port} | This can only happen if the worker URL is not pointing to an translate5 instance, or if there is an error on the translate5 instance. In the latter case investigate the log for further errors. | ||||||
| Worker | Worker HTTP response state was not 2XX but {state}. | This should happen only if there is an error on the translate5 instance. In the latter case investigate the log for further errors. | ||||||
| Worker | Worker HTTP response state was 404, the worker system requests probably the wrong server! | Check the server URL configuration values. Either runtimeOptions.worker.server or runtimeOptions.server.protocol and runtimeOptions.server.name are pointing to a wrong server / translate5 installation! |
Authentication
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Authentication | Tried to authenticate via hashAuthentication, but feature is disabled in the config! | Please set runtimeOptions.hashAuthentication in the configuration to one of the following values: disabled: the feature is disabled and produces this error. |
Users & Customers
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Customer | A client cannot be deleted as long as tasks are assigned to this client. | Remove all tasks first from that customer. | ||||||
| Customer | The given client-number is already in use. | There exists already a customer with that client-number. | ||||||
| User | The user can not be deleted, he is PM in one or more tasks. | Change the PMs in the affected tasks. | ||||||
| User | User can not be saved: the chosen login does already exist. | Use a different login. | ||||||
| User | User can not be saved: the chosen userGuid does already exist. | Use a different userGuid, if no userGuid was provided explicitly, just save again to generate a new one. | ||||||
| Customer | The given domain is already in use. | The given domain is already defined for one of the customers. |
...
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Segment | The data of the saved segment is not valid. | The data of the saved segment contains invalid data, see error details for more information. | ||||||
| Segment | The data of the saved segment is not valid. | See E1065, in addition that the validations contain at least an error where the segment is either to long or to short. This error is separate since it should produce an warning instead just a debug level entry. | ||||||
| Segment | Unable to save the segment. The segment model tried to save to the materialized view directly. | Programming error: The writeable table of the segment is set to the materialized view. This is wrong, since the way is: write to the LEK_segments table, write to the data table, then update the view with the data from there. | ||||||
| Segment Pixellength | Textlength by pixel failed; most probably data about the pixelWidth is missing: fontFamily: "{fontFamily} fontSize: "{fontSize}". | Same as E1082 below, but no default width is available for that font and font size. | ||||||
| Segment Pixellength | Segment length calculation: missing pixel width for several characters. | On of the characters in the segment has no pixel length defined, the default pixel width is used. This error happens in most cases on the export of a task, where the length of the segments is finally checked. Also it happens on saving a segment. | ||||||
Excel Ex-Import
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
E1137 | Task | Task can not be exported as Excel-file. | |||||||
E1141 | Task | Excel Reimport: upload failed. | error on writing file to /data/editorImportedTasks/{takGuid}/excelReimport | ||||||
E1138 | Task | Excel Reimport: Formal check failed: task-guid differs in task compared to the excel. | |||||||
E1139 | Task | Excel Reimport: Formal check failed: number of segments differ in task compared to the excel. | |||||||
E1140 | Task | Excel Reimport: Formal check failed: segment #{segmentNr} is empty in excel while there was content in the the original task. | |||||||
E1142 | Segment | Excel Reimport: at least one segment needs to be controlled. | This is actually a warning. You have to control all segments in the given list. They may have an invalid tag-structure (eg. open a tag but not closing it) or something similar. This can lead to problems on further workflow steps. | ||||||
E1148 | Task | Task can not be locked for excel export, no excel export could be created. | That means the task is currently in use by another user / process. This is logged as info, since this can happen if another proofreader is editing while another proofreader is finishing the task. |
Plug-Ins
Plug-In Okapi
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Plug-In Okapi | Okapi Plug-In: Bconf not given or not found: {bconfFile} | Either there was no bconf given, or the default bconf could not be found. Default for import should be: ./application/modules/editor/Plugins/Okapi/data/okapi_default_import.bconf Default for export should be: ./application/modules/editor/Plugins/Okapi/data/okapi_default_export.bconf | ||||||
| Plug-In Okapi | Okapi Plug-In: tikal fallback can not be used, workfile does not contain the XLF suffix: {workfile} | In seldom scenarios tikal is used for export, if tikal receives an non XLIFF file this error is thrown. | ||||||
| Plug-In Okapi | Okapi Plug-In: Data dir not writeable: {okapiDataDir} | Solution: change filesystem rights so that the apache user can write into ./application/modules/editor/Plugins/Okapi/data | ||||||
| Plug-In Okapi | Okapi Plug-In: Error in converting file {file} on import. See log details for more information. | An error described in message happend on converting the file. Check the message, since the error could be independent from the given file, for example if some Okapi configuration was wrong, or the Okapi server is not available. A full log of the happened exception is available in the log (level debug). | ||||||
| Plug-In Okapi | Okapi Plug-In: Configuration error - no Okapi server URL is configured! | Set a correct Okapi server URL in the configuration: | ||||||
| Plug-In Okapi | Okapi Plug-In: The exported XLIFF contains empty targets, the Okapi process will probably fail then. | If the Okapi export failed investigate the XLIFF to find out the empty segments and why they are empty. | ||||||
| Plug-In Okapi | Okapi Plug-In: Error in converting file {file} on export. See log details for more information. | An error described in message happend on converting the file. Check the message, since the error could be independent from the given file, for example if some Okapi configuration was wrong, or the Okapi server is not available. A full log of the happened exception is available in the log (level debug). |
...
| 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 | 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 NecTm
| EventCode | Context | EventMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Plug-In NecTm | NecTm Plug-In: Synchronize of NEC-TM-Tags with our categories failed | NecTm Plug-In: Synchronize of NEC-TM-Tags with our categories failed. Check if the api-server of NEC-TM is running! | ||||||
EventCode Design rules / decisions
...