Page tree

Versions Compared

Key

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

...

EventCodeContextEventMessageDescription / Solution

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!

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.

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.

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
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
E1130E1131E1130
E1131
E1130E1131

TerminologyNo TermTaggers available, task imported without terms tagged.See E1129 how to reactivate the TermTaggers.

...