Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

EventCodeContextEventMessageDescription / Solution

Anchor
E1257
E1257
E1257

Language Resources; Service

The LanguageResource-Service "{serviceType}" is not configured. Please check this confluence-page for more details: "{url}"

When adding a LanguageResource, trasnalte5 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.

Anchor
E1050
E1050
E1050

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.

Anchor
E1051
E1051
E1051

Language Resources; TaskCannot 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.

Anchor
E1106
E1106
E1106

Language ResourcesGiven 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).

Anchor
E1158
E1158
E1158

Language ResourcesA Language Resources cannot be deleted as long as tasks are assigned to this Language Resource.Remove all tasks first from that resource.

Anchor
E1169
E1169
E1169

Language ResourcesThe task is in use and cannot be reimported into the associated language resources.Check who or what process is locking the task

Anchor
E1282
E1282
E1282

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,

Anchor
E1288
E1288
E1288

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.

Anchor
E1300
E1300
E1300

Language ResourcesThe 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.

Anchor
E1301
E1301
E1301

Language ResourcesThe 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.

Anchor
E1302
E1302
E1302

Language ResourcesThe 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.

Anchor
E1303
E1303
E1303

Language Resouce OpenTM2OpenTM2: could not add TMX data to TMThe uploaded TMX could not be added to the TM, see error details for more information.

Anchor
E1304
E1304
E1304

Language Resouce OpenTM2OpenTM2: could not create prefilled TMThe uploaded TM could not be used as new TM, see error details for more information.

Anchor
E1305
E1305
E1305

Language Resouce OpenTM2OpenTM2: could not create TMThe TM could not be created, see error details for more information.

Anchor
E1306
E1306
E1306

Language Resouce OpenTM2OpenTM2: could not save segment to TMA segment in the TM could not be updated, see error details for more information.

Terminology

EventCodeContextEventMessageDescription / Solution

Anchor
E1152
E1152
E1152

Terminology

Missing mandatory collectionId for term creation.


Anchor
E1153
E1153
E1153

TerminologyMissing mandatory language (ID) for term creation.

Anchor
E1154
E1154
E1154

TerminologyGroupId was set explicitly, this is not allowed. Must be set implicit via a given termEntryId.

Anchor
E1105
E1105
E1105

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.

Anchor
E1108
E1108
E1108

TerminologyThere 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.

Anchor
E1109
E1109
E1109

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.

Anchor
E1110
E1110
E1110

TerminologyThere 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.

Anchor
E1111
E1111
E1111

TerminologyThe 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.

Anchor
E1113
E1113
E1113

TerminologyNo 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.

Anchor
E1114
E1114
E1114

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.

Anchor
E1115
E1115
E1115

TerminologyCollected terms could not be converted to XML.Internal SimpleXML error.

Anchor
E1116
E1116
E1116

Terminology

Could not load TBX into TermTagger: TBX hash is empty.

There was probably an error on the TBX generation before.

Anchor
E1117
E1117
E1117

TerminologyCould 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.

Anchor
E1118
E1118
E1118

TerminologyCould 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.

Anchor
E1119
E1119
E1119

TerminologyTermTagger communication Error.

Anchor
E1130
E1130
E1130

TerminologyTermTagger 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.

Anchor
E1120
E1120
E1120

TerminologyTermTagger returns an error on tagging segments.

Anchor
E1121
E1121
E1121

TerminologyTermTagger result could not be decoded.Look also for a directly following E1133 or E1134 in the log.

Anchor
E1122
E1122
E1122

TerminologyTermTaggerImport Worker can not be initialized!Some error happened on worker initialization, check logged parameters.

Anchor
E1123
E1123
E1123

TerminologySome 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.

Anchor
E1124
E1124
E1124

TerminologyParameter validation failed, missing serverCommunication object.Happens on live termtagging on segment editing only.

Anchor
E1125
E1125
E1125

TerminologyTermTagger 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.

Anchor
E1126
E1126
E1126

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.

Anchor
E1127
E1127
E1127

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.

Anchor
E1128
E1128
E1128

TerminologySee E1122.

Anchor
E1240
E1240
E1240

TerminologyTermTagger 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.

Anchor
E1129
E1129
E1129

TerminologyTermTagger 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:

Code Block
languagesql
DELETE FROM `Zf_memcache` WHERE `id` = 'TermTaggerDownList';


Anchor
E1131
E1131
E1131

TerminologyTermTagger 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.

Anchor
E1132
E1132
E1132

TerminologyConflict in merging terminology and track changes: "{type}".Merging track changes and terminology was producing and error. See log details for more information.

Anchor
E1133
E1133
E1133

TerminologyTermTagger 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.

Anchor
E1134
E1134
E1134

TerminologyTermTagger 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.

...