...
EventCode | Context | ErrorMessage | 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. |
Task & Workflow
EventCode | Context | ErrorMessage | Description / Solution | ||||||
---|---|---|---|---|---|---|---|---|---|
| Task; Workflow | Multi Purpose Code logging in the context of a task | Multi Purpose code for several info logs around a task. Also important in Context of workflow. | ||||||
| Job; Workflow | Multi Purpose Code logging in the context of jobs (task user association) | Multi Purpose Code logging in the context of jobs (task user association) | ||||||
| Workflow only | Multi Purpose Code logging in the context of pure workflow processing | Multi Purpose Code logging in the context of workflow processing | ||||||
| Task | The task can not be removed due it is used by a user. | One user has opened the task for reading or editing the task. Therefore this task can not be deleted. | ||||||
| Task | The task can not be removed due it is locked by a user. | One user has opened the task for editing the task, or some other action has locked the task. Therefore this task can not be deleted. | ||||||
| Task | The task can not be locked for deletion. | The task must be locked by the deleting user, before it can be deleted. This lock could not be set. | ||||||
| Task; ManualStatusCheck Plug-In | The Task can not be set to finished, since not all segments have a set status. | Each segment must have set a status in order to finish the task. | ||||||
| Task | The current task status does not allow that action. | This error occurs if the current status of the task does not allow the triggering action. | ||||||
| Task; ArchiveTaskBeforeDelete Plug-In | Task could not be locked for archiving, stopping therefore the delete call. | The task must be locked by the deleting user, before it can be deleted. This lock could not be set. | ||||||
| Task | The referenced customer does not exist (anymore). | The user tried to add a non existence client to a task. Probably the customer was deleted in the mean time. |
...
EventCode | Context | ErrorMessage | 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}. 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. | ||||||
| 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 Groupshare
EventCode | Context | ErrorMessage | Description / Solution | ||||||
---|---|---|---|---|---|---|---|---|---|
| Plug-In GroupShare | Multi Purpose Code logging in the context of Groupshare | Multi Purpose Code logging in the context of Groupshare. | ||||||
| Plug-In GroupShare | Groupshare Plug-In: Exception | General Purpose Exception | ||||||
| Plug-In GroupShare | Groupshare Plug-In: No valid license token in cache for current user | There is no valid license token in the cache for the current user. The license token creation for this user was probably done before, but the token does not exist anymore. |
Plug-In MatchAnalysis
EventCode | Context | ErrorMessage | 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. |
ErrorCode Design rules / decisions
...